Verizon Patent and Licensing Inc.

Cellco Partnership

Guavus, Inc.

Other

Chris S Neisinger

Lalit R Kotecha

Sagiv Draznin

Benjamin J Parker

Barry F Hoffner

Steven Roy Rados

Phillip Andrew Ritter

Andrew Howard Colby

Douglas Alan Junkins

David Chiang

Emerando M Delos Reyes

Scott Anthony Townley

William Howard Stone, Jr

Brian Olson

Satish S Vasamsetti

Lindsay Notwell

Mark Guyler

Michal Patryk Debicki

A system and method for determining a quality of experience (QoE) requirement for an application accessing a CSP network is described. When the application is executed on a mobile device, a message is communicated from the mobile application to a QoE network appliance. The message is associated with a QoE requirement for latency, bandwidth, and packet loss rate. A radio access network (RAN) data set and a core network (CN) data set that includes a network data analytics function (NWDAF) data set is identified and communicated to the QoE network appliance which associates the RAN data set, the CN data set, and the NWDAF data with the requirements for said latency, bandwidth, and packet loss rate, and generates a measured QoE Score.

Determining QoE requirements for 5G networks or hybrid 5G networks

A system and method for measuring quality of experience (QoE) satisfaction for an application accessing a CSP network is described. A QoE requirement is associated with an application executed on a mobile device that is communicatively coupled to a CSP network. The QoE requirement for the application includes a QoE latency requirement, a QoE bandwidth requirement, and a QoE packet loss rate requirement. An edge-collection module gathers a radio access network (RAN) data set, and a core network (CN) data set that includes a network data analytics function (NWDAF) data set. The QoE network appliance generates a measured QoE score with the RAN data set, the CN data set, and the NWDAF data set. The measured QoE score is associated with the latency measurement, the bandwidth measurement, and the packet loss rate measurement. A subscriber ID is billed when a charging function determines the measured QoE satisfies the QoE requirement.

Measuring QoE satisfaction in 5G networks or hybrid 5G networks

A network load traffic management component is communicatively coupled to a radio access network (RAN). The network load traffic management component includes a subscriber scoring module and a subscriber scoring database that operates on a server processor and a server memory. The network load traffic management component identifies at least one network event corresponding to a RAN control plane. The network load traffic management component monitors each network event for a session time, in which each session time is associated with each subscriber interacting with the RAN. The network load traffic management component, repeatedly, determines a performance measurement for each network event associated with each session time. The performance measurement for each network event is recorded. A subscriber score is generated based on the performance measurements for each network event. A predictive indicator score is generated based on subscriber scores and behavioral analytics associated with each subscriber.

Predictive indicator based on network performance

A system for detecting and managing network data traffic and a network load traffic management module is described. The system for detecting and managing network data traffic includes a Radio Access Network (RAN), a plurality of mobile devices, a network load traffic management server, a first dataset and a corresponding first baseline, a second data set and a corresponding second baseline, a data flow dataset, and a probability for one or more mobile devices to remain within each location associated with each RAN site, wherein the probability is calculated by the network traffic management module.

Network loading management system and method

A system may comprise an aggregator gateway associated with a zone. The system may further comprise a first relay gateway and a second relay gateway connected to the aggregator. The first relay gateway and the second relay gateway may be associated with the zone. The first relay gateway may be connected to a first M2M device located in the zone and to a second M2M device located in the zone. The second relay gateway may be connected to a third M2M device located in the zone and to a fourth M2M device located in the zone.

Scalability and redundacy for machine-to-machine (M2M) architecture

A third-party application, executing at a mobile device, may be provided with information describing congestion levels in a network, such as a cellular wireless network through which the mobile device connects. In one implementation, the third-party application may select, based on the information describing the congestion levels, a data flow, from a number of data flows, to use when communicating with a destination device, each of the data flows being associated with different quality of service (QoS) parameters and being associated with different charging rates. The mobile device may communicate, through a proxy server, and using the selected data flow, with the destination device. The communication with the destination device may be implemented using sponsored data that is not charged to an account associated with an owner of the mobile device.

Providing network congestion information to mobile devices for sponsored data

A server may receive provisioning information for a client device; provision, based on the provisioning information, the client device to prepare the client device to gather data to form a data record and communicate with a user device, via the server, to receive or transmit information relating to the data record; and receive a communication request from the user device via a first network. The communication request may include a request to transmit the information relating to the data record to or from the client device. The server may communicate with the client device via a second network, on behalf of the user device, to process the communication request based on authorizing the user device. The second network may be different from the first network. The server may provide a response to the communication request to the user device. The response may include the information relating to the data record.

