Abstract:
Embodiments described herein are generally directed to decentralized proof of creation. According to one embodiment, a blockchain and smart contracts, including a social decentralized identifier (DID) contract and multiple creator contracts owned and controlled by respective creators, are maintained by a proof of creation facilitator service. A first social DID for a creator of a digital artifact is created on the blockchain via the social DID contract. Based at least in part on the first social DID, decentralized proof of creation (e.g., a non-fungible token (NFT)) for the digital artifact is created on the blockchain via a creator contract of the multiple creator contracts deployed by or on behalf of the creator.
Abstract:
A 3GPP monitoring architecture framework provides monitoring event configuration, detection, and reporting for machine-type and other mobile data applications by configuring monitoring on a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node through existing interfaces, such as Tsp, T4, and T5 interfaces.
Abstract:
An apparatus may comprise a radio-frequency (RF) transceiver and a message aggregation module arranged to intercept multiple messages from one or more mobile data applications during an idle mode of a device, one or more of the multiple messages operable to trigger a transition of the device from the idle mode to a connected mode by causing a radio resource control message to be sent from the device to a radio access network, the message aggregation module to store the multiple messages in a buffer associated with the one or more mobile data applications in order to maintain the device in the idle mode, and schedule for transmission by the RF transceiver the stored messages at a defined time instance based on a delay tolerance for the one or more mobile data applications when the device is in the connected mode. Other embodiments are disclosed and claimed.
Abstract:
Technologies for performing security monitoring services of a network functions virtualization (NFV) security architecture that includes an NVF security services controller and one or more NFV security services agents. The NFV security services controller is configured to transmit a security monitoring policy to the NFV security services agents and enforce the security monitoring policy at the NFV security services agents. The NFV security services agents are configured to monitor telemetry data and package at least a portion of the telemetry for transmission to an NFV security monitoring analytics system of the NFV security architecture for security threat analysis. Other embodiments are described and claimed.
Abstract:
A 3GPP monitoring architecture framework provides monitoring event configuration, detection, and reporting for machine-type and other mobile data applications by configuring monitoring on a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node through existing interfaces, such as Tsp, T4, and T5 interfaces.
Abstract:
Examples are disclosed for delivering, at user equipment (UE) such as a wireless device, emergency payloads for non-voice emergency services (NOVES). The examples include receiving, at a UE, an emergency payload associated with a NOVES that may include an emergency indicator, a voice message, a video or a text message. An attempt may be made to deliver the emergency payload to a public service answering point (PSAP) and if the attempt is not successful, the emergency payload may be stored at the UE. A number of reattempts may be made to deliver the emergency payload to the PSAP if the attempt is not successful. Based on an acknowledgement of delivery of the emergency payload to the PSAP or aborting reattempts to deliver the emergency payload, the stored emergency payload may be removed from the UE. Other examples are described and claimed.
Abstract:
A method and an information handling system configured to select a mobility anchor point for a mobile device in a distributed mobility anchor point network may comprise collecting information about movement behavior or data transfer behavior of the mobile device, or tunneling overhead of two or more base stations. A mobility anchor point associated with a first base station may be assigned to the mobile device if the mobile device is connected to the first base station for at least a predetermined amount of time, if the mobile device transfers at least a predetermined amount of data via the first base station, or device if a tunneling overhead of the first base station is less than a predetermined level. In some embodiments, a centralized mobility anchor may be assigned to the mobile device if the mobile device is highly mobile and there is no identified base station to which the mobile device is frequently connected.
Abstract:
A network apparatus comprises a controller to determine a first base station for transmitting data and to determine a second different base station for receiving data. In one embodiment, the network apparatus further comprises a transceiver to transmit data to the first base station while associated with the second base station. The transceiver is operable to receive data from the second base station while associated with the first base station.
Abstract:
Embodiments of apparatus, packages, computer-implemented methods, systems, devices, and computer-readable media (transitory and non-transitory) are described herein for ascertaining, e.g., by a traffic detection function (“TDF”), that a first user equipment (“UE”) and a second UE are, potentially, sufficiently proximate to each other to wirelessly exchange data directly. In various embodiments, an evolved serving mobile location center (“E-SMLC”) may be instructed, e.g., by the TDF, to obtain location change data associated with the first and second UEs. In various embodiments, a determination may be made, e.g., by the TDF, based on the location change data, whether the first and second UEs are sufficiently proximate to exchange data directly, and whether the first and second UEs are likely to remain proximate for at least a predetermined time interval. In various embodiments, the first and second UEs may be caused to commence device-to-device (“D2D”) communication based on the determination.
Abstract:
Embodiments described herein are generally directed to decentralized compute infrastructure (DCI). According to one embodiment, a determination is made by a recommendation engine running on a client computer system to offload a particular non-containerized workload associated with a host application from a SaaS cloud to the client computing system on which the host application is also running. After the determination, a unit of execution in which the particular workload is packaged may be fetched and the non-containerized workload may be caused to be run locally on the client computing system. In some examples, a metric indicative of cost savings accrued by a vendor of the host application due to offloading may be tracked and at least a portion of the cost savings may be distributed to one or both of a subscriber of the host application and one or more third party stakeholders.