Verizon Patent and Licensing Inc.

Yahoo! Inc.

Yahoo Holdings, Inc.

Oath Inc.

Excalibur IP, LLC

Daryl M Low

Jin Yang

Donna L Polehn

Arda Aksu

Lalit R Kotecha

Patricia Ruey Chang

Anne-Lise Hassenklover

Sanchan Saxena

Gaurav Vaish

Benoit M Schillings

Atte Lahtiranta

Marco Wirasinghe

Andreas Rossbacher

Ric Allinson

Jay Anthony Hobson

Gautam Godse

Karan Ashar

Jee Seon Yi

Itsik Figenblat

Brian Tunning

A device may receive channel data associated with a channel provided between a network and a user device, and may calculate, based on the channel data, key performance indicator data that includes a plurality of key performance indicators for the channel. The device may multiply the plurality of key performance indicators by factors to generate factored key performance indicator data that includes a plurality of factored key performance indicators. The device may apply weights to the plurality of factored key performance indicators of the factored key performance indicator data to generate factored weighted key performance indicator data that includes a plurality of factored weighted key performance indicators. The device may calculate a quality indicator for the channel based on the factored weighted key performance indicator data, and may perform one or more actions based on the quality indicator for the channel.

Systems and methods for determining initial channel quality conditions of a channel for provision of content

A network device may receive multi-access edge computing (MEC) proximity service information that identifies a set of MEC devices and a set of network services supported by respective MEC devices of the set of MEC devices. The network device may transmit, to a base station, at least a portion of the MEC proximity service information for broadcasting by the base station. The network device may receive, from a user device, a request to establish a peer-to-peer connection with a MEC device for the network service. The network device may authenticate the user device for access to the network service. The network device may transmit, to the user device and the MEC device, connection information that enables the user device and the MEC device to establish the peer-to-peer connection, based on authenticating the user device for access to the network service.

Systems and methods for network-enabled peer-to-peer communication using multi-access edge computing

Systems and methods provide a latency certification service. One or more network devices in an application service layer network receive a service request for a latency certification service and instantiate a Transmission Control Protocol (TCP) proxy for a data session between an application server device and a user equipment (UE) device. The one or more network devices obtain a digital certificate for the TCP proxy. The one or more network devices receive, at the TCP proxy, a data packet from the UE device; apply a certified timestamp to the data packet to form a certified timestamped data packet; and forward the certified timestamped data packet to the application server device.

System and method for latency certification service

A method, a device, and a non-transitory storage medium are described in which a network allocation service is provided. The network allocation service may use available network resource information of an application service layer network of a first type, such as a multi-access edge computing network, and application service demand information of an application to determine whether a performance metric of the application service would be satisfied. The performance metric may include a threshold service time that includes a processing time associated with a processing of an application service request and response, by the application service layer network, and a transit time associated the application service response from the application service layer network to an end device. The network allocation service may select the first type or a second type of application service layer network depending on the outcome of the determination.

Method and system for edge and non-edge networks allocation

A multi-access edge computing (MEC) node of a MEC network may receive, from a user device a first request to communicate via a peer-to-peer connection routed through a MEC network. The MEC node may identify one or more candidate devices that are available to communicate with the user device via the peer-to-peer connection. The MEC node may provide, to a particular candidate device of the one or more candidate devices, a second request to communicate via the peer-to-peer connection. The MEC node may receive, from the particular candidate device, an acceptance to communicate via the peer-to-peer connection. The MEC node may route data between the user device and the particular candidate device via the peer-to-peer connection.

Systems and methods for peer-to-peer data exchange via multi-access edge computing

As provided herein, a translated string, received from a translator for an application (e.g., an instrumented application) may be identified. The translated string may be identified based upon the translated string being associated with a service call instruction for the application. A simulated instrumented application may be generated for testing the application. The simulated instrumented application may be generated to comprise the translated string integrated into the application. The simulated instrumented application may comprise an element corresponding to the translated string. A user interface may be generated. The user interface may comprise the simulated instrumented application, the translated string visually associated with the element, and an editing functionality to edit the translated string.

In-context translation review

The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Inferring user identity across multiple applications and user devices

Techniques are described for providing deep linking capability from any mobile app to any other mobile app in a way that is scalable. App configuration information (including deep link information) is programmatically accumulated and provided to mobile devices in a way that enables launching or linking to mobile apps to meet expressed information needs of users. In addition, online marketplaces are described that employ such techniques to enable a wide variety of transaction types.

Deep linking to mobile applications

An output resource identifier, such as a universal resource locator (URL), may be programmatically generated using one or more recomposition rules and decomposed parts of a source, or input, URL. The decomposed parts may be programmatically generated using one or more decomposition rules. The input and output URLs may comprise one or more of web and/or native URLs.

System and method for programmatically creating resource locators

In one embodiment, a current state of an application that is executing may be identified. A plurality of next possible states to which a user can navigate from the current state may be ascertained. A history of user behavior of one or more users may be determined. Data pertaining to at least one of the plurality of next possible states may be fetched based, at least in part, upon the history of user behavior of the one or more users.

Mobile application pre-fetching using a state framework

A method for identifying a user is provided, including the following method operations: identifying at least three contact regions on a touch sensitive surface, the contact regions defined by simultaneous contact of at least three fingers of the user with the touch sensitive surface; for each contact region, determining a center point; determining distances between each of the determined center points of the contact regions; comparing the determined distances against predefined distances associated with a known user; based on the comparing, determining the user to be the known user or not the known user.

Multi-finger user identification

A request is received to access a user account. A geolocation of a mobile device registered with the user account is obtained directly from the mobile device. Authentication credentials for the user account are verified for correctness. A mobile device geolocation verification request is transmitted to a cellular data provider. The cellular data provider is equipped to independently determine a true geolocation region of the mobile device for comparison with the geolocation of the mobile device as obtained directly from the mobile device. A verification response to the mobile device geolocation verification request is received from the cellular data provider. The verification response indicates whether or not the geolocation of the mobile device as obtained directly from the mobile device corresponds to the true geolocation region of the mobile device. A response to the access request based on the verification response is transmitted.

Methods and system for device authentication

A server-implemented method for managing packages on a client device is provided. The method initiates with receiving a content request from a client device, the content request defining a requested content item and current package data identifying one or more currently installed packages on the client device. Required packages for providing the requested content item are determined based on the content request, wherein determining the required packages includes analyzing dependencies amongst the required packages. A response to the content request is generated based on the determined required packages and the current package data, the response defining actions for providing the requested content item at the client device and actions for managing the one or more currently installed packages on the client device. The package management instructions are sent to the client device.

Growing community of inventors

San Jose, CA, United States of America

Daryl M Low