Verizon Patent and Licensing Inc.

Amazon Technologies, Inc.

Verizon Laboratories Inc.

Verizon and Redbox Digital Entertainment Services, LLC

Fenglin Yin

Jianxiu Hao

Jack Jianxiu Hao

Zhiying Jin

Susan Kelly

Zhong Chen

Guillermo Ortiz

Ajit Nair

Hannah Youngsil Moon

Diego Sebastian Rozensztejn

David Anthony Philbin

Demetrios Karis

William Christopher Smith

Sharon Marie Walker

Jennifer Logan Stelling

Jae Won Chung

Okeno R Palmer

Wei Xia

Pramod Kalyanasundaram

John S Huitema

Dahai Ren

Jian Huang

Hong Xiao

Feng Li

Shuai Wu

Fengping Zhang

Fang Zhu

Guanrao Chen

Ishan Awasthi

Lin Zhu

Wenjie Liu

Juhong Liu

Ashraf Shehata

Vivian H Lu

Abhishek Gupta

Andrew Roberto Turner

A method includes receiving readings from a plurality of Internet of Things (IoT) devices. The method identifies rules associated with the readings from the IoT devices and determines a three dimensional (3D) dataset based on the plurality of IoT devices, the readings and rules associated with the readings from the plurality of IoT devices. The method includes determining policies to be applied to routing of the readings based on rules for dividing the readings into subsets of the 3D dataset, and routing processing for subsets of the readings to be processed in parallel by processing units based on the policies. The method further includes processing the readings to generate a list of actions, and resolving the conflicts in the list of actions based on a multi-phase queue. The method also includes executing the actions.

Rules execution system for IoT devices

A device can receive, from a network device, information that identifies a user device. The network device might have authenticated the user device based on the user device accessing a radio access network. The device can receive, from the user device, a request for a first token. The request can include an encrypted session identifier. A server device might have encrypted the session identifier. The device can determine the session identifier, and generate the first token based on the session identifier and the information that identifies the user device. The device can encrypt the first token using an application public key, and provide, to the user device, the encrypted first token. The user device can provide, to the server device, the encrypted first token. The server device can register the user device to receive content based on the encrypted first token.

Network-based device registration for content distribution platforms

A device may receive first data items and second data items that may have been output by sensor devices. The device may add, to a node in a data structure, at least some of the first data items. The device may divide the node to create subnodes that correspond to subregions of a geographic region. The device may add, to at least one of the subnodes, at least some of the second data items. The device may generate a probability of a first relationship, between the first data items and the second data items, based on determining subnodes that include a first data item and determining subnodes that exhibit a predefined second relationship with a second data item. The device may send, to another device, the probability of the first relationship to support location-based services.

Determining a probability of a relationship between layers of geographic information system data

A system is configured to receive, by a first server, a request, from a user device, for a first record stored by a cache associated with the first server, determine, a first timestamp associated with the first record, determine that the first record is invalid based on the first timestamp, and determine, based on determining that the first record is invalid, whether the first record is out of date with respect to a corresponding second record stored by a second server by comparing a second timestamp of the first record with a timestamp of the second record. The system is further configured to update the first record with information from the second record to form an updated first record when the first record is out of date, and to send the updated first record to the user device associated with the request.

Time-based data caching

A device can receive, from a user device, a transmission control protocol (TCP) synchronize (SYN) packet associated with a request to establish a TCP connection with a server device. The device can prevent a first TCP connection from being established between the device and the user device based on the TCP SYN packet. The device can cause a second TCP connection to be established between the device and the server device based on the TCP SYN packet and after preventing the first TCP connection from being established. The device can cause a third TCP connection to be established between the device and the user device after causing the second TCP connection to be established. The device can transfer network traffic between the user device and the server device based on the second TCP connection and the third TCP connection.

Transmission control protocol (TCP) synchronize (SYN) signaling passthrough for TCP proxy servers

