Abstract:
Various embodiments are generally directed to techniques for connectionless small data transmission. In one embodiment, for example, an apparatus may comprise a processor circuit, a configuration component for execution by the processor circuit to establish a connectionless small data transmission (CSDT) mode, and a communication component for execution by the processor circuit to send a small data preamble, receive a resource allocation message identifying an assigned resource, and send a small data item in the CSDT mode using the assigned resource. Other embodiments are described and claimed.
Abstract:
Various embodiments are generally directed to improved techniques for UPCON mitigation. In one embodiment, for example, an evolved node B (eNB) may comprise a processor circuit, a detection component for execution by the processor circuit to detect user plane congestion between an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) and a serving gateway (S-GW) of an evolved packet core (EPC), and a configuration component for execution by the processor circuit to select a set of user equipment (UEs) served by the E-UTRAN and the S-GW and send a request to utilize an alternate S-GW of the EPC to serve the set of UEs while maintaining a current packet data network (PDN) gateway (P-GW) for the set of UEs. Other embodiments are described and claimed.
Abstract:
Examples may include techniques for a device trigger recall or a device trigger replace procedure as implemented at a machine type communication-interworking function (MTC-IWF) in response to a command received from a service capability server (SCS). Examples may also include the SCS generating a command for a device trigger recall or a device replace to cause the MTC-IWF to implement the device trigger recall or device trigger replace procedure to either recall or replace a trigger message destined for user equipment. Both the MTC-IWF and the SCS may operate in compliance with one or more 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards.
Abstract:
Briefly, in accordance with one or more embodiments, methods to establish and control communication of a dedicated device such as a dedicated user equipment (UE) with dedicated nodes of a network are provided.
Abstract:
Various embodiments may be generally directed to techniques for UE initiated and network initiated IP flow mobility. Various embodiments provide techniques for sharing IP flow routing rules and/or filters between a UE and various network infrastructure components using existing network based protocols or extensions thereto. Various embodiments provide techniques for provisioning network based IP flow mobility triggers and for ensuring UE connections to a 3GPP network are maintained in the absence of any 3GPP network IP flows.
Abstract:
Examples may include techniques for a device trigger recall or a device trigger replace procedure as implemented at a machine type communication-interworking function (MTC-IWF) in response to a command received from a service capability server (SCS). Examples may also include the SCS generating a command for a device trigger recall or a device replace to cause the MTC-IWF to implement the device trigger recall or device trigger replace procedure to either recall or replace a trigger message destined for user equipment. Both the MTC-IWF and the SCS may operate in compliance with one or more 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards.
Abstract:
A machine type communication interworking function (MTC-IWF) is configured to receive from a service capability exposure function (SCEF), services capability server (SCS), or a third-party application server (AS), application communication pattern information defined by an MTC application and representing characteristics of machine-to-machine (M2M) communications expected from a user equipment (UE) machine type communication (MTC) device. The MTC-IWF being configured to communicate the information to a mobility management entity (MME) that thereby provides core network (CN) originated assistance to an evolved universal terrestrial radio access network node B (eNB). Disclosed are embodiments for providing the information in the form of Diameter-based messages communicated through Tsp, T5, and other interfaces, or through an application programming interface (API) exposed by the SCEF, SCS, or MTC-IWF.
Abstract:
Technology for reporting radio access network (RAN) user plane congestion (UPCON) is disclosed. In an example, a core network (CN) device can include computer circuitry configured to: receive an UPCON event report using an UPCON container that includes a congestion situation indicator to indicate a UPCON situation; and change an UPCON process based on the congestion situation indicator. The core network device can include a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a policy and charging enforcement function (PCEF), a policy and charging rules function (PCEF), a serving general packet radio service (GPRS) support node (SGSN), a gateway GPRS support node (GGSN), an access network discovery and selection function (ANDSF), an operation and maintenance (O&M) subsystem, an UPCON server, a proxy, or a standalone function entity.
Abstract:
Various embodiments may be generally directed to techniques for UE initiated and network initiated IP flow mobility. Various embodiments provide techniques for sharing IP flow routing rules and/or filters between a UE and various network infrastructure components using existing network based protocols or extensions thereto. Various embodiments provide techniques for provisioning network based IP flow mobility triggers and for ensuring UE connections to a 3GPP network are maintained in the absence of any 3GPP network IP flows.
Abstract:
Briefly, in accordance with one or more embodiments, a Cellular Internet of Things evolved Node B (CIoT eNB) comprises baseband processing circuitry to process a Cellular Internet of Things Application Protocol (CIAP) setup request message received from a CIoT gateway (CIoT GW), wherein the CIAP setup request message is to configure a reduced signaling overhead between the CIoT eNB and the CIoT GW, and generate a CIAP setup response message to be transmitted to the CIoT GW in response to the CIAP setup request message. In other embodiments, a Cellular Internet of Things gateway (CIoT GW) comprises baseband processing circuitry to generate a Cellular Internet of Things Application Protocol (CIAP) setup request message to be transmitted to a CIoT evolved Node B (CIoT eNB), and process a CIAP setup response message received from the CIoT eNB in response to the CIAP setup request message.