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:
It is recognized herein that capabilities are lacking related to how different users can be authenticated on top of an existing subscription authentication. In some examples, a user-centric authentication layer may be supported on top of an existing subscription authentication, such that different users may use the same user equipment (UE) with customized services, and different users of devices can be identified behind a gateway with a 3GPP subscription (without the devices having a dedicated 3GPP subscription). Further, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.
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 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, apparatuses and methods for bandwidth management, aggregation and internet protocol (“IP”) flow mobility (“IFOM”) across multiple-access technologies are provided. Included is a method that includes selecting, from a packet data network (“PDN”) connection formed through a plurality of access systems communicatively coupled with a wireless transmit and/or receive unit (“WTRU”), an access system over which to transport a flow of internet protocol (“IP”) traffic to and/or from the WTRU. The method may also include sending, to the WTRU, a request to associate the flow of IP traffic with the selected access system.
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 are disclosed to desynchronize transmissions in group-based operations. A group user equipment (UE), e.g., a UE that is a member of a group of UEs, may be in an inactive mode. The group UE may receive a multicast message indicating that the group UE may enter an active mode. For example, the group UE may use the active mode for periodic reporting of its monitoring activity to the network. The multicast message may indicate a mechanism for the group UE to use to send an uplink transmission to the network. The group UE may send the uplink transmission to the network at a transmission time indicated by the mechanism. The transmission time may be desynchronized from other UEs in the group.
Abstract:
The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.
Abstract:
Systems and/or methods for providing internetworking among application services layers (ASLs) of different network technologies may be provided. For example, a tunnel anchor point (TAP) may be established. The TAP may be configured to enable communication between a local application in the network and a remote application in a different network. At the TAP, an ASL tunnel may be created to the local application in the network to facilitate the communication. Additionally, a message from the local application may be received where at least a portion of the message may be configured to be provided to a remote ASL and the remote application in the different network to which the local application wishes to communicate. At least the portion of the message may be provided to the remote ASL and the remote application in the different network.
Abstract:
A method and apparatus for data transmissions in a wireless network are disclosed. A first device may send a first frame to a second device including information regarding a number of pending data frames to be transmitted from the first device to the second device. The first device receives an acknowledgement frame including a number of approved data frames for transmission from the first device to the second device. The first device then may send a plurality of data frames without performing the contention-based channel access procedure in response to the acknowledgement frame. The first device may send a first frame to a second device for requesting data frames that are pending at the second device. The first device receives an acknowledgement frame including a number of pending and approved data frames. The first device may receive a plurality of data frames in response to the acknowledgement frame.