Attributes of a session, between a source device and a verification device, for sending first verification data, such as a password and an account identifier, are determined. The verification device generates user device data based on an identifier, such as a mobile device number (MDN), for a user device associated with the account identifier. An identifier, such as an MDN, associated with the source device and an encryption key associated with the verification device are determined based on session attributes. Second verification data is generated based on the identifier associated with the source device. The second verification data is encrypted using the encryption key and forwarded to the verification device. The verification device decrypts the second verification data and compares the identifier for the user device to the identifier for the source device to determine whether the first verification data was sent from the user device.

Using a mobile device number (MDN) service in multifactor authentication

A first device may receive data, to be provided to a second device, and an application identifier. The data and application identifier may be received from a third device. The first device may be associated with a first network, and the second device may be associated with a second network. The first network may be a different network than the second network. The application identifier may be associated with the second device. The first device may determine that the data is destined to the second device based on the application identifier. The first device may cause a secure session to be established with the second device. The secure session may allow the data to be securely transmitted from the third device to the second device. The first device may provide the data to the second device via the secure session.

Secure data upload/download service

A device may receive traffic flow information that includes user device identifiers. The device may receive, from a user device accessing an application associated with a third party service, an authentication request to authenticate the user device with a third party device that provides the third party service. The request may include a session token that identifies a session, an application identifier that identifies the application, and a user device identifier that identifies the user device. The device may determine to authenticate the user device based on whether the user device identifier matches one of the user device identifiers included in the traffic flow information. The device may provide, to the third party device, the session token and an indication of whether the user device has been authenticated to permit the third party device to allow or deny access to the third party service.

Authentication of a user device using traffic flow information

Systems and methods described herein provide redundant functionality for multi-cloud high availability continuous service provisioning. Service rule configuration of regional internet services platforms at different geographical locations are provisioned through a multi-cloud provisioning platform. The systems and methods provide that there is no disruption of service provisioning, in the event of a failure of one cloud provisioning platform, as long as at least one other cloud provisioning platform is available. In the event of a cloud disaster outage at one cloud provisioning platform, a regional internet services platform will automatically register with another active cloud provisioning platform.

High availability internet services provisioning

Methods, systems, and computer program products for providing location based services are provided. Embodiments may include storing locations for a plurality of users of a telecommunication environment and contact lists of associated users for the plurality of users. Embodiments may also include providing the locations of the associated users for a first user based on a request from the first user. The request may further include providing locations for associated users who are located within an area of interest. The area of interest may be defined by a particular distance from the first user or by a point of interest of the first user. The locations of the users may be determined based on the locations of communication devices of the users including an identified receiving communication device for each user.

Method, system, and computer program product for providing location based services

A device may receive, from a mobile device, first encrypted information, encrypted by a content provider device using a first private key, and at least one unencrypted identifier. The device may decrypt, using a first public key, the first encrypted information to obtain first information that may include second encrypted information, encrypted using a second public key. The device may decrypt, using a second private key, the second encrypted information to obtain second information that may include at least one first identifier and at least one second identifier corresponding to a toll-free data service campaign that may be provided by a content provider. The device may allow toll-free data service traffic, for the mobile device, based on whether the at least one first identifier corresponds to the at least one unencrypted identifier and the traffic includes at least one third identifier that corresponds to the at least one second identifier.

Identifying traffic associated with a content provider's toll-free data service campaign

A first device may receive a request from a second device. The request may include a device identifier associated with the second device. The request may be transmitted by the second device to obtain a signature, based on which to access a third device. The first device may determine that the device identifier is associated with a secure authentication service. The first device may generate a signature based on determining that the device identifier is associated with the secure authentication service. The first device may provide the signature to the third device. The signature may permit the third device to selectively permit or deny access by the second device based on a result of authenticating the signature. Access may be permitted when the third device successfully authenticates the signature, and access may be denied when the third device fails to authenticate the signature.

Secure authentication service

Growing community of inventors

Lexington, MA, United States of America

Fenglin Yin