WO2016091298A1 - Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base - Google Patents

Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base Download PDF

Info

Publication number
WO2016091298A1
WO2016091298A1 PCT/EP2014/077184 EP2014077184W WO2016091298A1 WO 2016091298 A1 WO2016091298 A1 WO 2016091298A1 EP 2014077184 W EP2014077184 W EP 2014077184W WO 2016091298 A1 WO2016091298 A1 WO 2016091298A1
Authority
WO
WIPO (PCT)
Prior art keywords
user device
flow
cell
service
information
Prior art date
Application number
PCT/EP2014/077184
Other languages
English (en)
Inventor
Seppo Ilmari Vesterinen
Matti Einari Laitila
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2014/077184 priority Critical patent/WO2016091298A1/fr
Publication of WO2016091298A1 publication Critical patent/WO2016091298A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/263—Rate modification at the source after receiving feedback
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • This description relates to wireless networking.
  • Different applications may have different quality of service (QoS) and/or quality of experience (QoE) requirements, such as bandwidth or data rate and latency.
  • QoS quality of service
  • QoE quality of experience
  • User devices and the network may be unable to meet the QoE requirements of the numerous concurrent applications with the uplink communication resources, such as uplink wireless resources, granted by a base station.
  • a method may include determining, by a base station, a congestion level for a cell, receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device, determining one or more flow events for the user device flow, sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow, receiving, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow, and sending, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: determine, by a base station, a congestion level for a cell; receive, by the base station via the cell from a user device, data associated with a user device flow from the user device; determine one or more flow events for the user device flow; send, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow; receive, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow; and send, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to the user device to cause the user device to adjust an uplink data rate of the user device flow.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: determining, by a base station, a congestion level for a cell; receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device; determining one or more flow events for the user device flow; sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow; receiving, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow; and sending, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • a method may include determining, by a base station, a congestion level for a cell, receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class, determining one or more flow events for the user device flow, sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device identification information that identifies the user device, the user device being associated with a service subscription level, receiving, by the base station from the quality of experience manager, an updated quality of service profile for the first service class
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: determine, by a base station, a congestion level for a cell; receive, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class; determine one or more flow events for the user device flow; send, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device
  • identification information that identifies the user device, the user device being associated with a service subscription level; receive, by the base station from the quality of experience manager, an updated quality of service profile for the first service class; send, by the base station to the user device based upon the updated quality of service profile for the first service class, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising: determining, by a base station, a congestion level for a cell; receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class; determining one or more flow events for the user device flow; sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow;
  • identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device identification information that identifies the user device, the user device being associated with a service subscription level; receiving, by the base station from the quality of experience manager, an updated quality of service profile for the first service class; sending, by the base station to the user device based upon the updated quality of service profile for the first service class, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • a method may include receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell, receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network, receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows, determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows, and sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network; receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows; and sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network; receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows; and sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • a method may include receiving, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell, receiving service subscription level information that identifies a service subscription level for one or more user devices within the cell, receiving, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes, determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes, and sending, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell; receive service subscription level information that identifies a service subscription level for one or more user devices within the cell; receive, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes; determine, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes; and send, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • a computer program product may include a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the cell; receiving, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes; and sending, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • FIG. 1 is a diagram of a network according to an example implementation.
  • FIG. 2 is a diagram of a network according to another example
  • FIG. 3 is a block diagram illustrating a user device (or UE) and a base station (or RAN node) according to an example implementation.
  • FIG. 4 is a flow chart illustrating operation of a base station according to an example implementation.
  • FIG. 5 is a flow chart illustrating operation of a base station according to another example implementation.
  • FIG. 6 is a flow chart illustrating operation of a quality of experience manager according to an example implementation.
  • FIG. 7 is a flow chart illustrating operation of a quality of experience manager according to another example implementation.
  • FIG. 8 is a block diagram of a wireless station (e.g., BS or user device) according to an example implementation.
  • a wireless station e.g., BS or user device
  • RAN radio access network
  • a RAN node such as a base station (BS), eNB, or Access Point (AP)
  • BS base station
  • eNB eNode
  • AP Access Point
  • QoE manager e.g., to allow the QoE manager to calculate or determine updated QoS policies for one or more user devices, user device flows (e.g., application flows or service flows), or classes of service (service class).
  • an improved QoE may be accomplished by a QoE manager, which may be provided at a core network, as part of a cloud-based service, or other location.
  • the QoE manager may receive information, such as cell loading or cell congestion information for one or more cells, flow events for one or more user device flows for one or more cells, an indication of a type of application or class of service (also known as service class) of an application that is generating the flow events, a service subscription level for each of the user devices of one or more cells, and/or other information.
  • Updated QoS policies may be determined by the QoE manager, e.g., based on the information.
  • the QoE manager may determine updated user device specific QoS policies (e.g., different QoS policy for each user device), updated flow-specific QoS policies (e.g., a different QoS policy for each application flow/service flow), or updated QOS policies for each class of service/service class.
  • updated user device specific QoS policies e.g., different QoS policy for each user device
  • updated flow-specific QoS policies e.g., a different QoS policy for each application flow/service flow
  • updated QOS policies for each class of service/service class.
  • the QoE manager may receive a cell congestion value indicating that a cell is congested or overloaded, e.g., wherein requests or need for resources from user devices or user device flows may be greater (e.g., significantly greater) than existing wireless/radio resources.
  • the QoE manager may be able to determine the existing/active flows (based on the flow events), the approximate resource needs for each flow (e.g., based on application type or class of service/service class for flow), and the service subscription level (e.g., premium service, or regular service) of each user device.
  • the QoE manager may (at least temporarily) adjust the QoS policies of one or more user device flows to, e.g., allocate a greater percentage of available wireless resources in the congested cell to user device flows for user devices that have a premium (or high priority) service subscription level, and allocate a lower percentage (or possibly even little or no resources) to flows of user devices that have a regular (or low priority) service subscription level.
  • the QoE manager may send the updated QoS policies to the base station or cell.
  • the base station or cell may then forward instructions or even the updated QOS policies to one or more of the user devices to cause one or more user devices in the congested cell to adjust an uplink data rate for one or more flows (application flows or service flows of the user device) or classes of service/service classes.
  • the base station may determine a congestion level for a cell, e.g., based on a buffer status for one or more transmission buffers for one or more user devices or user device flows, a packet drop rate for one or more user devices or flows, a packet delay or latency, and/or other factors.
  • the BS may also detect one or more flow events for user device flows within the cell.
  • a user device flow may include, for example, an application flow of data (e.g., including data generated by an application running on the user device) between an application and a core network via the cell, or a service flow of data (e.g., including data generated by a service running on the user device) between the service or the user device and the core network via the cell.
  • Flow events may include any event associated with the flow, such as, for example, activation (or initiation) of a new flow, modification of a flow (which may include modification by the user device of a QoS parameter or QoS policy implemented by the user device for transmission of data for the flow), and termination (or ending) of the flow.
  • the QoE manager may also receive an application identification information (e.g., such as a traffic flow template for the flow) that may identify the user device flow and/or identify the application at the user device that is generating the user device flow, and user device identification information that identifies the user device.
  • an application identification information e.g., such as a traffic flow template for the flow
  • Each user device may have or may be associated with a service subscription level (e.g., gold service, silver service and bronze service, or premium service and regular service) for a wireless network.
  • the QoE manager may, for example, adjust QoS policies to allocate more (or a higher percentage of) resources to higher priority service subscription levels, and allocate less resources to lower priority service subscription levels, e.g., so that the expected performance or wireless experience provided to flows (e.g., a VoIP flow for a Voice over IP call) of premium level/high priority user devices is maintained even in periods where the cell may become congested.
  • QoS policies may be adjusted to allocate more (or a higher percentage of) resources to higher priority service subscription levels, and allocate less resources to lower priority service subscription levels, e.g., so that the expected performance or wireless experience provided to flows (e.g., a VoIP flow for a Voice over IP call) of premium level/high priority user devices is maintained even in periods where the cell may become congested.
  • a greater percentage of resources may be allocated to a first VoIP flow for a high priority user device, e.g., to maintain the required data rate and latency requirements for the first VoIP flow, while reducing data rate for a second VoIP flow for a low priority user device, which may cause the performance of the second VoIP flow at the low priority user device to suffer.
  • This is merely one illustrative example.
  • a central QoE manager which may receive congestion information from multiple cells, and which may retrieve service subscription level information for each user device from the core network, may make system level decisions in terms of allocation of resources, and may make handover recommendations, e.g., QoE manager may recommend that a high priority user device perform a handover from a congested cell to an uncongested cell. Also, the QoE manager may not make a similar recommendation for handover for a low priority user device, so that a higher performance level or higher quality of experience may be maintained for the higher priority device (e.g., QoE manager prioritizing the higher priority user device for handover to a less congested cell), for example.
  • the QoE manager may determine the uplink resource requirements/needs for each user data flow, e.g., based on the flow events, the type of application or class of service/service class for the flow, and the service subscription level for the user device, and/or other factors. In the event that a cell becomes congested, e.g., where there are more requests for resources than there are available resources in the cell, then the QoE manager may determine updated QoS policies for each user data flow, each user device, and/or for each class of service/service class within the cell.
  • the QoE manager may determine one or more updated QoS policies (e.g., including one or more QoS parameters, such as minimum bit rate, maximum latency, packet drop policy, ...) based on, for example, the cell congestion level, the flow events from one or more user device flows, the service subscription levels of one or more user devices within the cell, and/or other factors.
  • the QoE manager may know or be able to determine a current status of a cell, taking into account cell load/congestion, flow status (e.g., activated or not), and resource
  • the QoE manager may adjust one or more QoS policies, e.g., to increase the amount or percentage of resources within a cell allocated to user devices or user device flows having a premium service level, while decreasing the amount or percentage of cell resources allocated to user devices or user device flows having a lesser (e.g., regular) service subscription level, in the event the cell becomes congested.
  • the QoE manager may then send the updated QoS policies to the BS or cell, and the BS may provide instructions (or may send the QoS policy) to one or more user devices to cause the user device adjust an uplink data rate of one or more user device flows or classes of service/service classes.
  • a technique may include a base station determining a congestion level for a cell, receiving, from a user device, data associated with a user device flow from the user device, determining one or more flow events for the user device flow, sending, from the base station, information, including the congestion level and the one or more flow events, to a quality of experience (QoE) manager to allow the quality of experience manager to determine one or more updated quality of service (QoS) profiles for the user device.
  • QoE quality of experience
  • QoS quality of service
  • the technique may also include receiving, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow, sending, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to the user device to cause the user device to adjust an uplink data rate of the user device flow.
  • a technique may include receiving, from one or more cells in a wireless network: cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell, a service subscription level information that identifies a service subscription level for one or more user devices within the wireless network, and user device flow event information that indicates events associated with one or more user device flows (e.g., application flows or service flows).
  • cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell
  • service subscription level information that identifies a service subscription level for one or more user devices within the wireless network
  • user device flow event information that indicates events associated with one or more user device flows (e.g., application flows or service flows).
  • the technique also includes determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service (QoS) policy for each of one or more of the user device flows, and sending, to one or more of the cells, an updated quality of service (QoS) policy for one or more user device flows.
  • QoS quality of service
  • a base station in a fifth generation wireless mobile system (5G) or other wireless communication system or network may monitor and/or determine whether user devices and the network are meeting Quality of Experience (QoE) requirements for numerous concurrent application flows and/or service flows with different Classes of Service
  • QoE Quality of Experience
  • CoS /service classes based on monitoring the uplink data transmissions, and/or buffer status reports, that the base station receives from the user devices.
  • the base station may monitor whether the user device and/or the network are meeting a first quality of service (QoS) policy associated with a first application, first application type (which may include one or more similar applications), and/or first class of service (CoS)/service class, whether the user device and/or the network are meeting a second QoS policy associated with a second application, second application type, and/or second CoS, or any number of QoS policies, applications, application types, or CoSs.
  • An application type may include applications with similar purposes and/or functions, such as voice (e.g.
  • Voice over Internet Protocol / VoIP Voice over Internet Protocol / VoIP applications, video applications, text applications, Web browsers, or data applications.
  • the user device(s) may insert into packets identifiers of the application, application type, and/or CoS associated with the packets, and/or the packets may include identifiers of the application, application type, and/or CoS associated with the packets.
  • the base station may monitor whether the user device and/or network are meeting QoS policies for applications, application types, and/or CoSs based on average packet sizes of received data associated with the respective applications, application types, and/or CoSs, based on average frequencies of receiving packets of received data associated with the respective applications, application types, and/or CoSs, based on comparing times of receipt of packets associated with the respective applications, application types, and/or CoSs to QoS requirements for the respective applications, application types, and/or CoSs, based on determining a data rate for the respective applications, application types, and/or CoSs based on receiving packets associated with and/or identifying the respective applications, application types, and/or CoSs, based on determining latencies for the respective applications, application types, and/or CoSs, and/or based on determining latencies of service for the respective applications, application types, and/or CoSs.
  • the related bearer and session management signaling between the core network, base station and the user devices within the network may be reduced. This reduction in bearer/session
  • management signaling may allow additional communication resources to be assigned and/or scheduled for data communication in the network.
  • the base station may communicate with each of the user devices via a single Ethernet-like link layer point-to-point connection, which may be wireless, with variable data capacity, per user device.
  • the base station may establish and maintain a single adaptive connection with each of the user devices within the wireless network, increasing and decreasing the uplink data communication resources and/or uplink wireless resources for each user device within the adaptive connection, rather than maintain multiple dedicated radio bearers per CoS with each user device.
  • the communication resources may include time slots and/or frequency slots or bands via which the user devices send data to the base station.
  • the user devices may each prioritize the uplink traffic according to a set of its configured QoS policy data to identify the individual and concurrent application and/or service flows in uplink at the upper protocol layers (L3 and above) and map these to multiple priority queues/transmission buffers at the data link and physical layers of the radio link connection (L2 and L1 ), such as two or more queues/buffers, each queue/buffer being associated with a different application, application type, CoS, service flow, and/or application flow and having different QoS requirements.
  • a set of its configured QoS policy data to identify the individual and concurrent application and/or service flows in uplink at the upper protocol layers (L3 and above) and map these to multiple priority queues/transmission buffers at the data link and physical layers of the radio link connection (L2 and L1 ), such as two or more queues/buffers, each queue/buffer being associated with a different application, application type, CoS, service flow, and/or application flow and having different QoS requirements.
  • the base station may perform predictive uplink radio scheduling based on uplink buffer status reports received from the user devices in a fast control loop, assigning more uplink data communication resources to user devices with large amounts of data in their queues and/or more full queues and less uplink data communication resources to user devices with lower amounts of data in their queues and/or less full queues, according to an example implementation.
  • the base station may also be configured with QoS policy data to identify the individual and concurrent application and/or service flows at the upper protocol layers (L3 and above) in order to provide a dynamic uplink flow control for the user devices based on the application and/or service flow aware monitoring in a slow control loop, in which the base station monitors and/or determines whether the user devices are meeting the QoS
  • This flow control function in the base station may also be capable to adjust dynamically the uplink data rate control function in the user equipment with accuracy of an individual application flow and/or service flow at the upper protocol layers.
  • the base station may instruct the user device to adjust an uplink data rate of an application flow and/or service flow by instructing the user device to adjust the uplink data rate of the application flow at an upper application protocol layer associated with the application, application type, and/or CoS based on the monitoring whether the user device and/or network is meeting the QoS policy for the application, application type, and/or CoS.
  • a service flow and/or application flow adjusted by the base station may be identified by traffic flow template (TFT) filtering rules.
  • TFT traffic flow template
  • the base station may monitor whether the user device is meeting quality of service policies associated with applications, application types, and/or CoSs by monitoring data received via application protocol layer flows associated with the applications, application types, and/or CoSs.
  • the base station may determine whether and/or which application protocol layer a packet and/or data is associated with based on a TFT.
  • the base station may also perform admission control by monitoring the current network load including data still to be sent based on the uplink buffer status reports to determine whether sufficient communication resources are available to admit new user devices. Switching functions in the base station and user devices may enable port-based forwarding, virtual local area network (VLAN) tagging, and/or TFT filtering rules.
  • VLAN virtual local area network
  • the TFT filtering rules may be based on and/or match fields including source address (which may include a subnet mask), Internet Protocol protocol number (such as Transmission Control Protocol (TCP) or Uniform Datagram Protocol (UDP)), destination port range, source port range, Internet Protocol Security (IPSec) Security Parameter Index (SPI), Type of Service (TOS) (for IPv4), Flow-Label (for IPv6), source Ethernet Medium Access Control (MAC) address, Ether-type number (such as a protocol carried in the Ethernet frame including IPv6 or IPv4), CoS, and/or VLAN identifier.
  • source address which may include a subnet mask
  • Internet Protocol protocol number such as Transmission Control Protocol (TCP) or Uniform Datagram Protocol (UDP)
  • IPSec Internet Protocol Security
  • SPI Security Parameter Index
  • TOS Type of Service
  • MAC Medium Access Control
  • Ether-type number such as a protocol carried in the Ethernet frame including IPv6 or IPv4
  • CoS CoS
  • the TFT may be a classifier that matches fields in packets (such as IP packets and/or Ethernet frames) generated and/or sent by the user device, and/or received by the base station.
  • the user device may include an internal packet data router function, and/or an internal multilayer switch function that supports port-based forwarding, that performs flow detection, such as IP flow detection and/or Ethernet flow detection, based on TFTs configured in the user device, and routes matching uplink packets to multiple, such as four, queues and/or buffers in the user device.
  • the multiple queues and/or buffers that store packets based on the TFTs may be considered transmission buffers with different priority levels.
  • the user device may transmit the packets stored in the queues and/or buffers to the base station via the scheduled uplink wireless resources.
  • the user devices may be connected (and in communication) with the base station, which may also be referred to as an access point (AP) or an enhanced Node B (eNB).
  • AP access point
  • eNB enhanced Node B
  • At least part of the functionalities of a base station or (e)Node B may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • the base station may provide wireless coverage within a cell or wireless network, including to the user devices.
  • the base station may also be connected to a core network via an interface such as an S1 interface and/or base station controller. This is merely one example of a wireless network, and others may be used.
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, a mobile station, a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, or a multimedia device, as examples.
  • SIM subscriber identification module
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • FIG. 1 is a diagram of a network 100 according to an example embodiment.
  • the network 100 may include a wireless network, such as a wireless infrastructure network.
  • the network 100 may include a wireless infrastructure network in which a base station 102 communicates with, and assigns communication resources to, multiple user devices 104A, 104B, 104C.
  • the network 100 may include a cellular network, such as a fifth generation wireless mobile system (5G) network or a Long-Term Evolution (LTE) or LTE-Advanced network. While three user devices 104A, 104B, 104C are shown in FIG .1 , any number of user devices 104A, 104B, 104C may be included in the network 100.
  • the base station 102 may forward data between the user devices 104A, 104B, 104C and a User-plane Gateway 106, base station controller, mobile switching center, gateway, and/or other upstream nodes in a packet network.
  • the user devices 104A, 104B, 104C may generate and send data in an uplink direction to the base station 102 in a form of packets (e.g., packets or frames) using uplink data communication resources and/or uplink wireless resources that the base station 102 assigned to and/or scheduled for the respective user device 104A, 104B, 104C.
  • the data may originate from applications running on the user devices 104A, 104B, 104C, and/or may originate from wireless nodes 108A, 108B in communication with one of the user devices 104C.
  • the base station 102 may also send data in a downlink direction to the user devices 104A, 104B, 104C.
  • the base station 102 and user devices 104A , 104B, 104C may also send control signals to each other, such as uplink maps, buffer status messages, requests for additional uplink communication resources, and instructions to adjust uplink data rates for particular CoSs.
  • the base station 102 may have established point-to-point links with each of the user devices 104A, 104B, 104C.
  • the data may be sent and received according to the Internet Protocol (IP), and may be encapsulated within Ethernet (IEEE 802.3) frames, for example.
  • IP Internet Protocol
  • IEEE 802.3 Ethernet
  • Each of the applications (or application flows or service flows) running on the user devices 104A, 104B, 104C and generating data may have its own quality of service (QoS) requirements, such as a minimum data rate and/or a maximum latency, packet drop rate policy, or other QoS parameter.
  • QoS quality of service
  • the user devices 104A, 104B, 104C may each be configured with QoS policy data to identify the individual and concurrent application flows and/or service flows in uplink at the upper protocol layers (L3 and above) and map or group the applications into classes of service (CoSs) or service classes, such as a first CoS (or first service class) and a second CoS (or a second service class), or any number of CoSs.
  • the user devices 104A, 104B, 104C may group applications with similar QoS requirements into same classes of service/service classes.
  • the user devices 104A, 104B, 104C may, for example, group applications with same or similar data rate and/or latency requirements into a same CoS.
  • the CoS/service class may have QoS requirements based on the best QoS requirement for the applications in each category/CoS (or service class), such as the highest data rate requirement of all the applications in the CoS and the lowest latency requirement of all the applications in the CoS, to ensure that all of the applications in the CoS meet their QoS requirements.
  • Each of the user devices 104A, 104B, 104C may perform data rate control for each identified application flow and/or service flow in uplink at the upper protocol layers and maintain a queue or buffer for storing the data packets while the data rate control function determines based on the QoS policy data when packets in each application and/or service flow should be put into the actual priority queues or transmission buffers.
  • the priority queue or transmission buffer may store packets in the CoS that include data and are ready for uplink transmission over the radio link to the base station 102.
  • the user devices 104A, 104B, 104C may determine which priority queues or buffers, such as the first priority queue or buffer or the second priority queue or buffer, from which to send packets to the base station 102.
  • the user devices 104A, 104B, 104C may determine which priority queues or transmission buffers from which to send packets in each scheduled transmission block over the radio link based on their associated priority in an attempt to meet the QoS requirements of the applications in each CoS.
  • the user devices 104A, 104B, 104C may also adjust their data rate control functions for their identified application and/or service flows in uplink at the upper protocol layers based on a quality of service instruction for a flow control received from the base station 102.
  • the quality of service instruction for a flow control may, for example, instruct the user device 104A, 104B, 104C to adjust an uplink data rate or transmission rate for a particular application and/or service flow, such as to increase a transmission rate of packets to meet the QoS requirements for one or more applications in that CoS, or decrease a transmission rate of packets for an application flow and/or service flow to enable packets in other CoSs to meet the QoS requirements for applications in those CoSs, or to throttle an application flow and/or service flow exceeding its maximum data rate in uplink.
  • the user devices 104A, 104B, 104C may each send at least one buffer (also referred to as a buffer status) signal to the base station 102.
  • the user devices 104A, 104B, 104C may send the buffer signals to the base station 102 periodically in order to let the uplink radio scheduler in the base station 102 decide the required radio resources for each user device 104A, 104B, 104C.
  • the buffer signals may each indicate a level of fullness of each or all of the transmission buffers or priority queues in the user device 104A, 104B, 104C that sent the buffer signal, or the buffer signals may each indicate a level of fullness of one of the buffers or queues in the user device 104A, 104B, 104C that send the buffer signal.
  • the base station 102 may base the uplink radio scheduling at least in part on the received buffer signal(s).
  • the base station 102 may assign uplink data communication resources and/or uplink wireless resources to one or more of the user devices 104A, 104B, 104C.
  • the base station 102 may also monitor whether the one or more user devices 104A, 104B, 104C are meeting the QoS requirements and/or QoS policies for the application, application type, CoS, service flow, and/or application flow in one, two, or more of their CoSs.
  • the base station 102 may monitor whether the one or more user devices 104A, 104B, 104C are meeting the QoS requirements for their CoSs and/or QoS policies based on the data received from the user devices 104A, 104B, 104C in the CoSs via the assigned uplink data communication resources, and/or based on the buffer signals received from the user devices 104A, 104B, 104C.
  • the base station 102 may determine whether the QoS requirements for application and/or service flows are being met based on packets that the base station 102 receives from the user devices 104A, 104B, 104C for forwarding to their next hop destination from the base station 102, e.g., to a User-Plane Gateway 106.
  • the base station 102 may, for example, compare times of receipt of packets in a application and/or service flow to the QoS parameters in the policy data, determine a data rate for an application flow and/or service flow, or determine a latency for an application flow and/or service flow based on receiving packets in the application and/or service flow.
  • the base station 102 may also determine whether the user devices 104A, 104B, 104C will meet quality of service requirements for application flows and/or service flows for future transmissions based on the levels of fullness of the priority queues or transmission buffers for the CoSs.
  • the base station 102 may, for example, determine that a transmission buffer or priority queue for a CoS, or multiple buffers or queues for multiple CoSs, are too full for the user device 104A, 104B, 104C to be able to meet QoS requirements of the CoS(s).
  • the base station 102 may adjust the assigned uplink data communication resources, such as by assigning and/or scheduling additional uplink data communication resources and/or additional uplink wireless resources in the radio scheduler, and/or instruct the user device 104A, 104B, 104C to adjust an uplink data rate of a particular application and/or service flow or multiple application flows and/or service flows at the upper protocol layers, to meet the QoS of the CoS or CoSs.
  • the user device 104A, 104B, 104C may detect launching a new application flow in the user device with help of packet inspectionand comparing packets against the TFT filtering rules configured in its QoS policy data.
  • the user device may request QoS policy modification from the network in case the CoS requirements for a new application and/or service flow are not included in the existing policy data stored in the user device and in the base station.
  • the network may verify from a subscription database whether the user device is authorized to get its new requested service.
  • a network initiated QoS policy modification/addition may occur in which the base station may detect launching/initiating of a new application flow from the user device based on packet inspection of data received from the user device.
  • the base station may log the occurrence of a new flow event (e.g., activation or initiation of a new flow) and then send a flow event to the QoE manager 110, and the QoE manager may decide to add a policy rule for a new application, etc., or QoE manager 110 may adjust/update QoS policies for one or more flows or service classes based on the anticipated/estimated additional traffic demands on the cell by this new application flow, for example.
  • a new flow event e.g., activation or initiation of a new flow
  • QoE manager 110 may adjust/update QoS policies for one or more flows or service classes based on the anticipated/estimated additional traffic demands on the cell by this new application flow, for example.
  • the base station 102 can determine whether the QoS requirements for the application flows and/or service flows are being met without the user devices 104A, 104B, 104C sending to the base station 102, and without the base station 102 receiving from the user devices 104A, 104B, 104C, any message indicating whether QoS requirements being met.
  • the base station 102 and user devices 104A, 104B, 104C need not establish any radio bearers to communicate QoS performance related changes desired in the user devices.
  • the base station 102 may also send on demand an instruction to a user device 104A, 104B, 104C instructing the user device 104A, 104B, 104C to change a policy for a CoS or for a user device flow (application flow or service flow).
  • the base station 102 may instruct the user device 104A, 104B, 104C to change the policy including changing a minimum data rate and/or a maximum latency, or other QOS parameter for the CoS or flow, and/or may instruct the user device 104A, 104B, 104C to change the policy by adjusting packets sizes of packets in an application flow associated with an application, application type, and/or CoS.
  • the base station 102 may instruct the user device 104A, 104B, 104C to change the policy based on the base station 102 determining that the user device 104A, 104B, 104C is not meeting QoS requirements for every application in the CoS, or based on determining that QoS requirements for the CoS are preventing the user device from meeting QoS
  • Network 100 in FIG .1 also include a quality of experience (QoE) manager 110, e.g., to manage the QoS policies used by each user device flow (e.g., application flow or service flow) or class of service (CoS)/service class.
  • QoE quality of experience
  • CoS class of service
  • QoE manager 110 may receive information from one or more cells or base stations, including a cell congestion value that indicates a level or amount of traffic/data congestion at the cell, flow event information from one or more cells or base stations that identifies one or more events for one or more user device flows (e.g., application flows or service flows), identification information for one or more user devices, which may identify one or more of: the user device, one or more user device application/service flows running on the user device, or the application/service running on a user device that generated the flow events, and/or other information.
  • the QoE manager 110 may also receive or obtain (e.g., either from each base station, or from the core network) a service subscription level for each user device or subscriber.
  • the QoE manager 110 may determine one or more updated QoS policies for one or more user devices.
  • the QoS policies may be user device-specific QoS policies, user device flow-specific QoS policies (e.g., policies specific to each application/service flow of a user device), or QoS policies specific to each class of service/service class.
  • the updated QoS policies may be sent to the cell(s) or base station(s).
  • Each cell or base station may then then send instructions (such as a QoS policy that is specific to the user device, a user device flow(s), or class of service for the user device) to one or more user devices, e.g., to cause the user device to adjust the uplink transmission rate or uplink data rate for the associated flow or class of service/service class to the cell or base station.
  • instructions such as a QoS policy that is specific to the user device, a user device flow(s), or class of service for the user device
  • a subscriber and application specific QoE solution for Mobile Broadband Access networks may be provided that takes advantage of the application/service flow aware QoS control function that is run locally in the RAN nodes (radio base stations) and that operates based on a QoS policy (or QoS policy data) configured by a centralized QoE management system/QoE manager 110, which may be located in the core network, provided as part of a cloud service, or other location.
  • a QoS policy or QoS policy data
  • QoE manager 110 may dynamically control the use of radio resources in the service aware RAN nodes, e.g., base stations or 5G Access Points.
  • the RAN nodes e.g., base stations or 5G access points
  • the RAN nodes may, for example, perform user-plane data packet inspection (e.g., stateless packet inspection/SPI or deep packet inspection/DPI) to detect uplink user-plane data or traffic, detect flow events (e.g., based on a TFT for one or more received uplink packets), and may report this information to the QoE manager 110, and then may adjust the operation of user device/end-user application/service flows based on instructions or QoS policies received from the QoE manager 110.
  • user-plane data packet inspection e.g., stateless packet inspection/SPI or deep packet inspection/DPI
  • flow events e.g., based on a TFT for one or more received uplink packets
  • one or more of the RAN nodes may have one or more, or even all, of the following characteristics:
  • ⁇ Implements a "hybrid" radio scheduling having feedback control loop both at Link Layer (fast L2 control loop) and at the upper layers (L3 and above slow control loop, or "slow outer control loop” in L2) by implementing a Flow Control function where the service flow aware metering function in the RAN node does not only give the usual token bucket feedback to the radio scheduler at the user device but shall also be capable to communicate using control signalling at the upper layer (L3) with the service flow aware data rate control function of the user device/UE.
  • the QoS over the radio link may be operating based on the operator/QoE manager-provided policies configured in the RAN nodes to cover all served user devices and optionally with subscriber/user device-specific policies that are configured by the QoE manager 110 based on cell load/congestion, flow events/traffic, and other information.
  • ⁇ Implements a real-time data-logging function for the application/service flow related events over the radio link connection.
  • ⁇ Implements a control-plane interface using multicasting to report RAN node and user device specific events (such as flow events, cell congestion, etc.) in real time to the QoE management system e.g., to QoE manager 110 in the operator's network.
  • QoE management system e.g., to QoE manager 110 in the operator's network.
  • ⁇ Implements a control-plane interface to receive feedback from the centralized QoE management system, e.g., QoE manager 110, in order to allow the QoE manager 110 alter dynamically the operator, subscriber and application/service flow related policies in the RAN node/BS depending on the overall network resource usage situation.
  • QoE management system e.g., QoE manager 110
  • each RAN node may typically report Cell load information/cell congestion value (e.g., based on buffer status reports from user devices) and cell identification/cell ID to the centralized QoE management system or QoE manager 110, so the QoE manager 110 can resolve or determine the impacted user devices/UEs.
  • a RAN node e.g., base station, eNB, or 5GAP
  • the flow event information may, for example, be sent as multicast message(s) including information about the user's ID (e.g., user device ID, subscriber ID, or mobile station identifier/ID), the user's (or user device's) service subscription level/class, the type of application or the type of content, which may be identified by the base station/RAN node providing a a TFT (Traffic Filtering table) from which the QoE manager 110 can determine the type of application that is generating data for the user device flow and thus allow the QoE manager 110 to estimate the resource usage or resource requirements for each user device flow (e.g., application/service flow), class of service/service class, or for the user device overall which may include multiple flows running on the user device.
  • TFT Traffic Filtering table
  • the QoE manager 110 may be located in the core network, or may be a service provided in the cloud or as a cloud-based service and may be capable of Big Data analysis.
  • the QoE manager e.g., for LTE or other systems, may support congestion mitigation functions that are used to control the
  • a system is provided with a number of QoE features or enhancements, such as, for example:
  • the optimization of QoS policies in order to support overall QoE management may operate so that it takes into account also the real time event reports (e.g., flow event reports) received from the RAN nodes/base stations that include information about individual application/service flows for a single impacted user device/UE/subscriber.
  • real time event reports e.g., flow event reports
  • the centralized QoE management system/QoE manager 110 may dynamically calculate and modify the QoS policies for user devices (e.g., for application/service flows or classes of service/service classes) within the impacted/congested cells/RAN nodes. In this manner, the QoE manager may adjust one or more QoS policies for impacted user devices, flows or classes of service, e.g., the QoE manager 110 may adjust the radio resource usage per class of service, or adjust the radio resource usage for each application/service flow, or user device flow, for a single impacted UE/subscriber/user device.
  • the centralized QoE management system/QoE manager 110 may transmit the QoS policies to a RAN node/base station over a data oriented control-plane interface with messages indicating the user's ID (or user device ID) and the modified QoS policy rules, e.g., in form of TFT entries and their corresponding QoS parameters.
  • the RAN node or base station may also adjust its QoS treatment to operate based on the current QoS policy data that it has received from the centralized QoE management system/QoE manager 110.
  • RAN nodes may include application/service flow aware flow control function, and the RAN node/BS and the operation of its user devices and user device flows within the cell, may be adjusted dynamically by the QoE manager 110 determining and providing updated/adjusted QoS policies for each user device, class of service/service class or each user device flow (e.g., application flow or service flow), depending on the overall network resource usage situation (e.g., flow events/flow demands for each user device, cell congestion, service subscription levels for each user device or user device flow, and other network or resource usage information) in real time.
  • the QoE manager 110 determining and providing updated/adjusted QoS policies for each user device, class of service/service class or each user device flow (e.g., application flow or service flow), depending on the overall network resource usage situation (e.g., flow events/flow demands for each user device, cell congestion, service subscription levels for each user device or user device flow, and other network or resource usage information) in real time.
  • FIG. 2 is a diagram of a network according to another example
  • the network may include two network portions or subnetworks, including a radio access network (RAN) 121 and a core network 123.
  • RAN 121 may include one or more RAN nodes or base stations (BSs) and one or more user devices or user equipments (UEs) per cell/BS.
  • Each RAN node or base station (BS) may provide wireless services to one or more user devices via one or more cells.
  • RAN node/BS 102 may provide wireless services via cell 143A (serving UEs 141 A, 141 B), and cell 143B (serving UEs 141 C, 141 D).
  • QoE manager 110 and other blocks are provided as part of the core network 123.
  • RAN nodes/BSs 102 may be service aware, e.g., the RAN nodes/BSs 102 may inspect packets or frames of received uplink data received from user devices, e.g., to detect one or more fields associated with a TFT, in order to detect flow events, for one or more flows and/or user devices. Based on this data (e.g., packet or frame) inspection, RAN nodes/BSs 102 may perform service aware flow control, such as service aware congestion mitigation functions including bandwidth limitation, prioritization and traffic gating over the radio link connections 142 according to the provided policies.
  • service aware flow control such as service aware congestion mitigation functions including bandwidth limitation, prioritization and traffic gating over the radio link connections 142 according to the provided policies.
  • each user device 141 may use an initial or default QoS policy for each application/service flow or class of service/service class.
  • the RAN node/BS 102 may perform packet/frame inspection of data received from one or more user devices/UEs 141 , e.g., to detect flow events for one or more flows. RAN node/BS 102 may then report these flow events to the QoE manager 1 10 via line or interface 1 1 1 .
  • RAN node/BS 102 may detect an activation of a new user device flow (e.g., application flow or service flow) by detecting application or flow identification information, such as by receiving a TFT (including one or more fields that may identify the application or the flow) for a new flow, e.g., a new source /destination IP address pair in a header (or other field or set of fields of the TFT) of a received uplink data frame/packet that is for the new flow, and e.g., does not match any existing flows.
  • a new user device flow e.g., application flow or service flow
  • detecting application or flow identification information such as by receiving a TFT (including one or more fields that may identify the application or the flow) for a new flow, e.g., a new source /destination IP address pair in a header (or other field or set of fields of the TFT) of a received uplink data frame/packet that is for the new flow, and e.g.,
  • RAN node/BS 102 may detect a termination of an application/service flow when the RAN node/BS 102 does not detect any data (e.g., frames/packets) with fields that match the TFT of the flow for at least a threshold period of time. If at least a threshold period of time passes after the last uplink data is received for a flow, then the RAN node/BS 102 may assume that the flow has ended or been terminated, according to an example implementation.
  • RAN node/BS 102 may receive an explicit notification of flow termination from the user device or core network 123. RAN node/BS 102 may generate a log of these flow events (flow event information).
  • Each RAN node/BS 102 may send or report the flow event information to the QoE manager 1 10, e.g., to inform the QoE manager 1 10 of which flows are active, and to identify the application that is generating the flow, e.g., so that the RAN node/BS 102 may determine or estimate the uplink resource needs or requirements for each of the flows for each user device and/or to estimate a total/cumulative uplink RAN resources needed for a cell or BS.
  • RAN node/BS 102 may send the flow event information, e.g., including one or more of the following: event identification (e.g., indicating flow activation, modification or termination), a cell ID that identifies the cell where the event was detected, an application (or flow) identification information (e.g., TFT for the flow), a user device ID that identifies the user device from which the flow/data originated, and/or other information.
  • event identification e.g., indicating flow activation, modification or termination
  • cell ID that identifies the cell where the event was detected
  • an application (or flow) identification information e.g., TFT for the flow
  • user device ID e.g., TFT for the flow
  • each RAN node/BS 102 may receive a buffer report (or buffer status report) from one or more user device/UE, where the buffer report/buffer status report may indicate a level of fullness of (or an amount of data stored in the buffer awaiting transmission from) each of a plurality of transmission buffers at each reporting user device/UE.
  • a transmission buffer may be provided for each (or one or more) user device flows (e.g., application/service flows), or for each class of service/service class.
  • Each RAN node/BS 102 may determine a cell congestion value or cell load for a cell based on buffer status reports received from user devices/UEs within or attached to the cell.
  • a higher level of fullness for one or more transmission buffers may indicate a cell load or cell congestion level for the cell. For example, if 90% of the buffers are more than 50% full, then this indicates a backlog of data awaiting uplink resources for transmission to the BS/RAN node, which means there is a high cell load or high cell congestion level at the cell.
  • Other factors may also be used to determine cell load or cell congestion in the uplink direction, e.g., data (e.g., packet or frame) latency, packet drop rate, or other data/factors.
  • a cell congestion level may be determined by each RAN node/BS 102, e.g., based on the buffer status reports from each (or one or more) of the user devices/UEs that report buffer status or other congestion-related information.
  • Each RAN node/BS 102 or cell may report the cell congestion level for the cell to the QoE manager 1 10.
  • a low cell congestion level or low cell load may indicate to the QoE manager 1 10 that there are sufficient resources for all the current user device flows.
  • a high cell load or a high cell congestion level may indicate to QoE manager 1 10 that there are not sufficient resources within the cell for all current user device (e.g.,
  • uplink resources both uplink wireless/radio resources from UE to BS, and uplink resources from BS to core network/gateway
  • uplink resources may be provided (or continue being provided at a greater level than lower priority flows) to some high priority/high service subscription level user device flows, while at the same time possibly reducing the allocation of uplink resources (e.g., uplink UE to BS uplink resources, and/or BS to core network uplink resources) to some lower priority/service subscription level flows.
  • the QoE manager 1 10 may obtain, e.g., from HSS 170, the service subscription level of each or one or more of the user devices.
  • Some example service subscription levels may include a premium (or priority/high priority) service subscription level, which may be more expensive, and may offer better performance level or greater resource allocation, than a regular (or a standard/low priority) service subscription level.
  • higher service level subscriptions may generally receive a greater portion of available network resources (e.g., including UE to BS wireless/RAN resources and/or BS-to-core network resources), as compared to lower service level subscriptions, e.g., in the event that cell load/congestion indicates there are insufficient resources (e.g., uplink resources) to accommodate or meet the needs of all active flows within the cell.
  • available network resources e.g., including UE to BS wireless/RAN resources and/or BS-to-core network resources
  • QoE manager 1 10 may deny (or reduce) resources to one or more flows or classes of service/service classes associated with a user device having a lower service subscription level, e.g., by specifying (via a QoS policy) a lower minimum data rate and/or a higher latency for such lower level/priority subscription flows or classes of service/service classes.
  • the QoE manager 1 10 may allocate a larger portion of available network resources to high priority flows/classes of service, e.g., by specifying via a QoS policy that may include a higher minimum data rate and/or lower latency for flows or classes of service associated with higher service
  • the QoE manager 1 10 may determine updated or adjusted QoS policies (e.g., updated minimum uplink data rate, maximum latency, packet drop policy, or other QoS parameters) for each user device, for each user device flow, and/or for each class of service at a user device, based on all or part of this information (e.g., cell congestion values, flow events, application/flow identification information for each flow, a service subscription level for each user device and/or possibly other information).
  • updated or adjusted QoS policies e.g., updated minimum uplink data rate, maximum latency, packet drop policy, or other QoS parameters
  • the RAN node/BS 102 may perform metering of application/service flow data/traffic to support data traffic scheduling and application/service aware flow control over the radio link connections 142.
  • a RAN node/BS 102 may implement a real-time data-logging function to log or record the application/service flow related events e.g. their activation, modification and termination that occur over the radio/wireless link connection.
  • applications/services e.g., mobile applications in smart phones
  • the application may typically generate a substantial amount of logged flow event data compared to traditional bearer based session management that has been historically been used over cellular wireless networks.
  • each RAN node/BS 102 may receive or collect flow event data (and thus determine the active application/service flows for the cell, and the type of application is generating the flow), cell congestion information/cell congestion values (e.g., based upon buffer status reports from the user devices/UEs), and possibly other data or information, which may then be reported to the QoE manager 1 10.
  • This information may provide the QoE manager 1 10 with a more complete picture of the current status of the uplink traffic demands, including identification of current application/service flows, and the types of applications generating the traffic for each of these flows, resource usage or expected resource requirements for each flow (e.g., based on a type of application which may be determined by the QoE manager 1 10 based on the TFT), and resource demands of existing user device flows or classes of traffic.
  • the QoE manager 1 10 may also obtain the service subscription level for each user device, e.g., so that when a cell uplink resources become congested, the QoE manager 1 10 may adjust the QoS profiles for each flow or class of service/service classes to allocate more resources to flows or classes of service/service classes from user devices having a premium or high priority service subscription level, for example.
  • each RAN node/BS 102 may implement a control-plane interface 1 1 1 using multicasting to report RAN node 102 related events, cell 143 related events, user device 141 related events and transport network interface 153 related events in real time to the QoE manager 1 10.
  • enhanced RAN level functionality and performance may be obtained by RAN nodes/BSs detecting and reporting flow events and cell congestion and other information to the QoE manager 1 10.
  • cell conditions e.g., cell congestion or uplink traffic demands, available uplink resources at the cell, activation or termination of flows, changes in service level subscriptions for one or more user devices, etc.
  • the QoE manager 1 10 may then send these updated/adjusted flow-specific or class of service-specific QoS policies to the RAN nodes/BSs 102, so that each RAN node/BS 102 may then send instructions or the QoS policies to each user device to cause the user devices adjust uplink transmission scheduling and operation (e.g., cause the user devices to adjust uplink data rates for each flow) based on these adjusted/updated flow-specific (or class of service-specific) QoS policies.
  • the HSS Home
  • Subscriber Server 170 may include a database for the subscriber/user device- related information.
  • the QoE manager 1 10 may obtain from the HSS 170 service level subscription for each user device, and stored QoS policy information for the impacted user devices/UEs 141 via the control-plane interface 161 .
  • the PCRF (Policy and Charging Rules Function) 180 is a node designated in real-time to determine QoS policy rules in a network and accesses subscriber database in HSS 170 via the control-plane interface 182 and other specialized functions, such as a charging system, in a centralized manner.
  • information related to calls or resource usage may be provided to PCRF to allow
  • the PCRF 170 On determining the QoS values (QoS parameters) for the requested end-to- end (e-2-e) services, the PCRF 170 passes the QoS values to the PDN GW (Packet Data Network GateWay) 190 by using the control-plane interface 181 .
  • the QoS rules/values may be used to configure the EPS bearer services in the user devices/UEs 141 and the PDN- GW 190 that are further associated to the E-RAB bearer services in RAN node (eNB) 102 and Radio Bearers over the radio link connection 142.
  • eNB RAN node
  • the RAN nodes 102 may typically provide service aware QoS handling over the radio link 142 based on its configured policy rules (e.g., QoS policies/rules) covering a large set of applications and services instead of necessitating to configure (set, modify, release) the traditional bearer services in control of the core network.
  • policy rules e.g., QoS policies/rules
  • a PDN GW packet data network gateway
  • 190 packet data network gateway
  • Such user-plane GW may support congestion mitigation, such as, e.g., bandwidth limitation, prioritization and traffic gating according to the provided QoS policies including TFTs with granularity of a subscriber/UE specific
  • the QoE manager 1 10 may have a control-plane interface 162 to obtain end- user input from the PCRF 180 to be used in its analysis related operations (by analytics block 1 12), which may involve analyzing received data and determining updated/adjusted QoS policies or rules for one or more user device flows/classes of service, for example.
  • QoE manager 1 10 use have a control-plane interface 163 to alter the QoS policy decision rules in the PCRF 180 and another control-plane interface 164 to alter the QoS policy rules in the PDN GW 190, e.g., to perform actions (e.g., actions performed or communicated to other blocks via action block 1 13) according to its analysis.
  • Actions may, for example, include sending (e.g., from action block 1 13 of QoE manager 1 10) one or more updated/adjusted QoS policies for one or more user devices, application/service flows or classes of
  • QoE manager 1 10 may dynamically calculate and modify the QoS policies for the impacted RAN nodes/BSs 102 in which the overall network loading situation, including (in some example implementations)
  • QoS policies may cover or apply to all the served user devices/UEs 141 in the RAN nodes/BSs 102.
  • QoE manager 1 10 may adjust the radio resource usage per class of service type (which may include multiple flows or multiple applications), or may adjust the radio resource usage per user device flow (e.g., per application/service flow) for a single impacted UE/subscriber/user device.
  • the QoE manager 1 10 may transmit updated QoS policies to RAN nodes/BSs 102 via a control-plane interface 152, e.g., to transfer messages to RAN node/BS 102 that contain the user's ID/user device ID and the modified QoS policy/ QoS rules, e.g., which may include for each QoS policy: a TFT (or TFT entry) that may identify the flow, and the corresponding QoS parameters (e.g., updated minimum data rate and maximum latency for the QoS policy).
  • a TFT or TFT entry
  • QoS parameters e.g., updated minimum data rate and maximum latency for the QoS policy
  • FIG. 3 is a block diagram illustrating a user device (or UE) and a base station (or RAN node) according to an example implementation.
  • a user equipment (UE) 310 or user device is in communication with a RAN node or base station (BS) 312.
  • UE 310 may include one or more applications 314, such as applications appM , appl2, appl3, ...appln.
  • Each application 314 may generate one or more application flow 316, which may be a flow of data generated by the application for uplink transmission.
  • UE 310 may include a UE application aware uplink (UL) rate control 318 to adjust the uplink data transmission rate from one or more of the flows 316, e.g., based on flow control signals 319 received from the BS 312 or based on a QoS policy received by the UE 310 from the BS 312, or based on other criteria.
  • UE application aware UL rate control 318 may include, for example, an application service flow recognition block 320 to recognize data (e.g., frames or packets) from different flows, e.g., based on a TFT for each flow, and an application/service flow rate control 322 that adjusts the uplink transmission data rate for each of the flows.
  • UE 310 may also include a UE radio link layer UL scheduling block 324 that performs scheduling of UL data transmissions for one or more flows.
  • a flow classifier 326 classifies each flow into one of a plurality of service classes (or classes of service).
  • a plurality of transmission buffers 328 are provided, e.g., with one buffer being provided to store data for each service class. Data (e.g., frames or packets) from each flow may be classified into one of the service classes and then temporarily stored in a data buffer 328 for the service class, awaiting uplink transmission to BS 312.
  • UE radio link layer UL scheduling block 324 may report buffer status of each transmission buffer, e.g., by sending buffer status reports 329 to BS 312, which may indicate a level of fullness for the transmission buffer for each service class.
  • a flow scheduler 330 may receive grants 331 (e.g., uplink scheduling grants that allow the UE to transmit on UL resources to BS 312) from BS 312. Flow scheduler 330 may then schedule UL data transmissions to BS 312 for each service class or application/service flow (schedule UL transmissions from each transmission buffer), e.g., based on QoS rules, or an updated QoS policy, flow control signals 319, or other instructions, for example.
  • the UL data transmissions are shown in FIG. 3 as packets over radio link 331 .
  • BS 312 includes a BS radio link layer UL scheduler 340 to schedule UL transmissions, including a flow monitoring block 342 that may implement a token bucket flow control, an uplink radio scheduling block 344 that receives buffer status reports 329 and sends resource/scheduling grants 331 to UE 310, a radio link quality monitoring block 346 that detects and/or monitors the radio link quality between the BS 312 and the UE 310 (and to other UEs as well), and a cell load monitoring block 348 that detects or monitors the cell load, and determines a cell congestion value based upon the buffer status reports received from one or more UEs (including from UE 310).
  • a flow monitoring block 342 that may implement a token bucket flow control
  • an uplink radio scheduling block 344 that receives buffer status reports 329 and sends resource/scheduling grants 331 to UE 310
  • a radio link quality monitoring block 346 that detects and/or monitors the radio link quality between the BS 312 and the
  • BS 312 also includes a BS application aware UL flow control 350 including a packet lookup and port forwarding decision block that determines a forwarding
  • Flow monitoring block 356 may output flow control signals 319, e.g., based on QoS policies/QoS parameters for each flow or service class.
  • Flow monitoring block 356 may output data/packets via line 357 to BS data packet relaying block 358, which forwards the data or packets to a BS egress port flow monitoring and transport congestion detection block 360 which monitors congestion and forwards data/packets out via line 361 .
  • a BS QoE reporting function 362 receives flow events and flow identification information from flow monitoring block 356 and/or block 354, cell congestion values for one or more cells from cell load monitoring block 348, and information from block 360.
  • BS QoE reporting function 363 may report flow events and status, and cell congestion values, cell ID, and other information to the QoE manager 1 10 (shown in FIGS. 1 and 2).
  • a BS policy context data manager 364 may receive updated QoS policies for one or more flows or one or more service classes, and these QoS policies or policy rules may be stored in a BS policy context database 366.
  • Each of the applications (or application flows or service flows) running on the user devices / UE 310 supporting 5G access like a 5G User Equipment (UE) and generating data may have assigned its own quality of service (QoS) requirements, such as a minimum data rate and/or a maximum latency, packet drop rate policy, or other QOS parameter.
  • QoS quality of service
  • the UEs may each be configured with QoS policy data with TFTs (Traffic Filtering Templates) to recognize the individual and concurrent application flows and/or service flows in uplink at the upper protocol layers (L3 and above) and map or group the applications into desired number of classes of service (or service classes).
  • TFTs Traffic Filtering Templates
  • the UE 310 may perform Application/Service Flow aware data rate control for each recognized application flow and/or service flow in uplink at the upper protocol layers and maintain a queue or buffer 328 for storing the data packets while the data rate control function 322 determines based on the QoS policy data (received via 319 from BS 312) when packets in each application and/or service flow should be delivered timely to the radio link layer UL scheduling function 324.
  • the Flow Classifier function 326 in the UL radio link layer scheduling function 324 of the UE 310 may group applications with similar QoS requirements into same service class. For example, applications with same or similar data rate and/or latency requirements could be assigned into a same service class.
  • the service class may, for example, have QoS requirements based on the best QoS requirement for the applications in each
  • category/service class such as the highest data rate requirement of all the applications in the Service Class and the lowest latency requirement of all the applications in the service class, to ensure that all of the applications in the service class meet their QoS requirements.
  • the UE radio link layer UL scheduling function 324 shall have priority queues/transmission buffers for the desired number of data traffic types with different Service Class, e.g., Guaranteed Bit Rate (GBR), Real-time, non-Real-time, Best Effort, e.g., one transmission buffer 328 per Service Class.
  • GRR Guaranteed Bit Rate
  • the Flow Classifier function 326 shall direct each data packet to priority queues/transmission buffers 328 that match best with their service class, for example.
  • Each priority queue/transmission buffer 328 stores the uplink data packets in the service class that are ready to be transmitted over the radio link to the base station 312 at the time.
  • the radio link layer UL scheduler function 324 in the UE 310 reports periodically the UL Buffer Status information 329 to the UL radio scheduling block 344 in the base station (BS) 312 in order to allow the UL radio scheduling block 344 or BS 312 to determine the required radio resources for each served user device.
  • the UL Buffer Status signals 329 may each indicate a level of fullness of each or all of the transmission buffers 328 or priority queues in the user device/UE 310 that sent the buffer status signal, or the buffer status signals may each indicate a level of fullness of one of the buffers or queues in the user device that send the buffer status signal.
  • the radio link layer UL scheduler function 324 in the base station may allocate/schedule uplink radio resources for each served UE that are communicating over a shared radio link connection. For example, the radio resource allocation operates based on the received buffer status information and the metered radio link quality from each served UE. The granted uplink radio resources for each UE are informed/identified to the UE via the Grant messages 331 . [00102] Upon each received Grant message 331 , the Flow Scheduler function 330 in the UE may determine which priority queues or transmission buffers 328 from which to send packets in each scheduled transmission block over the radio link based on their associated priority in an attempt to meet the QoS requirements of the applications in each class of service (or service class).
  • the base station 312 may perform Flow Classification and Monitoring for the received data packets in a transmission blocks over the radio link connection in order to implement Token Bucket Scheduling (TBS) based on the configured bucket size duration per class of service flow, metering the class of service/service class flows and adjusting the grant accordingly
  • TBS Token Bucket Scheduling
  • the base station 312 may also monitor all the uplink data received from the served user devices 310 via the assigned uplink data communication resources based on which information the base station can determine the cell loading situation in real-time.
  • the ingress port of the base station internal switch function receives the UL data packets from the radio link layer scheduling functions.
  • the port forwarding decision to the next hop destination of the packet shall be done based on the packet inspection and the configured port forwarding rules.
  • the base station ingress ports from the radio interface may perform packet inspection based application/service flow recognition and session tracking functions.
  • the base station may be configured with similar QoS policy data with TFTs (Traffic Filtering Templates) like in the UE 310 to recognize the individual and concurrent application flows and/or service flows in uplink at the upper protocol layers (L3 and above) and map or group the applications into desired number of classes of service (service classes) and their corresponding QoS parameters.
  • TFTs Traffic Filtering Templates
  • the session tracking function 354 may detect the start and the end of individual application flows (e.g. TCP, RTP etc. connections) that could be used for monitoring the usage of the end user applications like Skype, Youtube, etc.
  • individual application flows e.g. TCP, RTP etc. connections
  • the Application/Service Flow Monitoring function 356 in the base station may determine whether the QoS requirements for application and/or service flows are being met based on packets that the base station receives from the user devices for forwarding to their next hop destination.
  • the base station may, for example, compare times of receipt of packets in a application and/or service flow to the QoS parameters in the policy data, determine a data rate for an application flow and/or service flow, or determine a latency for an application flow and/or service flow based on receiving packets in the application and/or service flow.
  • the Application/Service Flow Monitoring function 356 in the base station may also be capable to communicate (e.g., via flow control signals 319) at the upper layer (L3) with the Application/Service Flow Rate Control function 322 of the UE in order to implement a flow control function over the radio connection that operates with granularity of an individual application/service flow.
  • the UEs may also adjust their data rate control functions 322 at the upper protocol layers for their recognized application/service flows in uplink based on a quality of service instruction for a flow control received from the base station.
  • the quality of service instruction for a flow control may, for example, instruct the user device to adjust an uplink data rate or transmission rate for a particular application and/or service flow, such as to increase a transmission rate of packets to meet the QoS requirements for one or more applications in that Service Class, or decrease a transmission rate of packets for an application flow and/or service flow to enable packets in other Service Classes to meet the QoS requirements for applications in those Service Classes, or to throttle an application flow and/or service flow exceeding its maximum data rate in uplink.
  • the base station 312 may also send on demand an instruction to a user device instructing the user device to change a policy for a Service Class or for a user device flow (application flow or service flow).
  • the base station 312 may instruct the user device to change the policy including changing a minimum data rate and/or a maximum latency, or other QoS parameter for the Service Class or flow, and/or may instruct the user device to change the policy by adjusting packets sizes of packets in an application flow associated with an application, application type, and/or Service Class.
  • the base station may instruct the user device/UE 310 to change the policy based on the base station determining that the user device is not meeting QoS requirements for every application in the service class, or based on determining that QoS requirements for the CoS/service class are preventing the user device from meeting QoS requirements for other service classes and/or applications in other service classes.
  • the outgoing data packets from the base station to the Gateway could be transported by using standard tunneling
  • the Egress Port functions may include flow monitoring and transport congestion detection functions 360.
  • the congestion in the transport network connections in uplink direction can be detected based on monitoring the buffer statuses and dropped packets.
  • the transmission buffer in the network interface is getting full and the switch must drop packets with lower priority according to its configured port forwarding rules in order to avoid buffer overflow.
  • service aware UL Scheduling in 5G UE and 5G Base Station can be enhanced with dynamic QoE control by implementing real time event and status reporting from the 5G BS to a centralized QoE Management System.
  • a centralized QoE manager 1 10 is able to obtain/receive not only the cell loading situation (receive a cell congestion value) in the RAN/BS but has input to determine the overall resource usage with accuracy of a subscriber and their consumed
  • the centralized QoE manager 1 10 may adjust dynamically the QoS Policy data in the 5G BSs 312. This creates kind of the third layer QoE control loop above the radio link layer scheduling and the application/service aware flow control described hereinabove.
  • FIG. 4 is a flow chart illustrating operation of a base station according to an example implementation.
  • Operation 410 may include determining, by a base station, a congestion level for a cell.
  • Operation 420 may include receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device.
  • Operation 430 may include determining one or more flow events for the user device flow.
  • Operation 440 may include sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow.
  • Operation 450 may include receiving, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow.
  • operation 460 may include sending, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • the sending information to the quality of experience manager may include sending, from the base station, information to the quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; application identification information that identifies an application type of an application that generated the flow events for the user device flow; and user device identification information that identifies the user device, the user device being associated with a service subscription level.
  • the determining a congestion level for the cell may include receiving, by the base station from the user device, a buffer status from the user device indicating a level of fullness for one or more transmission buffers, and determining a congestion level for the cell based on at least the buffer status of the one or more transmission buffers of the user device.
  • the user device may include a first user device, wherein the determining a congestion level for the cell comprises: receiving, by the base station, a buffer status from each of a plurality of user devices within the cell, including receiving a buffer status from the first user device, each buffer status indicating a level of fullness for one or more user device transmission buffers; and determining a congestion level for the cell based on the buffer status received from the plurality of user devices.
  • the congestion value may include a radio access node (RAN) congestion information (RCI) that indicates a congestion level of the cell.
  • RAN radio access node
  • RCI congestion information
  • the user device flow may include one or more of the following: an application flow of data between an application running on the user device and a core network via the cell; and a service flow of data between a service running on the user device and the core network via the cell.
  • the determining one or more flow events for the user device flow may include determining one or more of the following flow events: an activation of the user device flow based upon receiving, by the base station from the user device, data that includes information identifying a new user device flow; a modification of the user device flow or a modification to a quality of service policy associated with the user device flow; and a termination of the user device flow based on a failure of the base station to receive data for the user device flow for at least a threshold period of time.
  • the application identification information may include: a traffic flow template identifying values for one or more fields associated with the user device flow.
  • the updated quality of service profile may include a traffic flow template and one or more quality of service parameters for a quality of service policy associated with the user device flow, the traffic flow template including values for one or more fields associated with the user device flow.
  • the sending instructions to the user device may include sending, by the base station to the user device, the updated quality of service profile for the user device flow to cause the user device to adjust an uplink data rate of the user device flow.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: determine, by a base station, a congestion level for a cell; receive, by the base station via the cell from a user device, data associated with a user device flow from the user device; determine one or more flow events for the user device flow; send, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow; receive, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow; and send, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to the user device to cause the user device to adjust an uplink data rate of the user device flow.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: determining, by a base station, a congestion level for a cell; receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device; determining one or more flow events for the user device flow; sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: the congestion value for the cell; and flow event information that indicates the determined flow events for the user device flow; receiving, by the base station from the quality of experience manager, an updated quality of service profile for the user device flow; and sending, by the base station to the user device based upon the updated quality of service profile for the user device flow, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • the at least one data processing apparatus being configured to perform sending information to the quality of experience manager comprises the at least one data processing apparatus being configured to perform: sending, from the base station, information to the quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; application identification information that identifies an application type of an application that generated the flow events for the user device flow; and user device identification information that identifies the user device, the user device being associated with a service subscription level.
  • FIG. 5 is a flow chart illustrating operation of a base station according to another example implementation.
  • Operation 510 may include determining, by a base station, a congestion level for a cell.
  • Operation 520 may include receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class.
  • Operation 530 may include determining one or more flow events for the user device flow.
  • Operation 540 may include sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device
  • Operation 550 may include receiving, by the base station from the quality of experience manager, an updated quality of service profile for the first service class. And, operation 560 may include sending, by the base station to the user device based upon the updated quality of service profile for the first service class, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: determine, by a base station, a congestion level for a cell; receive, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class; determine one or more flow events for the user device flow; send, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow; identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device
  • identification information that identifies the user device, the user device being associated with a service subscription level; receive, by the base station from the quality of experience manager, an updated quality of service profile for the first service class; send, by the base station to the user device based upon the updated quality of service profile for the first service class, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising: determining, by a base station, a congestion level for a cell; receiving, by the base station via the cell from a user device, data associated with a user device flow from the user device, the user device flow included within a first service class; determining one or more flow events for the user device flow; sending, from the base station, information to a quality of experience manager to allow the quality of experience manager to determine one or more updated quality of service profiles for the user device, the information including: a cell congestion information including a congestion value that indicates the congestion level for the cell and a cell identifier that identifies the cell; flow event information that indicates the determined flow events for the user device flow;
  • identification information that identifies either the first service class for the user device flow or identifies an application type of an application that generated the flow events; and user device identification information that identifies the user device, the user device being associated with a service subscription level; receiving, by the base station from the quality of experience manager, an updated quality of service profile for the first service class; sending, by the base station to the user device based upon the updated quality of service profile for the first service class, instructions to cause the user device to adjust an uplink data rate of the user device flow.
  • FIG. 6 is a flow chart illustrating operation of a quality of experience manager according to an example implementation.
  • Operation 610 may include receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell.
  • Operation 620 may include receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network.
  • Operation 630 may include receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows.
  • Operation 640 may include determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows.
  • operation 650 may include sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • the cell congestion information may include radio access node (RAN) congestion information (RCI) that indicates a congestion level from a radio access node to a core network.
  • RAN radio access node
  • RCI congestion information
  • one or more of the user device flows may include one of the following: an application flow of data packets between an application running on a user device and a core network via a cell; and a service flow of data packets between a service running on a user device and the core network via a cell.
  • the receiving, from one or more cells, user device flow event information may include receiving user device flow event information from one or more reporting base stations or radio access network (RAN) nodes that detect one or more of the events.
  • RAN radio access network
  • the receiving, from one or more base stations, user device flow event information may include receiving one or more of the following for one or more user device flows: information indicating activation of a user device flow; information indicating a modification of a user device flow or a modification to a quality of service policy associated with the user device flow; and information indicating termination of a user device flow.
  • the determining may include determining an updated quality of service policy, including one or more updated quality of service parameters, for each of one or more of the user device flows.
  • the sending may include sending, to one or more of the cells for each of one or more user device flows, a traffic flow template and one or more quality of service parameters for a quality of service policy associated with the user device flow, each traffic flow template identifying values for one or more fields associated with the user device flow.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network; receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows; and sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, from one or more cells in a wireless network, cell congestion information including a congestion value that indicates a congestion level for a cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the wireless network; receiving, from one or more cells, user device flow event information that indicates events associated with one or more user device flows; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the user device flows; and sending, to one or more of the cells, an updated quality of service policy for one or more user device flows.
  • FIG. 7 is a flow chart illustrating operation of a quality of experience manager according to another example implementation.
  • Operation 710 may include receiving, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell.
  • Operation 720 may include receiving service subscription level information that identifies a service subscription level for one or more user devices within the cell.
  • Operation 730 may include receiving, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes.
  • Operation 740 may include determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes. And, operation 750 may include sending, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • an apparatus may include at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell; receive service subscription level information that identifies a service subscription level for one or more user devices within the cell; receive, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes; determine, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes; and send, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • a computer program product may include a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, from a cell in a wireless network, cell congestion information including a congestion value that indicates a congestion level for the cell and a cell identifier that identifies the cell; receiving service subscription level information that identifies a service subscription level for one or more user devices within the cell; receiving, from the cell, user device flow event information that indicates events associated with one or more user device flows, each user device flow associated with a service class of a plurality of service classes; determining, based on the cell congestion information, the service subscription level information and the flow event information, an updated quality of service policy for each of one or more of the service classes; and sending, to the cell, the updated quality of service policy for each of the one or more of the service classes.
  • FIG. 8 is a block diagram of a wireless station (e.g., BS or user device) 800 according to an example implementation.
  • the wireless station 800 may include, for example, two RF (radio frequency) or wireless transceivers 802A, 802B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.
  • a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals
  • a memory 806 to store data and/or instructions.
  • Processor 804 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 804 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 802 (802A or 802B).
  • Processor 804 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 802, for example).
  • Processor 804 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 804 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 804 and transceiver 802 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 808 may execute software and instructions, and may provide overall control for the station 800, and may provide control for other systems not shown in FIG. 8, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 800, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored
  • RF or wireless transceiver(s) 802A/802B may receive signals or data and/or transmit or send signals or data.
  • Processor 804 (and possibly transceivers 802A/802B) may control the RF or wireless transceiver 802A or 802B to receive, send, broadcast or transmit signals or data.
  • QoE manager 1 10 may include a processor, memory, and one or more network interfaces, and may be provided within a core network, on a server, or provided as a cloud service.
  • the embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in cooperation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be nonexistent.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a
  • a machine-readable storage device or in a propagated signal for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Abstract

L'invention concerne une technique qui peut consister à déterminer un niveau de congestion pour une cellule, à recevoir, à partir d'un dispositif d'utilisateur, des données associées à un flux de dispositif d'utilisateur à partir du dispositif d'utilisateur, à déterminer un ou plusieurs évènements de flux pour le flux de dispositif d'utilisateur, à envoyer, à partir de la station de base, des informations, comprenant le niveau de congestion et le ou les évènements de flux, à un gestionnaire de qualité d'expérience pour permettre au gestionnaire de qualité d'expérience de déterminer un ou plusieurs profils de qualité de service mis à jour pour le dispositif d'utilisateur, à recevoir, par la station de base à partir du gestionnaire de qualité d'expérience, un profil de qualité de service mis à jour pour le flux de dispositif d'utilisateur, à envoyer, par la station de base au dispositif d'utilisateur sur la base du profil de qualité de service mis à jour pour le flux de dispositif d'utilisateur, des instructions au dispositif d'utilisateur pour amener le dispositif d'utilisateur à ajuster un taux de données de liaison montante du flux de dispositif d'utilisateur.
PCT/EP2014/077184 2014-12-10 2014-12-10 Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base WO2016091298A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/077184 WO2016091298A1 (fr) 2014-12-10 2014-12-10 Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/077184 WO2016091298A1 (fr) 2014-12-10 2014-12-10 Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base

Publications (1)

Publication Number Publication Date
WO2016091298A1 true WO2016091298A1 (fr) 2016-06-16

Family

ID=52103115

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/077184 WO2016091298A1 (fr) 2014-12-10 2014-12-10 Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base

Country Status (1)

Country Link
WO (1) WO2016091298A1 (fr)

Cited By (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028061A1 (fr) * 2016-08-12 2018-02-15 中兴通讯股份有限公司 Procédé, dispositif et système de mappage de données de plan d'utilisateur, et support de stockage
KR20180045611A (ko) * 2016-10-26 2018-05-04 에스케이텔레콤 주식회사 단말장치 및 기지국장치와, QoS 제어방법
KR20180080169A (ko) * 2018-07-02 2018-07-11 에스케이텔레콤 주식회사 기지국장치와 QoS 제어방법
DE102017007290B3 (de) * 2017-08-01 2018-11-08 Mbda Deutschland Gmbh Medienzugriffssteuergerät, verfahren zur medienzugriffssteuerung und taktisches luftverteidigungssystem
WO2018208366A1 (fr) * 2017-05-07 2018-11-15 Qualcomm Incorporated Activation de qualité de service cellulaire new radio pour sessions de données de protocole non internet
WO2019104343A1 (fr) 2017-11-27 2019-05-31 Opanga Networks, Inc. Système et procédé d'accélération ou de décélération d'un protocole de réseau de transport de données sur la base de conditions de congestion du réseau de transport en temps réel
WO2019217723A1 (fr) * 2018-05-11 2019-11-14 Viavi Solutions Inc. Détection de brouillage d'un faisceau
US10560206B2 (en) 2017-12-12 2020-02-11 Viavi Solutions Inc. Processing a beamformed radio frequency (RF) signal
WO2020038556A1 (fr) * 2018-08-21 2020-02-27 Huawei Technologies Co., Ltd. Nœud d'accès au réseau et dispositif client pour la gestion de la qualité de service
EP3633936A1 (fr) * 2018-10-04 2020-04-08 Sandvine Corporation Procédé et système de gestion de congestion sensible aux applications
WO2020074108A1 (fr) * 2018-10-08 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Commande de notification dans un système de communication
US10631263B2 (en) 2018-09-14 2020-04-21 Viavi Solutions Inc. Geolocating a user equipment
WO2020152395A1 (fr) * 2019-01-23 2020-07-30 Nokia Solutions And Networks Oy Marquage d'un paquet de données de liaison montante
US20200383006A1 (en) * 2018-02-19 2020-12-03 Huawei Technologies Co., Ltd. Apparatus for supporting and influencing qos levels
US10965654B2 (en) 2017-11-28 2021-03-30 Viavi Solutions Inc. Cross-interface correlation of traffic
US10979326B2 (en) 2018-05-11 2021-04-13 Viavi Solutions Inc. Detecting interference of a beam
CN112672364A (zh) * 2019-10-16 2021-04-16 中国移动通信有限公司研究院 策略配置方法、装置、相关设备及存储介质
CN112913272A (zh) * 2018-08-20 2021-06-04 诺基亚通信公司 方法、装置和计算机程序
CN110049352B (zh) * 2019-04-18 2021-06-18 北京达佳互联信息技术有限公司 码率确定方法、装置、计算机设备和存储介质
WO2021180704A1 (fr) 2020-03-11 2021-09-16 Ipcom Gmbh & Co. Kg Coordination d'un réglage de qualité de service entre différentes connexions
CN113475157A (zh) * 2018-12-22 2021-10-01 诺基亚通信公司 用于无线网络的连接行为标识
US20220110145A1 (en) * 2020-10-05 2022-04-07 Qualcomm Incorporated Traffic aware regular buffer status reports
CN114978998A (zh) * 2021-02-26 2022-08-30 中移(苏州)软件技术有限公司 一种流量控制方法、装置、终端及存储介质
US11632691B1 (en) * 2020-03-18 2023-04-18 Sprint Spectrum Llc Dynamic PDCP duplication with bearer modification, to help overcome reduced wireless quality
WO2023065103A1 (fr) * 2021-10-19 2023-04-27 Qualcomm Incorporated Améliorations de rapport de qualité d'expérience
CN116233871A (zh) * 2023-01-17 2023-06-06 广州爱浦路网络技术有限公司 一种xr服务增强方法、计算机装置和存储介质
CN113475157B (zh) * 2018-12-22 2024-05-14 诺基亚通信公司 用于无线网络的连接行为标识

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110158090A1 (en) * 2009-12-31 2011-06-30 Yusun Kim Riley Methods, systems, and computer readable media for condition-triggered policies
WO2014110410A1 (fr) * 2013-01-11 2014-07-17 Interdigital Patent Holdings, Inc. Gestion de congestion de plan utilisateur

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110158090A1 (en) * 2009-12-31 2011-06-30 Yusun Kim Riley Methods, systems, and computer readable media for condition-triggered policies
WO2014110410A1 (fr) * 2013-01-11 2014-07-17 Interdigital Patent Holdings, Inc. Gestion de congestion de plan utilisateur

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP DRAFT; ATIS NETWORK OPTIMIZATION FOCUS GROUP (NETOP-FG) ASSESSMENT & RECOMMENDATIONS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 8 November 2011 (2011-11-08), XP050574392 *
NTT DOCOMO: "C-Plane/PCC based Congestion Notification", vol. SA WG2, no. San Diego, US; 20130408 - 20130412, 2 April 2013 (2013-04-02), XP050708123, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_96_San_Diego/Docs/> [retrieved on 20130402] *

Cited By (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028061A1 (fr) * 2016-08-12 2018-02-15 中兴通讯股份有限公司 Procédé, dispositif et système de mappage de données de plan d'utilisateur, et support de stockage
KR20180045611A (ko) * 2016-10-26 2018-05-04 에스케이텔레콤 주식회사 단말장치 및 기지국장치와, QoS 제어방법
US10827379B2 (en) 2016-10-26 2020-11-03 Sk Telecom Co., Ltd. Terminal device, base station device, and method for controlling QoS
WO2018079948A3 (fr) * 2016-10-26 2018-08-02 에스케이텔레콤 주식회사 Dispositif terminal, dispositif station de base et procédé de commande de qos
KR102121733B1 (ko) * 2016-10-26 2020-06-11 에스케이텔레콤 주식회사 단말장치 및 기지국장치와, QoS 제어방법
WO2018208366A1 (fr) * 2017-05-07 2018-11-15 Qualcomm Incorporated Activation de qualité de service cellulaire new radio pour sessions de données de protocole non internet
CN110637476A (zh) * 2017-05-07 2019-12-31 高通股份有限公司 实现非互联网协议数据会话的新无线电蜂窝服务质量
US10986000B2 (en) 2017-05-07 2021-04-20 Qualcomm Incorporated Enabling new radio cellular quality of service for non-internet protocol data sessions
DE102017007290B3 (de) * 2017-08-01 2018-11-08 Mbda Deutschland Gmbh Medienzugriffssteuergerät, verfahren zur medienzugriffssteuerung und taktisches luftverteidigungssystem
EP3718270A4 (fr) * 2017-11-27 2021-08-25 Opanga Networks, Inc. Système et procédé d'accélération ou de décélération d'un protocole de réseau de transport de données sur la base de conditions de congestion du réseau de transport en temps réel
WO2019104343A1 (fr) 2017-11-27 2019-05-31 Opanga Networks, Inc. Système et procédé d'accélération ou de décélération d'un protocole de réseau de transport de données sur la base de conditions de congestion du réseau de transport en temps réel
US11381508B2 (en) 2017-11-27 2022-07-05 Opanga Networks, Inc. System and method for accelerating or decelerating a data transport network protocol based on real time transport network congestion conditions
CN111386683A (zh) * 2017-11-27 2020-07-07 欧庞戈网络有限公司 基于实时传输网络拥塞状况来加速或减速数据传输网络协议的系统和方法
US10965654B2 (en) 2017-11-28 2021-03-30 Viavi Solutions Inc. Cross-interface correlation of traffic
US11799838B2 (en) 2017-11-28 2023-10-24 Viavi Solutions Inc. Cross-interface correlation of traffic
US10560206B2 (en) 2017-12-12 2020-02-11 Viavi Solutions Inc. Processing a beamformed radio frequency (RF) signal
US10742336B2 (en) 2017-12-12 2020-08-11 Viavi Solutions Inc. Processing a beamformed radio frequency (RF) signal
US11088771B2 (en) 2017-12-12 2021-08-10 Viavi Solutions Inc. Processing a beamformed radio frequency (RF) signal
US11700551B2 (en) * 2018-02-19 2023-07-11 Huawei Technologies Co., Ltd. Apparatus for supporting and influencing QoS levels
US11943666B2 (en) 2018-02-19 2024-03-26 Huawei Technologies Co., Ltd. Apparatus for supporting and influencing QoS levels
US20200383006A1 (en) * 2018-02-19 2020-12-03 Huawei Technologies Co., Ltd. Apparatus for supporting and influencing qos levels
WO2019217723A1 (fr) * 2018-05-11 2019-11-14 Viavi Solutions Inc. Détection de brouillage d'un faisceau
US10979326B2 (en) 2018-05-11 2021-04-13 Viavi Solutions Inc. Detecting interference of a beam
KR102121730B1 (ko) * 2018-07-02 2020-06-11 에스케이텔레콤 주식회사 기지국장치와 QoS 제어방법
KR20180080169A (ko) * 2018-07-02 2018-07-11 에스케이텔레콤 주식회사 기지국장치와 QoS 제어방법
CN112913272A (zh) * 2018-08-20 2021-06-04 诺基亚通信公司 方法、装置和计算机程序
WO2020038556A1 (fr) * 2018-08-21 2020-02-27 Huawei Technologies Co., Ltd. Nœud d'accès au réseau et dispositif client pour la gestion de la qualité de service
US10631263B2 (en) 2018-09-14 2020-04-21 Viavi Solutions Inc. Geolocating a user equipment
US11191057B2 (en) 2018-09-14 2021-11-30 Viavi Solutions Inc. Geolocating a user equipment
EP3633936A1 (fr) * 2018-10-04 2020-04-08 Sandvine Corporation Procédé et système de gestion de congestion sensible aux applications
US11297527B2 (en) 2018-10-04 2022-04-05 Sandvine Corporation Method and system for application aware congestion management
WO2020074108A1 (fr) * 2018-10-08 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Commande de notification dans un système de communication
CN113475157A (zh) * 2018-12-22 2021-10-01 诺基亚通信公司 用于无线网络的连接行为标识
CN113475157B (zh) * 2018-12-22 2024-05-14 诺基亚通信公司 用于无线网络的连接行为标识
US11979754B2 (en) 2018-12-22 2024-05-07 Nokia Solutions And Networks Oy Connection behavior identification for wireless networks
CN113348652B (zh) * 2019-01-23 2023-05-02 诺基亚通信公司 标记上行链路数据分组
CN113348652A (zh) * 2019-01-23 2021-09-03 诺基亚通信公司 标记上行链路数据分组
US11902872B2 (en) 2019-01-23 2024-02-13 Nokia Solutions And Networks Oy Marking an uplink data packet
WO2020152395A1 (fr) * 2019-01-23 2020-07-30 Nokia Solutions And Networks Oy Marquage d'un paquet de données de liaison montante
CN110049352B (zh) * 2019-04-18 2021-06-18 北京达佳互联信息技术有限公司 码率确定方法、装置、计算机设备和存储介质
CN112672364A (zh) * 2019-10-16 2021-04-16 中国移动通信有限公司研究院 策略配置方法、装置、相关设备及存储介质
CN112672364B (zh) * 2019-10-16 2024-03-19 中国移动通信有限公司研究院 策略配置方法、装置、相关设备及存储介质
WO2021180704A1 (fr) 2020-03-11 2021-09-16 Ipcom Gmbh & Co. Kg Coordination d'un réglage de qualité de service entre différentes connexions
US11632691B1 (en) * 2020-03-18 2023-04-18 Sprint Spectrum Llc Dynamic PDCP duplication with bearer modification, to help overcome reduced wireless quality
US20220110145A1 (en) * 2020-10-05 2022-04-07 Qualcomm Incorporated Traffic aware regular buffer status reports
CN114978998B (zh) * 2021-02-26 2023-12-12 中移(苏州)软件技术有限公司 一种流量控制方法、装置、终端及存储介质
CN114978998A (zh) * 2021-02-26 2022-08-30 中移(苏州)软件技术有限公司 一种流量控制方法、装置、终端及存储介质
WO2023065103A1 (fr) * 2021-10-19 2023-04-27 Qualcomm Incorporated Améliorations de rapport de qualité d'expérience
CN116233871A (zh) * 2023-01-17 2023-06-06 广州爱浦路网络技术有限公司 一种xr服务增强方法、计算机装置和存储介质
CN116233871B (zh) * 2023-01-17 2023-12-15 广州爱浦路网络技术有限公司 一种xr服务增强方法、计算机装置和存储介质

Similar Documents

Publication Publication Date Title
WO2016091298A1 (fr) Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d&#39;informations rapportées à partir d&#39;une station de base
EP3443718B1 (fr) Procédé et appareil pour l&#39;exposition de la capacité de qualité de service d&#39;un réseau de communication
EP3446464B1 (fr) Systèmes et procédé destinés à la surveillance de qualité de service, l&#39;application de politique et la facturation dans un réseau de communication
US10623928B2 (en) Terminal node, method, storage medium for video data transmission
US10827501B2 (en) Techniques for providing proximity services (ProSe) priority-related information to a base station in a wireless network
US11026247B2 (en) Transmitting data based on flow input from base station
US9843964B2 (en) Method and apparatus for managing congestion in wireless communication system
US20140155043A1 (en) Application quality management in a communication system
US20140153392A1 (en) Application quality management in a cooperative communication system
KR20170093938A (ko) 통신들의 경험 품질 시행
US10834650B2 (en) Directed handover of elephant flows
US11483732B2 (en) Intelligent allocation of network resources
US20140341031A1 (en) Differentiation of traffic flows mapped to the same bearer
US20170006495A1 (en) Intelligent handling of voice calls from mobile voice client devices
EP2859769B1 (fr) Systèmes et procédés pour des applications collaboratives dans des systèmes de communication
JP2016225682A (ja) 中継装置、通信システム、通信制御方法および通信制御プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14812726

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14812726

Country of ref document: EP

Kind code of ref document: A1