Facilitating communication between a user device and a client device via a common services platform

A first device may receive provisioning information for a second device; establish a tunnel with the second device within a first network based on receiving the provisioning information; provide the provisioning information to the second device to cause the second device to gather or process data within the first network; and receive a command instruction from a user device via a second network. The command instruction may relate to the data gathered or processed by the second device. The first network may be separate from the second network. The first device may communicate with the second device within the first network and independently of the second network to process the command instruction; form a response to the command instruction based on processing the command instruction; and provide the response to the command instruction towards the user device.

Processing communications via a sensor network

A device defines a first bucket for general Internet protocol (IP) traffic provided to and from a user device associated with an open network, and defines a second bucket for quality of service (QoS)-based traffic provided to and from the user device. The device also assigns a first billing rate for the general IP traffic associated with the first bucket, and assigns a second billing rate to the QoS-based traffic associated with the second bucket, where the second billing rate is greater than the first billing rate. The device further associates the first billing rate and the second billing rate with a subscriber associated with the user device.

Quality of service (QoS)-enabled voice-over-internet protocol (VoIP) and video telephony applications in open networks

A first device may receive data associated with a second device from within a first network and independently of a second network. The second device may include a sensor or an application to form or process a data record. The first device may establish a bearer between the first device and a particular user device, of multiple user devices, in accordance with a bearer policy; and provide the data towards the particular user device via a first sub-network, of multiple sub-networks, of the second network and via the bearer. The first sub-network may be independent of a second sub-network of the multiple sub-networks. The second sub-network may permit user device data to be transmitted between the multiple user devices. The first sub-network and the second sub-network may consume different levels of network resources.

Transmitting data via a private sub-network of a service provider network

A network device is configured to receive information relating to factors associated with quality of experience issues. The network device is configured to analyze the information. The network device is configured to predict that a quality of experience factor associated with a particular type of communication will exceed a threshold level a future time. The network device is configured to send a message to the device, the device generating a rule or policy; and the rule or policy instructing one or more other network devices to increase a capacity of the network to prevent the quality of experience factor from exceeding the threshold value at the future time.

Network capacity planning

A system, associated with a service provider network, is configured to monitor traffic, that is traveling to or from the service provider network, to obtain traffic metrics that correspond to a collection of network layers, where the network layers; process the traffic metrics with respect to each of the network layers to identify an anomaly, associated with the traffic, that corresponds to at least one of the network layers; send a request for packets associated with the traffic based on the identification of the anomaly; receive copies of the packets associated with the traffic; analyze the copies of the packets to obtain information associated with the anomaly; and send a notification that indicates that the anomaly has been identified, where the notification includes the traffic metrics associated with the traffic or the information associated with the anomaly.

Anomaly detection and identification using traffic steering and real-time analytics

A system may receive a connection request, from a user device, that includes information identifying a particular application; identify that the particular application is associated with a group of classes of traffic; establish a group of bearer channels that are associated with the group of classes of traffic, the group of bearer channels being associated with a group of different levels of quality of service ('QoS'); process, via a first bearer channel and according to a first level of QoS, first traffic associated with the user device and the particular application; and process, via a second bearer channel of the group of bearer channels, according to a second level of QoS, second traffic associated with the user device and the particular application, the second bearer channel being different from the first bearer channel, and the second level of QoS being different from the first level of QoS.

Quality of service treatement for applications with multiple traffic classes

One or more servers may: receive information regarding a content file stored by a device; provide information associated with a first cost value corresponding to a cost to deliver the content file from the device to a user device; receive a delivery instruction directing the one or more servers to provide a portion of the content file to the user device via one or more ports or via one or more access points, each of the one or more ports or the one or more access points being associated with respective one or more second cost values; generate a key associated with the information regarding the content file and with the delivery instruction; receive an indication of selection of the key by the user device; deliver, to the user device, the portion of the content file via the one or more ports or the one or more access points.

Tiered-based billing for content delivery

A system is configured to receive information associated with a flow being transported via a cell within a radio access network (RAN) associated with a service provider network; identify a user device, associated with the flow, based on the information; identify a location of the device based on a location of the cell; generate a group of codes based on the location, the codes corresponding to a group of code lengths and representing one or more quantities of error associated with the location, where a particular code is associated with a code length that corresponds to a quantity of error; and transmit the codes to a content provider, where the codes enable the content provider to obtain the quantity of error that corresponds to a geographical boundary in which the user device is located, and target content, associated with an advertiser within the boundary, to the user device.

Growing community of inventors

Danville, CA, United States of America

Chris S Neisinger