WO2023014255A1 - Gestion de configuration de qoe basée sur un événement - Google Patents

Gestion de configuration de qoe basée sur un événement Download PDF

Info

Publication number
WO2023014255A1
WO2023014255A1 PCT/SE2022/050643 SE2022050643W WO2023014255A1 WO 2023014255 A1 WO2023014255 A1 WO 2023014255A1 SE 2022050643 W SE2022050643 W SE 2022050643W WO 2023014255 A1 WO2023014255 A1 WO 2023014255A1
Authority
WO
WIPO (PCT)
Prior art keywords
qoe
measurement
wireless device
network node
trigger event
Prior art date
Application number
PCT/SE2022/050643
Other languages
English (en)
Inventor
Luca LUNARDI
Johan Rune
Ali PARICHEHREHTEROUJENI
Cecilia EKLÖF
Filip BARAC
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023014255A1 publication Critical patent/WO2023014255A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present disclosure is generally related to wireless communications networks and is more particularly related to the performing of quality-of-experience (QoE) measurements in such networks.
  • QoE quality-of-experience
  • QoE measurements have been specified for the Long-Term Evolution (LTE) and Universal Mobile Telecommunications System (UMTS) wireless standards and are being specified for the NR (New Radio) standards under development by the 3 rd -Generation Partnership Project (3GPP).
  • LTE Long-Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • NR New Radio
  • the purpose of the application layer measurements is to measure the end user experience when using certain applications.
  • QoE measurements for streaming services and for MTSI (Mobility Telephony Service for IMS) services are supported.
  • Quality of Experience Measurement Collection enables configuration of application layer measurements in the user equipment (UE) and transmission of QoE measurement result files by means of Radio Resource Control (RRC) signalling.
  • Application layer measurement configuration received from the Operations and Maintenance (0AM) subsystem or the core network (CN) is encapsulated in a transparent container, which is forwarded to the UE in a downlink RRC message.
  • Application layer measurements received from UE’s higher layer are encapsulated in a transparent container and sent to network in an uplink RRC message.
  • the result container is forwarded to a TCE, Trace Collector Entity.
  • the QoE measurements may be initiated towards the radio access network (RAN) in a management-based manner, i.e., from an O&M node in a generic way, e.g., for a group of UEs, or they may also be initiated in a signaling-based manner, i.e., initiated from CN to RAN, e.g., for a single UE.
  • the configuration of the measurement includes the measurement details, which is encapsulated in a container that is transparent to RAN.
  • the measurement When initiated via the core network, the measurement is started towards a specific UE.
  • the "TRACE START" S1AP message is used, which carries, among others, the details about the measurement configuration the application should collect (in the “Container for application layer measurement configuration” information element (IE), which is transparent to the RAN) and the details to reach the trace collection entity to which the measurements should be sent.
  • IE Container for application layer measurement configuration
  • the RAN is not aware of when the streaming session is ongoing in the UE Access Stratum and is also not aware of when the measurements are ongoing. It is an implementation decision when RAN stops the measurements. Typically, it is done when the UE has moved outside the measured area.
  • the UE capability transfer is used to transfer UE radio access capability information from the UE to E-UTRAN.
  • This procedure is shown in Figure 1.
  • the UE-EUTRA- Capability information element IE
  • the UE can include the “UE- EUTRA-Capability” IE.
  • the “UE-EUTRA-Capability “IE may include the UE-EUTRA- Capability-vl530-IE which can be used by the UE to indicate whether the UE supports or not QoE Measurement Collection for streaming services and/or MTSI services, as detailed in the “MeasParameters-vl530” encoding below.
  • Figure 2 illustrates the application layer measurement reporting procedure, as described in 3GPP TS 36.331. The purpose of this procedure is to inform E-UTRAN about application layer measurement reports.
  • a UE capable of application layer measurement reporting in RRC CONNECTED state may initiate the procedure when configured with application layer measurement, i.e., when measConfigAppLayer has been configured by E-UTRAN.
  • the UE shall, if configured with application layer measurement, and if SRB4 is configured, and if the UE has received application layer measurement report information from upper layers: set the measReportAppLayerContainer in the MeasReportAppLayer message to the value of the application layer measurement report information, set the serviceType in the MeasReportAppLayer message to the type of the application layer measurement report information, and submit the MeasReportAppLayer message to lower layers for transmission via SRB4.
  • the RRCConnectionReconfiguration message is used to reconfigure the UE to setup or release the UE for Application Layer measurements. This is signaled in the measConfigAppLayer-15 IE within the “OtherConfig” IE.
  • the setup includes the transparent container measConfigAppLayerContainer which specifies the QoE measurement configuration for the Application of interest and the serviceType IE to indicates the Application (or service) for which the QoE measurements are being configured.
  • Supported services are streaming and MTSI.
  • the MeasReportAppLayer RRC message is used by the UE to send to the E-UTRAN node the QoE measurement results of an application (or service).
  • the service for which the report is being sent is indicated in the “serviceType” IE.
  • the “UE Application layer measurement configuration” IE is described in 3GPP TS 36.413 V16.5.0 and 3GPP TS 36.423 vl6.5.0.
  • Certain aspects of this disclosure and their embodiments may provide solutions to these or other challenges.
  • the solutions described herein enable the management of QoE configurations (e.g., to initiate, inactivate, reactivate or release) based on events. That means that QoE measurements are only configured, carried out, etc., if certain event(s) are fulfilled.
  • the QoE configuration may be sent early to the UE and the UE activates the configuration when the event(s) are fulfilled, or alternatively, the network sends the QoE configuration to the UE when the event(s) are fulfilled.
  • An example method is carried out in a wireless device operating in a wireless network and is for performing QoE measurements.
  • This example method comprises receiving, from the wireless network, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action.
  • the example method further comprises detecting that the identified trigger event has occurred and performing the measurement-related action with respect to the corresponding QoE measurement, in response to detecting that the identified trigger event has occurred.
  • the apparatuses described herein include a wireless device for performing QoE measurements, where the wireless device is adapted to carry out the method summarized above, and variants thereof.
  • the wireless device may comprise processing circuitry and radio front-end circuitry connected to the processing circuitry, where the processing circuitry is configured to receive, from a wireless network, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action, detect that the identified trigger event has occurred, and perform the measurement-related action with respect to the corresponding QoE measurement, in response to detecting that the identified trigger event has occurred.
  • An example method for facilitating QoE measurements by a wireless device or group of wireless devices is carried out in a network node and comprises the step of sending, to a wireless device or group of wireless devices, a QoE measurement configuration message, where the QoE measurement configuration message identifies a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device before execution of the measurement-related action.
  • the method further comprises receiving, from at least one wireless device, a message indicating that the trigger event has occurred, and sending, to the at least one wireless device, one or more QoE configuration parameters corresponding to the QoE measurement, in response to the message indicating that the trigger event has occurred.
  • an example network node comprises radio front-end circuitry and processing circuitry connected to the radio front-end circuitry, where the processing circuitry is configured to send to a wireless device or group of wireless devices, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device before execution of the measurement-related action.
  • Figure 1 illustrates a UE capability transfer procedure
  • Figure 2 shows an application layer measurement reporting procedure.
  • FIG. 3 and Figure 4 show alternative approaches for management of Quality-of- Experience (QoE) configurations.
  • QoE Quality-of- Experience
  • Figure 5 shows another approach for management of QoE configurations.
  • Figure 6, Figure 7, and Figure 8 are process flow diagrams illustrating example methods might be carried out by a wireless device and by one or more network nodes, according to various embodiments.
  • Figure 9 shows an example of a communication system in accordance with some embodiments.
  • FIG. 10 shows a user equipment (UE) in accordance with some embodiments.
  • Figure 11 shows a network node in accordance with some embodiments.
  • Figure 12 is a block diagram of a host.
  • Figure 13 is a block diagram illustrating a virtualization environment.
  • Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • the terms “UE”, “terminal equipment”, “wireless terminal” and “terminal”, and “wireless device” are used interchangeably.
  • the terms “QoE measurement report”, “QoE report”, “measurement report” and “report” are used interchangeably.
  • the terms “event” and “event for QoE configuration management” are used interchangeably when not explicitly mentioned otherwise.
  • additional QoE configuration parameters refers to the QoE configuration parameters other than the QoE event-based configuration parameters regulating QoE configuration management.
  • the terms “QoE measurement configuration”, QoE measurement and reporting configuration”, “QoE configuration” can be used interchangeably.
  • QoE measurement also can refer to a measurement or data collection performed for the purpose of determining a QoE metric.
  • service and “application” are used interchangeably.
  • MCE and “TCE” are used interchangeably.
  • a network node can be, without limitation, a RAN node, a gNB, eNB, en-gNB, ng- eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, eNB-CU, eNB-CU-CP, eNB-CU- UP, eNB -DU, I AB -nodes, I AB -donors, lAB-donor-CU, lAB-donor-CU-CP, lAB-donor- CU-UP, lAB-donor-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB, a Core Network node, an 0AM node, an SMO node.
  • the solutions described herein enable the management of QoE configurations (e.g., to initiate, inactivate, reactivate or release) based on events. That means that QoE measurements are only configured, carried out, etc., if certain event(s) are fulfilled.
  • the QoE configuration may be sent early to the UE and the UE activates the configuration when the event(s) are fulfilled, or alternatively, the network sends the QoE configuration to the UE when the event(s) are fulfilled.
  • Figure 3 illustrates an overview of alternative 1, where a first network node sends events for QoE configuration management and additional QoE configuration parameters in the same message.
  • QoE configuration is pending at the UE (e.g., in the UE’s RRC layer) until the event is fulfilled (and, optionally, a confirmation arrives from the first network node).
  • Figure 4 shows an overview of alternative 2, where a first network node sends events for QoE configuration management and additional QoE configuration parameters in different messages.
  • a first network node e.g., a radio access network (RAN) node, such as an eNB or gNB, receives and/or derives one or more events for QoE configuration management applicable to an individual UE or to a group of UEs, the event(s) to be used to perform an action on one or more QoE configuration(s).
  • This receiving may be accomplished by means of information comprised in a FIRST MESSAGE sent by a second network node to the first network node, in some embodiments or instances.
  • the second network node can be, e.g., a RAN node, a core network (CN) node, an Operations, Administration, and Management (0AM) node or a Service Management and Orchestration (SMO) node. Deriving the event may be based on information comprised at least in part in the FIRST MESSAGE and/or based on other information available at the first network node, e.g., preconfigured setting and/or configuration parameters related to radio resource management, RAT, RAN node, cells, carrier frequencies, UE radio related capabilities, UE service-related capabilities, etc.
  • the second network node e.g., the 0AM node
  • the first network node e.g., the Access and Mobility Management Function, AMF, or the gNB
  • the QoE configuration is conditioned by an event at the application layer, but it does not have to inform the network node of what the event is, since it is an application related event.
  • the first network node sends a SECOND MESSAGE, e.g., an RRCReconfiguration message or a newly defined message, to the UE RRC.
  • This SECOND MESSAGE may comprise information pertaining to one or more events for QoE configuration management and one or more actions to perform on the QoE configuration(s) upon fulfillment of the one or more event.
  • the SECOND MESSAGE also comprises additional QoE configuration parameters (such as service type, one or more application layer container, QoE reference), part of which is to be further sent to the UE Application layer.
  • the QoE configuration parameters are sent later, in the FIFTH MESSAGE.
  • the first network node may receive at least one THIRD MESSAGE from the UE RRC indicating that one or more event for QoE configuration management is fulfilled.
  • This message may be, for example, MeasurementReport message or a UEAssistancelnformation message, or a newly defined message.
  • the first network node may receive a FOURTH MESSAGE from the UE RRC indicating a status or a change in status of an application associated to the event for QoE configuration management.
  • the THIRD MESSAGE sent by the UE can comprise a confirmation of reception of the SECOND MESSAGE.
  • the THIRD MESSAGE and FOURTH MESSAGE can be implemented in one signaling message or in separate signaling messages, in various embodiments.
  • the first network node may send a FIFTH MESSAGE comprising an explicit confirmation signal indicating that it is possible to send one or more of the pending QoE configuration from the RRC layer of the UE to the Application layer of the UE.
  • This FIFTH MESSAGE might be sent either after reception of a THIRD MESSAGE, or after reception of both a THIRD MESSAGE and a FOURTH MESSAGE, in various embodiments.
  • the first network node sends to the UE RRC a FIFTH MESSAGE comprising QoE configuration parameters.
  • This FIFTH MESSAGE can be sent either after reception of a THIRD MESSAGE, or after reception of both a THIRD MESSAGE and a FOURTH MESSAGE, or before the reception of the SECOND message.
  • the UE RRC sends a SIXTH MESSAGE to the UE Application Layer comprising the QoE configuration parameters, for use in carrying out the QoE measurement associated with the triggering event.
  • the SIXTH MESSAGE can be sent either after transmission of a THIRD MESSAGE, or after transmission of both a THIRD MESSAGE and a FOURTH MESSAGE, or after reception of a FIFTH MESSAGE.
  • the SIXTH MESSAGE can be sent after reception of the FIFTH MESSAGE.
  • Alternatives 1 and 2 refer to events related to the radio layer of the UE (e.g., the RRC layer).
  • the application layer-based events can be defined. In that case, it is the UE Application Layer that receives the message containing the events for the QoE configuration management and checks the conditions for the event fulfillment.
  • Alternative 3 can exist in at least 2 forms: Type 1, similar to Alternative 1, with a “Check condition for application-based event fulfillment” executed by the UE application layer, and Type 2, similar to Alternative 2, with “Check condition for application-based event fulfillment” executed by the UE application layer.
  • Figure 5 illustrates the Alternative 3, type 2, solution.
  • a SEVENTH MESSAGE is sent from the UE RRC to the UE Application Layer comprising “events for QoE configuration management,” an EIGHT MESSAGE is sent from the UE Application Layer to the UE RRC and comprises a notification of event(s) fulfillment, and a NINTH MESSAGE is sent from the UE Application Layer to the UE RRC and comprises indications of application status.
  • the first network node receives and/or derives one or more event for QoE configuration management.
  • This receiving may be by means of information comprised in a FIRST MESSAGE sent by a second network node to the first network node, where the second network node can be a RAN node, a CN node, an OAM node or a SMO node, and where this deriving of the event may be based on information other than that in the FIRST MESSAGE and available at the first network node, e.g., preconfigured setting and/or configuration parameters related to radio resource management, RAT, RAN node, cells, carrier frequencies, UE radio related capabilities, UE service related capabilities.
  • an event for QoE configuration management is to be used to perform an action pertaining to one or more QoE configurations for QoE measurements, where an action can be one or a combination of: sending one or more QoE configuration, or parts thereof (based on the fulfilled event)
  • An event for QoE configuration management which might also be referred to as a “trigger event” or “triggering event,” may be applicable to an individual UE or to a group of UEs.
  • An event for QoE configuration management may be applicable to one specific service type or to a group of configured service types, or at least one application identified by application name or an application identifier.
  • An event for QoE configuration management may be defined by one or more configuration parameters, where a configuration parameter can be: an identifier identifying the event one or more indications, indicating a Radio Access Technology (e.g., E-UTRA, NR) one or more indications, indicating a quantity and/or a condition associated to one or more of a radio channel, a radio resource, a radio access technology, a UE (e.g., RSRP, RSRQ, RS-SINR, RS SI, Interference, channel busy ratio, aerial UE height) one or more thresholds, expressed in various units (e.g., dB, dBm, meters, seconds) or unitless one of more hysteresis, expressed in various units (e.g., dB, dBm, meters, seconds) or unitless one or more offsets, expressed in various units (e.g., dB, dBm, meters, seconds) or unitless one or more time to trigger for an event, expressed in
  • An event for QoE configuration management may coincide with one of the events defined for NR in 3GPP TS 38.331, in some embodiments, such as:
  • An event for QoE configuration management may coincide with one of the events defined for E-UTRA in 3GPP TS 36.331, such as:
  • Event A5 PCell/ PSCell becomes worse than thresholdl and neighbour becomes better than threshold2
  • Event A6 Neighbour becomes offset better than SCell
  • An event for QoE configuration management can be defined based on one of the following, in some embodiments or instances: a change in the UE RRC state from a non-connected state to a connected state or vice versa (e.g., from NR RRC Idle or NR RRC Inactive to NR RRC Connected) a change in the UE radio resource management from a first RAT to a second RAT (e.g., from NR to E-UTRA or vice versa)
  • - number of radio link failures in a time interval is within a certain range, or below/above a threshold value, plus or minus a hysteresis
  • - number of connection establishment failures in a time interval is within a certain range, or below/above a threshold value, plus or minus a hysteresis
  • - number or mobility events in a time interval is within a certain range, or below/above a threshold value, plus or minus a hysteresis
  • An event for QoE configuration management may coincide with one of the events related to the data/user plane, in some embodiments, such as:
  • An event for QoE configuration management may relate to one or a combination of the following types of QoE configurations, in some embodiments: a QoE configuration comprising QoE metrics/parameters/values that cannot be interpreted by a Radio Access Network (RAN) node a QoE configuration comprising QoE metrics/parameters/values that can be interpreted by a Radio Access Network (RAN) node
  • RAN Radio Access Network
  • an event for QoE configuration management can be related to the UE application layer, such as, for example: starting an application session via a specific application, for example a video streaming session via YouTube.
  • an Application descriptor such as an OSId or an OSAppId.
  • an indicator related to an application e.g., a number of sessions, session length, session interval, load time, latency, timeliness.
  • the first network node can decide an action pertaining to QoE configuration based on one or more events for QoE configuration management combined with other conditions comprised in the QoE configuration.
  • Non-limiting examples of such conditions are: a list of cells, a list of TAs, a list of TAIs, a list of PLMNs, a list of S-NSSAIs, one or more service types or service subtypes, one or more carrier frequencies, one or more connectivity option (e.g., single connectivity, multi -radio connectivity), one or more RAT
  • the FIRST MESSAGE shown in any of Figures 3-5 can be implemented as an existing message or a new message over one of NGAP, S1AP, XnAP, X2AP, F1AP, E1AP, W1AP, such as: an NGAP INITIAL CONTEXT SETUP REQUEST message, an NGAP TRACE START message, an NGAP HANDOVER REQUIRED message, an NGAP HANDOVER REQUEST message, an XnAP HANDOVER REQUEST message.
  • This FIRST MESSAGE can comprise information pertaining to one or more events for QoE configuration management and, in some instances or embodiments, additional QoE configuration information associated to the one or more events.
  • the first network node sends a SECOND MESSAGE to UE, e.g., to the RRC layer of the UE, the SECOND MESSAGE comprising one or more events for QoE configuration management and/or one or more identifiers of event for QoE configuration management.
  • an event or an identifier of an event is signaled a part of a QoE configuration an event or an identifier of the event is signaled together with a QoE configuration an event or an identifier of an event is applicable to one QoE configuration an event or an identifier of the event is applicable to a set of QoE configurations
  • an identifier of an event can be the same as an eventld used for Event trigger Configuration or Conditional Trigger Configuration within an RRC message (e.g., one of the eventld or one of the condEventld within the NR RRCReconfiguration message)
  • the SECOND MESSAGE may comprise one of more identifiers identifying one or more QoE configurations.
  • the SECOND MESSAGE may comprise one or more QoE configurations, and/or an indication that indicates to the RRC layer of the UE to refrain sending the QoE configuration to the Application layer of the UE.
  • a condition can be indicated (implicitly or explicitly) indicating that upon fulfillment of one or more event, one or more of the pending QoE configurations can or shall be sent from the RRC layer of the UE to the Application layer of the UE without any further confirmation.
  • a condition can be indicated (implicitly or explicitly) indicating that the UE should wait for an explicit confirmation signal (FIFTH MESSAGE) before sending the one or more pending QoE configurations from the RRC layer of the UE to the Application layer of the UE.
  • FTH MESSAGE an explicit confirmation signal
  • the SECOND MESSAGE may comprise: indication(s) or pointer(s) indicating that one or more QoE configuration(s), or one or more of the identities identifying QoE configuration(s), is/are associated to one or more event for QoE configuration management or to one or more of the identities identifying event for QoE configuration management indication(s) indicating one or more actions to be performed on the QoE configuration(s) upon fulfillment of the one or more event, where non-liming examples of actions are: configuring/deconfiguring/reconfiguring application layer configuration for QoE measurements, starting/stopping/releasing QoE measurements immediately, etc.
  • the SECOND MESSAGE may comprise indication(s) indicating to the UE to send, to the first network node, upon fulfillment of one or more event for QoE configuration management, one or more of the following: information to identify the one or more event that is fulfilled
  • - information to identify the one or more application session to which a QoE configuration is applicable e.g., a service type, a recording session ID
  • a status or a change in status can be one of: started, stopped, ongoing, paused, resumed, in-synch, out-of-synch, synchronizing o the status or a change in status can be indicated per service type or service subtype o the association between an application session and a QoE configuration can be realized based on one or a combination of various information, such as: an identifier of the QoE configuration (e.g., a QoE reference or RRC ID), an identifier of the recording session (e.g., a recording session ID), a service type, a service subtype.
  • an identifier of the QoE configuration e.g., a QoE reference or RRC ID
  • an identifier of the recording session e.g., a recording session ID
  • service type e.g., a service subtype
  • the first network node can send the QoE configuration to the UE subsequently to event fulfillment.
  • the SECOND MESSAGE can be implemented as an existing message or a new message over NR.
  • RRC or E-UTRAN RRC, such as: an NR RRCSetup, an NR RRCReconfiguration, an NR RRCReestablishment, an NR RRCResume, an NR DLInformationTransfer, an NR DLInformationTranferMRDC, an NR UEInformationRequest, an E-UTRA RRCConnectionSetup, an E-UTRA RRCConnectionResume, an E-UTRA RRCConnectionReconfiguration, an E-UTRA RRCConnectionReestablishment, or an E-UTRA DLInformationTransfer
  • the first network node upon fulfillment of one or more events for QoE configuration management, receives, from the RRC layer of the UE, at least one THIRD MESSAGE, a THIRD MESSAGE comprising one or more of: information to identify the one or more events that is/are fulfilled; and information to identify one or more QoE configuration associated to the one or more event fulfilled (e.g., a QoE reference).
  • This THIRD MESSAGE may comprise timing information, in some embodiments or instances, e.g., indicating the time(s) at which the event(s) has/have been fulfilled.
  • the first network node sends to the UE, e.g., to the RRC layer of the UE, a FOURTH MESSAGE, the FOURTH MESSAGE comprising one or more of: information to identify one or more application session to which a QoE configuration is applicable (e.g., a service type, a recording session ID); and information concerning a status or a change in status for one or more application session / recording session to which a QoE configuration is associated.
  • information to identify one or more application session to which a QoE configuration is applicable e.g., a service type, a recording session ID
  • information concerning a status or a change in status for one or more application session / recording session to which a QoE configuration is associated e.g., a service type, a recording session ID
  • This FOURTH MESSAGE may comprise timing information, e.g., indicating the time(s) at which application session(s) / recording session(s) has/have been started/stopped/paused/resumed/in-synch/out-of- synch/synchronizing.
  • the THIRD MESSAGE and FOURTH MESSAGE described above can be implemented in one signaling message or in separate signaling messages.
  • the THIRD MESSAGE and/or the FOURTH MESSAGE can be implemented as an existing message or a new message over NR RRC, or E-UTRAN RRC, such as: an NR MeasReportAppLayer (or alike), an NR RRCSetupRequest, an NR RRCReconfigurationComplete, an NR RRCReestablishmentRequest, an NR RRCResumeRequest, an NR RRCResum eRequest 1, an NR MeasurementReport, an NR ULInformationTransfer, an NR ULInformationTranferMRDC, an NR ULInformationTransferIRAT, an NR SCGFailurelnformation, an SCGFailurelnformationEUTRA, an NR MCGFailurelnformation, an NR UE Assistanceinformation, an NR Failureinformation, an NR
  • the first network node may send to the UE, e.g., to the RRC layer of the UE, a FIFTH MESSAGE, the FIFTH MESSAGE comprising one or more of: (alternative 1) an indication, indicating to the RRC layer of the UE that sending of QoE configuration parameters to the Application layer of the UE is possible; and (alternative 2) one or more QoE configuration parameters.
  • the first network node sends, to the RRC layer of the UE a FIFTH MESSAGE only if the event has been fulfilled and if the UE has indicated to the network that a session in the application layer has started.
  • first network node i.e., a node providing a QoE configuration to a UE.
  • UE a node providing a QoE configuration to a UE.
  • the communication between the network and the UE, regarding the QoE configurations is at the RRC layer, and thus this discussion will describe actions taken by the UE’s RRC layer, which may, for example, interact with a distinct application layer at the U E.
  • RRC layer which may, for example, interact with a distinct application layer at the U E.
  • these operations and actions may more generally be understood as simply being performed by the UE.
  • this document refers to something happening at or in the RRC layer of the UE, it will be understood that the same actions or operations may be implemented in a wireless device in which there is nothing called an “RRC layer,” or in or by one or more other layers.
  • the RRC layer of the UE receives, from the first network node, a SECOND MESSAGE, the SECOND MESSAGE comprising information as described in the embodiments for the first network node.
  • the RRC layer of the UE may store one or more QoE configurations in a pending state, i.e., not sent to the upper layers yet for execution.
  • the RRC layer of the UE determines whether one or more events for QoE configuration management is/are fulfilled, using one or more sources of information. Nonlimiting examples are:
  • Event identifier(s)
  • Radio channel measurements e.g., RSRP, RSRQ, SINR
  • UE performances e.g., number of radio link failures, number of connection establishment failures, number of mobility events
  • UE speed connectivity options e.g., single connectivity, different MR-DC connectivity options, such as NR-DC, EN-DC
  • use of unlicensed spectrum a set of QoS parameters
  • set of service types or service subtypes e.g., single connectivity, different MR-DC connectivity options, such as NR-DC, EN-DC
  • the RRC layer of the UE sends to the first network node a THIRD MESSAGE, indicating that one or more event for QoE configuration management is fulfilled. In some embodiments or instances, the RRC layer of the UE sends to the Application layer of the UE a SIXTH MESSAGE, the SIXTH MESSAGE comprising one or more QoE configurations. In some embodiments or instances, the UE RRC sends the QoE configuration to the application once the associated event is triggered. In other embodiments or instances, the UE RRC sends the QoE configuration to the application once the associated event is triggered and a session is ongoing at the application layer.
  • the UE may store Session Start Indication signal at RRC layer and checks if Session start indication is already received from the upper layers (e.g., application). If the Session Start Indication is already received and the triggering condition of the configured event associated to the QoE configuration is met, the QoE configuration will be sent to the application layer.
  • the upper layers e.g., application
  • the application layer may perform the monitoring to determine when the triggering event has occurred and thus when to perform the QoE measurement-related action.
  • the application may inform the radio layer that the event has been fulfilled. If the application layer performs the event monitoring, the option could be that the application layer does not notify the radio layer in the UE that the event has been fulfilled.
  • either or both of the THIRD MESSAGE and FOURTH MESSAGE described above, which inform the network of event fulfilment and application status, respectively, may be omitted, in some embodiments or instances. If the THIRD MESSAGE is omitted, e.g., in the procedure shown in Figure 3, there is no notification that the event has been fulfilled - the UE just silently performs the action conditioned by the event. In this case, of course, the UE should have already received whatever QoE configuration parameters are necessary to carry out the QoE measurement-related action, such that the FIFTH MESSAGE and SIXTH MESSAGE shown in Figure 3 are also omitted. In some cases, only the message informing about the application status is omitted.
  • a RAN node obtains, from the Core Network (e.g., via NGAP) or from 0AM, an “Event for QMC configuration” IE containing an “Event A2” IE (or similar), indicating a level of radio channel quality (e.g., RSRP or RSRQ) to be used as threshold by RAN sends to a UE a QoE configuration or before RAN sends to a UE a signal to activate a pending QoE configuration.
  • an “Event for QMC configuration” IE containing an “Event A2” IE (or similar)
  • a level of radio channel quality e.g., RSRP or RSRQ
  • event-based QoE configuration is provided below, in the form of a modified excerpt of the 3 GPP specifications for the RRC layer, as found in 3GPP TS 38.331.
  • the bolded material is new, relative to previous versions of the specification, and relates to the present techniques.
  • the UE shall:
  • minSchedulingOffsetPreferenceConfig if minSchedulingOffsetPreferenceConfig is set to setup'.
  • releasePreferenceConfig is set to setup'.
  • the UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information.
  • the UE may not succeed e.g., because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g., regarding when to activate GNSS, are up to UE implementation.
  • wlanNameList if wlanNameList is set to setup, include available WLAN measurement results for any subsequent measurement report or any subsequent RLF report, CEF report and SCGFailurelnformation;
  • sensorNameList if sensorNameList is set to setup, include available Sensor measurement results for any subsequent measurement report or any subsequent RLF report, CEF report and SCGFailurelnformation;
  • the UE is requested to attempt to have valid Bluetooth measurements, WLAN measurements and Sensor measurements whenever sending a measurement report for which it is configured to include these measurements.
  • the UE may not succeed e.g., because the user manually disabled the WLAN or Bluetooth or Sensor hardware. Further details, e.g., regarding when to activate WLAN or Bluetooth or Sensor, are up to UE implementation.
  • eventTriggeredQoE is configured and eventID is set to eventA2 and if the event A2 is met according to 5.5.4.3.
  • AssistanceConfig-rl6 ⁇ OPTIONAL, — Need M drx-Pref erenceConf ig-r 16 SetupRelease ⁇ DRX-
  • PreferenceConfig-rl6 ⁇ OPTIONAL, — Need M maxBW-Pref erenceConf ig-r 16 SetupRelease ⁇ MaxBW-
  • MeasConf igAppLayer-rl7 SEQUENCE ⁇ measConf igAppLayerlD-r 17 MeasConf igAppLayerlD-r 17 , measConf igAppLayerContainer-rl7 OCTET STRING, serviceType-rl7 ENUMERATED ⁇ qoe, qoemtsi, spare6, spare5, spare4, spare3, spare2, sparel), eventTriggeredQoE QoETriggerConfig OPTIONAL
  • MeasConf igAppLayerID-rl7 : : INTEGER (1. .maxNrofQoE-rl7)
  • QoETriggerConfig: : SEQUENCE ⁇ eventld CHOICE ⁇ eventAl SEQUENCE ⁇ al -Threshold QoETriggerQuantity hysteresis Hysteresis , timeToTrigger TimeToTrigger ⁇ , eventA2 SEQUENCE ⁇ a2 -Threshold QoETriggerQuantity hysteresis Hysteresis , timeToTrigger TimeToTrigger ⁇ , eventA3 SEQUENCE ⁇ a3-Off set QoETriggerQuantity reportOnLeave BOOLEAN , hysteresis Hysteresis , timeToTrigger TimeToTrigger , useWhiteCellList BOOLEAN ⁇ , eventA4 SEQUENCE ⁇ a4 -Threshold QoETriggerQuantity reportOnLeave BOOLEAN , hysteresis Hysteresis , timeToTrigger TimeToTrigger , useWhiteCell
  • QoETriggerQuantity CHOICE ⁇ rsrp RSRP -Range , rsrq RSRQ -Range , sinr SINR-Range ⁇ end modified specification excerpt -
  • QMC Trigger Quantity and “Hysteresis” can be coded as follows:
  • QoETriggerQuantity : : CHOICE ⁇ rsrp RSRP-Range , rsrq RSRQ-Range , sinr SINR- Range
  • Hysteresis : : INTEGER (0..30)
  • SINR-Range : : INTEGER (0. .127)
  • Figures 6-8 are process flow diagrams illustrating example methods as might be carried out by a wireless device and by one or more network nodes, according to various embodiments or instances of the techniques described in detail above. These should be understood as representing generalizations of several of the detailed techniques explained above, such that many, if not all, of the specific examples and illustrations discussed above should be considered specific embodiments or instances of the methods shown in these figures. Thus, where the terminology used to explain the methods shown in Figures 6-8 differs somewhat from that used in the discussion above, the former should be understood as interchangeable with or inclusive of the terms used in the detailed discussion above.
  • FIG. 6 illustrates a process flow for a method, in a wireless device operating in a wireless network, for performing quality-of-experience (QoE) measurements.
  • this method comprises receiving, from the wireless network, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action.
  • this trigger event is referred to as an “event for QoE configuration management.”
  • identifying the trigger event may mean that the trigger event is explicitly defined, in the QoE measurement configuration message, but might also mean that the trigger event is identified, e.g., by an index.
  • the QoE measurement may be an application-layer measurement.
  • the method further comprises detecting that the identified trigger event has occurred.
  • the method includes performing the measurement-related action with respect to the corresponding QoE measurement, in response to detecting that the identified trigger event has occurred.
  • the measurement-related action comprises one of: initiating the corresponding QoE measurement; inactivating the corresponding QoE measurement; reactivating the corresponding QoE measurement; and releasing the corresponding QoE measurement.
  • the method further comprises sending, to the wireless network, a message indicating that the measurement- related action has been performed.
  • the QoE measurement configuration message further includes one or more QoE configuration parameters, and performing the measurement-related action comprises using the received one or more QoE configuration parameters.
  • the method comprises notifying the wireless network that the identified trigger event has occurred and receiving one or more QoE configuration parameters in response to said notifying, where performing the measurement- related action comprises using the received one or more QoE configuration parameters.
  • the QoE configuration parameters may include one or more of any of the following: a service type; an application layer container; and a QoE reference.
  • the method shown in Figure 6 may further comprise notifying the wireless network that the identified trigger event has occurred, e.g., as shown as the THIRD MESSAGE in Figures 3-5, and receiving, from the wireless network, a confirmation signal indicating that the measurement-related action is to be carried out, e.g., as shown as FIFTH MESSAGE in Figure 3.
  • performing the measurement-related action may be further in response to the confirmation signal.
  • detecting that the identified trigger event has occurred is performed in an RRC layer of the wireless device, and the method comprises the RRC layer of the wireless device providing an application layer of the wireless device with QoE configuration parameters for the measurement-related action, in response to said detecting. In some other embodiments or instances, detecting that the identified trigger event has occurred may be performed in an application layer of the wireless device.
  • FIG. 7 illustrates an example method as might be carried out in a network node operating in a wireless network, for facilitating quality-of-experience (QoE) measurements by a wireless device or group of wireless devices.
  • This method comprises, as shown at block 710, the step of sending, to a wireless device or group of wireless devices, a QoE measurement configuration message, where the QoE measurement configuration message identifies a trigger event associated with a corresponding QoE measurement and measurement-related action.
  • the trigger event is a condition or conditions that must be fulfilled at a wireless device before execution of the measurement-related action.
  • this method further comprises receiving, from at least one wireless device, a message indicating that the trigger event has occurred, as shown at block 720.
  • the method may further comprise sending, to the at least one wireless device, one or more QoE configuration parameters corresponding to the QoE measurement, in response to the message indicating that the trigger event has occurred. This is shown at block 730.
  • the method may comprise sending, to the at least one wireless device, in response to the message indicating that the trigger event has occurred, a message indicating that the at least one wireless device is to carry out the measurement-related action, e.g., as shown as FIFTH MESSAGE in Figure 3.
  • the method comprises receiving, from a second network node, a message defining or indicating the trigger event, e.g., as shown as FIRST MESSAGE in Figures 3-5.
  • the second network node may be an OAM node, for example.
  • the message from the second network node may further identify a condition that must be fulfilled at the first network node before the first network node sends the QoE configuration message to the wireless device or group of wireless devices.
  • Figure 8 illustrates a variant of the above-described method, where the sending of the QoE configuration to the wireless device is triggered by an event, i.e., one or more fulfilled conditions, at the first network node.
  • Figure 8 illustrates a method, in a network node operating in a wireless network, for facilitating quality-of-experience (QoE) measurements by a wireless device or group of wireless devices.
  • QoE quality-of-experience
  • This method comprises receiving, from a second network node, a QoE configuration management message defining a QoE configuration for forwarding to a wireless device or group of wireless devices, where the QoE configuration management message identifies a condition that must be fulfilled at the first network node before the first network node sends the QoE configuration to the wireless device or group of wireless devices.
  • the method further comprises determining that the condition has been fulfilled.
  • the method still further comprises sending the QoE configuration to the wireless device or group of wireless devices, in response to this determination.
  • sending the QoE configuration to the wireless device or group of wireless devices may comprise sending, to the wireless device or group of wireless devices, a QoE measurement configuration message that identifies a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device receiving the QoE measurement configuration message before execution of the measurement-related action.
  • a QoE measurement configuration message that identifies a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device receiving the QoE measurement configuration message before execution of the measurement-related action.
  • Figure 9 shows an example of a communication system 900 in accordance with some embodiments.
  • the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a radio access network (RAN), and a core network 906, which includes one or more core network nodes 908.
  • the access network 904 includes one or more access network nodes, such as network nodes 910a and 910b (one or more of which may be generally referred to as network nodes 910), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 910 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 900 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 910 and other communication devices.
  • the network nodes 910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 912 and/or with other network nodes or equipment in the telecommunication network 902 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 902.
  • the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and/or the telecommunication network 902, and may be operated by the service provider or on behalf of the service provider.
  • the host 916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 902 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunications network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 912 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN- DC).
  • MR-DC multi-radio dual connectivity
  • the hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912c and/or 912d) and network nodes (e.g., network node 910b).
  • the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 914 may be a broadband router enabling access to the core network 906 for the UEs.
  • the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 914 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 914 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 914 may have a constant/persistent or intermittent connection to the network node 910b.
  • the hub 914 may also allow for a different communication scheme and/or schedule between the hub 914 and UEs (e.g., UE 912c and/or 912d), and between the hub 914 and the core network 906.
  • the hub 914 is connected to the core network 906 and/or one or more UEs via a wired connection.
  • the hub 914 may be configured to connect to an M2M service provider over the access network 904 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection.
  • the hub 914 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 910b.
  • the hub 914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 910b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • gaming console or device music storage device, playback appliance
  • wearable terminal device wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • UE any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • wireless device as used herein may be understood to be interchangeable with “UE.”
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010.
  • the processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1002 may include multiple central processing units (CPUs).
  • the input/output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1000.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and/or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.
  • the memory 1010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016.
  • the memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 1010 may allow the UE 1000 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012.
  • the communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022.
  • the communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1018 and/or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1012 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG 11 shows a network node 1100 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR. NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108.
  • the network node 1100 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1100 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1100 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs).
  • the network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1100.
  • RFID Radio Frequency Identification
  • the processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1100 components, such as the memory 1104, to provide network node 1100 functionality.
  • the processing circuitry 1102 includes a system on a chip (SOC).
  • the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1112 and baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.
  • the memory 1104 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computerexecutable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1102.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non
  • the memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100.
  • the memory 1104 may be used to store any calculations made by the processing circuitry 1102 and/or any data received via the communication interface 1106.
  • the processing circuitry 1102 and memory 1104 is integrated.
  • the communication interface 1106 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1106 comprises port(s)/terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. Radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122.
  • the radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102.
  • the radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1120 and/or amplifiers 1122.
  • the radio signal may then be transmitted via the antenna 1110.
  • the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118.
  • the digital data may be passed to the processing circuitry 1102.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110.
  • the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110.
  • all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106.
  • the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).
  • the antenna 1110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.
  • the antenna 1110, communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1108 provides power to the various components of network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein.
  • the network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108.
  • the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100.
  • FIG 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein.
  • the host 1200 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1200 may provide one or more services to one or more UEs.
  • the host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212.
  • processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of host 1200.
  • the memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by a UE for the host 1200 or data generated by the host 1200 for a UE.
  • Embodiments of the host 1200 may utilize only a subset or all of the components shown.
  • the host application programs 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1200 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 13 is a block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1300 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1304 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1308a and 1308b (one or more of which may be generally referred to as VMs 1308), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308.
  • the VMs 1308 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1306.
  • a virtualization layer 1306 Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of VMs 1308, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 1308 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1308, and that part of hardware 1304 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1308 on top of the hardware 1304 and corresponds to the application 1302.
  • Hardware 1304 may be implemented in a standalone network node with generic or specific components. Hardware 1304 may implement some functions via virtualization. Alternatively, hardware 1304 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1310, which, among others, oversees lifecycle management of applications 1302.
  • hardware 1304 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1312 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments.
  • host 1402 Like host 1200, embodiments of host 1402 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1402 also includes software, which is stored in or accessible by the host 1402 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1406 connecting via an over-the-top (OTT) connection 1450 extending between the UE 1406 and host 1402.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1450.
  • the network node 1404 includes hardware enabling it to communicate with the host 1402 and UE 1406.
  • the connection 1460 may be direct or pass through a core network (like core network 906 of Figure 9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 906 of Figure 9
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1406 includes hardware and software, which is stored in or accessible by UE 1406 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1406 with the support of the host 1402.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1406 with the support of the host 1402.
  • an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and host 1402.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1450 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1450 may extend via a connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide the connection between the host 1402 and the UE 1406.
  • the connection 1460 and wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1402 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1406.
  • the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction.
  • the host 1402 initiates a transmission carrying the user data towards the UE 1406.
  • the host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406. The request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406.
  • the transmission may pass via the network node 1404, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402.
  • the UE 1406 executes a client application which provides user data to the host 1402.
  • the user data may be provided in reaction or response to the data received from the host 1402.
  • the UE 1406 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1406. Regardless of the specific manner in which the user data was provided, the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404.
  • the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402.
  • the host 1402 receives the user data carried in the transmission initiated by the UE 1406.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1406 using the OTT connection 1450, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the network’s responsiveness, by providing for improved monitoring of quality-of- experience (QoE) and thereby provide benefits such as improved latency, fewer interruptions or delays in streaming or other time-sensitive services, etc.
  • QoE quality-of- experience
  • factory status information may be collected and analyzed by the host 1402.
  • the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1402 may store surveillance video uploaded by a UE.
  • the host 1402 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1402 and/or UE 1406.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1404. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1402.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Embodiments of the techniques, apparatuses, and systems described above include, but are not limited to, the following enumerated examples.
  • a method, in a wireless device operating in a wireless network, for performing quality-of- experience (QoE) measurements comprising: receiving, from the wireless network, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action; detecting that the identified trigger event has occurred; and performing the measurement-related action with respect to the corresponding QoE measurement, in response to detecting that the identified trigger event has occurred.
  • QoE quality-of- experience
  • the measurement-related action comprises one of: initiating the corresponding QoE measurement; inactivating the corresponding QoE measurement; reactivating the corresponding QoE measurement; and releasing the corresponding QoE measurement.
  • the QoE measurement configuration message further includes one or more QoE configuration parameters, and wherein performing the measurement-related action comprises using the received one or more QoE configuration parameters.
  • the QoE configuration parameters include one or more of any of the following: a service type; an application layer container; and a QoE reference.
  • the QoE configuration parameters include one or more of any of the following: a service type; an application layer container; and a QoE reference.
  • a method in a network node operating in a wireless network, for facilitating quality-of- experience (QoE) measurements by a wireless device or group of wireless devices, the method comprising: sending, to a wireless device or group of wireless devices, a QoE measurement configuration message, the QoE measurement configuration message identifying a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device before execution of the measurement-related action.
  • QoE quality-of- experience
  • a method, in a network node operating in a wireless network, for facilitating quality-of- experience (QoE) measurements by a wireless device or group of wireless devices comprising: receiving, from a second network node, a QoE configuration management message defining a QoE configuration for forwarding to a wireless device or group of wireless devices, wherein the QoE configuration management message identifies a condition that must be fulfilled at the first network node before the first network node sends the QoE configuration to the wireless device or group of wireless devices; determining that the condition has been fulfilled; and sending the QoE configuration to the wireless device or group of wireless devices in response to said determining.
  • QoE configuration management message defining a QoE configuration for forwarding to a wireless device or group of wireless devices, wherein the QoE configuration management message identifies a condition that must be fulfilled at the first network node before the first network node sends the QoE configuration to the wireless device or group of wireless devices; determining that the condition has been fulfilled; and sending the Q
  • sending the QoE configuration to the wireless device or group of wireless devices comprises sending, to the wireless device or group of wireless devices, a QoE measurement configuration message that identifies a trigger event associated with a corresponding QoE measurement and measurement-related action, the trigger event being a condition or conditions that must be fulfilled at a wireless device receiving the QoE measurement configuration message before execution of the measurement- related action.
  • a user equipment for performing quality-of-experience (QoE) measurements comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • QoE quality-of-experience
  • a network node for facilitating quality-of-experience (QoE) measurements by a wireless device or group of wireless devices comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • QoE quality-of-experience
  • a user equipment for performing quality-of-experience (QoE) measurements, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • QoE quality-of-experience
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • OTT over-the-top
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over-the-top
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • the method of the previous embodiment further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • a communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment
  • E-UTRAN Evolved UTRAN gNB Radio base station in NR

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé donné à titre d'exemple pour effectuer des mesures de QoE dans un dispositif sans fil fonctionnant dans un réseau sans fil comprend la réception (610), à partir du réseau sans fil, d'un message de configuration de mesure de QoE, le message de configuration de mesure de QoE identifiant un événement de déclenchement associé à une mesure de QoE correspondante et une action liée à la mesure. Le procédé donné à titre d'exemple comprend en outre la détection (620) que l'événement déclencheur identifié s'est produit et la réalisation (630) de l'action liée à la mesure par rapport à la mesure QoE correspondante, en réponse à la détection du fait que l'événement déclencheur identifié s'est produit. Des exemples de procédés correspondants sont réalisés par un nœud de réseau dans le réseau sans fil.
PCT/SE2022/050643 2021-08-05 2022-06-28 Gestion de configuration de qoe basée sur un événement WO2023014255A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163229691P 2021-08-05 2021-08-05
US63/229,691 2021-08-05

Publications (1)

Publication Number Publication Date
WO2023014255A1 true WO2023014255A1 (fr) 2023-02-09

Family

ID=82611128

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050643 WO2023014255A1 (fr) 2021-08-05 2022-06-28 Gestion de configuration de qoe basée sur un événement

Country Status (1)

Country Link
WO (1) WO2023014255A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200037334A1 (en) * 2016-07-26 2020-01-30 Industrial Technology Research Institute Method and apparatuses for controlling quality of experience based on ue-assisted feedback
WO2020222172A1 (fr) * 2019-05-02 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Procédés d'activation et de désactivation de configurations de mesure par l'intermédiaire d'une liaison
WO2021064254A1 (fr) * 2019-10-04 2021-04-08 NEC Laboratories Europe GmbH Solution d'assurance sls à base d'analyses de données utilisant une mesure de qoe d'ue

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200037334A1 (en) * 2016-07-26 2020-01-30 Industrial Technology Research Institute Method and apparatuses for controlling quality of experience based on ue-assisted feedback
WO2020222172A1 (fr) * 2019-05-02 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Procédés d'activation et de désactivation de configurations de mesure par l'intermédiaire d'une liaison
WO2021064254A1 (fr) * 2019-10-04 2021-04-08 NEC Laboratories Europe GmbH Solution d'assurance sls à base d'analyses de données utilisant une mesure de qoe d'ue

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
3GPP TS 36.331
3GPP TS 36.413
3GPP TS 36.423
3GPP TS 38.331
3GPP TS 38.413
3GPP TS 38.423
ERICSSON: "pCR for TR 38.8xx: NR QoE Measurement Triggering, Configuration, Collection and Reporting", vol. RAN WG3, no. Online; 20200817 - 20200827, 7 August 2020 (2020-08-07), XP051915875, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_109-e/Docs/R3-205201.zip R3-205201 - pCR for TR 38.8xx NR QoE Measurement Triggering, Configuration, Collection and Reporting.docx> [retrieved on 20200807] *
SAMSUNG: "Discussion on NR QoE solutions", vol. RAN WG3, no. Electronic meeting; 20201102 - 20201112, 23 October 2020 (2020-10-23), XP051945626, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_110-e/Docs/R3-206036.zip R3-206036_Discussion on NR QoE solutions.docx> [retrieved on 20201023] *

Similar Documents

Publication Publication Date Title
WO2023014257A1 (fr) Maintenance de configuration de qualité d&#39;expérience
WO2023048628A1 (fr) Procédés, appareil et supports lisibles par ordinateur relatifs à des services à faible latence dans des réseaux sans fil
WO2023012705A1 (fr) Partitionnement d&#39;accès aléatoire et rapport d&#39;accès aléatoire
WO2022240334A1 (fr) Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires
WO2022235187A1 (fr) Procédés, appareil et supports lisibles par ordinateur se rapportant à un rapport de qualité d&#39;expérience dans des réseaux sans fil
WO2023014255A1 (fr) Gestion de configuration de qoe basée sur un événement
WO2024079717A1 (fr) Rapport de rapports qoe au sn
WO2023095037A1 (fr) Rapport mdt journalisé faisant intervenir une mobilité inter-rat
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2024030059A1 (fr) Mesure de qualité d&#39;expérience
WO2023101593A2 (fr) Systèmes et procédés pour rapporter des indications de couche supérieure et une qualité d&#39;expérience dans une connectivité multiple
WO2024096796A1 (fr) Configuration qoe flexible pour gestion de qoe
WO2023101591A1 (fr) Configuration de réduction au minimum des essais en conduite dans un équipement utilisateur
WO2023068980A1 (fr) Procédé et appareil de prise en charge de mesures de qoe
WO2023113672A1 (fr) Commande d&#39;indication dans un réseau de communication sans fil
WO2024107093A1 (fr) Rapport de qualité d&#39;expérience, et rapport de qualité d&#39;expérience visible de réseau d&#39;accès radio lors de défaillances de la liaison radio dans une double connectivité new radio
WO2023014264A1 (fr) Réduction de rapports de relaxation de mesure radio inutile
WO2023011942A1 (fr) Rapport de relaxation de mesure radio précoce
WO2023132774A1 (fr) Gestion de déclencheurs pour rapport qoe visible par ran
WO2023073656A1 (fr) Procédés pour la visibilité de ran d&#39;une session d&#39;enregistrement de qoe
WO2023062509A1 (fr) Activation de cellule secondaire basée sur un signal de référence temporaire par l&#39;intermédiaire d&#39;une commande de ressources radio
AU2022321640A1 (en) Signalling based minimization of drive test configuration availability
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023153991A1 (fr) Configuration de seuil de retard par support radio de données (drb)

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: 22744333

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE