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 and apparatus are described for negotiating “keep-alive” message frequencies of applications running on a wireless transmit/receive unit (WTRU). A node may include a negotiation and synchronization function (NSF) configured to collect information including frequencies of keep-alive messages required by application servers for different applications running on the WTRU, and send a keep-alive message frequency negotiation request message to the application servers to negotiate for a more proper frequency for each application on behalf of the WTRU. The node may further include a buffering and caching function (BCF) configured to cache and buffer application specific attributes including an indication of whether each of the applications needs to send periodic keep-alive messages to an associated application server. The node may be a packet data network gateway, a negotiation and caching gateway, or a serving gateway.
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 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:
A method and apparatus may use multiple URIs (MU) in a single request message for machine-to-machine (M2M) communication networks. Multiple single URI (SU)-type request messages may be received from an application client (e.g. a constrained application protocol (CoAP)/hypertext transfer protocol (HTTP) client) at a (CoAP/HTTP) intermediary node. The multiple SU-type request messages may be aggregated into a single MU-type request message at the intermediary node, and the single MU-type request message may be transmitted to a (CoAP/HTTP) server. A multiple value (MV)-type response message may be received from the (CoAP/HTTP) server. The MV-type response message may be deaggregated into multiple single value (SV)-type response messages. The multiple SV-type response messages may be transmitted to the (CoAP/HTTP) client.
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:
Embodiments contemplate wireless communication that may include sending machine type communication (MTC) application data from a services capability server (SCS) to an MTC user equipment (UE/WTRU) using a device trigger. The device trigger may be used to instruct an MTC device application to initiate communications with an SCS. Embodiments also contemplate that a first device trigger (DT) request may be received from a first wireless transmit/receive unit (WTRU) and a machine-type-communication inter-working function (MTC-IWF) may be determined in response to the first DT request. A second DT request may be sent to the MTC-IWF; and a first DT response may be received from the MTC-IWF. The first DT response may include a first information regarding a second WTRU.
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:
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.