WO2024030059A1 - Mesure de qualité d'expérience - Google Patents

Mesure de qualité d'expérience Download PDF

Info

Publication number
WO2024030059A1
WO2024030059A1 PCT/SE2023/050748 SE2023050748W WO2024030059A1 WO 2024030059 A1 WO2024030059 A1 WO 2024030059A1 SE 2023050748 W SE2023050748 W SE 2023050748W WO 2024030059 A1 WO2024030059 A1 WO 2024030059A1
Authority
WO
WIPO (PCT)
Prior art keywords
qoe
measurement
rrc
state
node
Prior art date
Application number
PCT/SE2023/050748
Other languages
English (en)
Inventor
Luca LUNARDI
Filip BARAC
Johan Rune
Cecilia EKLÖF
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 WO2024030059A1 publication Critical patent/WO2024030059A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • 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

  • Examples of this disclosure relate to Quality of Experience (QoE) measurement, for example in a UE, and to receiving results of at least one QoE measurement, for example in a network node or a Radio Access Network (RAN) node.
  • QoE Quality of Experience
  • RAN Radio Access Network
  • QoE measurements also referred to as “application layer measurements”
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications Service
  • 3GPP 3rd Generation Partnership Project
  • 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
  • MTSI Mobility Telephony Service for IMS
  • VR Virtual Reality
  • QMC Quality of Experience Measurement Collection
  • QoE reports QoE reports
  • An application layer measurement configuration also called QoE measurement configuration or QoE configuration
  • QoE configuration that the RAN receives from the QAM system or the CN is encapsulated in a transparent container, which is forwarded to a UE in a downlink RRC message.
  • An application layer measurement report (also called QoE report) that the UE Access Stratum (UE AS) or UE RRC layer receives from the UE's higher layer (application layer) is encapsulated in a transparent container and sent to network in an uplink RRC message.
  • the RAN then forwards the QoE report to a Measurement Collector Entity (MCE).
  • MCE Measurement Collector Entity
  • 3GPP release 17 a study item for “Study on NR QoE management and optimizations for diverse services” for NR has been approved and concluded.
  • the purpose of the study item was to study solutions for QoE measurements in NR.
  • QoE management in NR will not just collect the quality of experience parameters of streaming services but also consider the typical performance requirements of diverse services (e.g. AR/VR and URLLC, of which at least VR seems to be covered in 3GPP release 17).
  • the NR study also included more adaptive QoE management schemes that enable network optimization to satisfy user experience for diverse services.
  • the configuration data related to QoE measurements (in standard specifications typically referred to as application layer measurements) consists of a service type indication, an indication of an area in which the measurements are to be performed (denoted area scope), an IP address of the entity the collected measurement results (i.e. the QoE reports) should be sent to (often referred to as a MCE, spelled out as Measurement Collector Entity or Measurement Collection Entity, but the entity may sometimes also be referred to as a Trace Collection Entity) and a set of instructions of which type of measurements that should be performed and details of how these measurements are to be performed. These instructions are intended for the application layer in the UE and are placed in a “container” which the network entities handling it, e.g.
  • An area scope is defined in terms of cells or network related areas.
  • an area scope is defined as either a list of cells, a list of routing areas or a list of tracking areas.
  • an area scope is defined as either a list of cells or a list of tracking areas.
  • an area scope will be defined as either a list of cells or a list of tracking areas.
  • QoE and in particular QoE configuration, comes in two flavors: management-based QoE configuration and signaling-based QoE configuration.
  • the QoE configuration originates in the QAM system or some other administrational entity, e.g. dealing with customer satisfaction. All of these entities are in this document referred to as the QAM system (where the QAM system also contains further entities).
  • management-based QoE m-based QoE
  • the QAM system is typically interested in general QoE statistics from a certain area (which is configured as an area scope).
  • the m-based QoE configuration is sent directly from the QAM system to the RAN nodes controlling cells that are within the area scope.
  • Each RAN node selects UEs that are within the area scope (and also fulfills any other relevant condition, such as supporting the concerned application/service type) and sends the m-based QoE configuration to these UEs.
  • the QAM system With signaling-based QoE (s-based QoE), the QAM system is interested in collecting QoE measurement results from a specific UE, e.g. because the user of the UE has filed a complaint.
  • the QAM system sends the s-based QoE configuration to the HSS (in EPS/LTE) or UDM (in 5GS/NR), which forwards the QoE configuration to the UE’s current core network node (CN), e.g. an MME in EPS/LTE or an AMF in 5G/NR.
  • CN core network node
  • the CN then forwards the s-based QoE configuration to the RAN node that serves the concerned UE and the RAN forwards it to the UE.
  • Forwarded to the UE are the service type indication and the container with the measurement instructions.
  • the UE is not aware of whether a received QoE configuration is m-based or s- based.
  • the QoE framework is integrated with the Trace functionality and a Trace ID is associated with each QoE configuration.
  • the QoE functionality will be logically separated from the Trace functionality, but it will still partly reuse the Trace signaling mechanisms.
  • a globally unique QoE reference (formed of MCC+MNC+QMC ID, where the QMC ID is a string of 24 bits) will be associated with each QoE configuration.
  • the QoE reference is included in the container with measurement instructions and also sent to the RAN (i.e., the gNB in NR).
  • the QoE reference is replaced by a shorter identifier denoted as measConfigAppLayerld, which is locally unique within a UE (i.e., there is a one-to-one mapping between a measConfigAppLayerld and a QoE reference for each QoE configuration provided to a UE.
  • the measConfigAppLayerld is stored in the UE Access Stratum and forwarded in an AT Command (which is the type of instructions used in the communication between the UE’s modem part and the UE’s application layer) together with the service type indication and the container with the measurement instructions.
  • AT Command which is the type of instructions used in the communication between the UE’s modem part and the UE’s application layer
  • QoE reports are sent from the UE application layer to the UE Access Stratum, which forwards them to the RAN, which forwards them to the MCE. These QoE measurement results are placed in a “container”, which is uninterpretable for the UE Access Stratum and the RAN. QoE reporting can be configured to be periodic or only sent at the end of an application session. Furthermore, the RAN can instruct the UE to pause QoE reporting, e.g., in case the cell/gNB is in a state of overload.
  • the RAN is not aware of when an application session with an associated QoE measurement session is ongoing, and the UE Access Stratum is also not automatically aware of this.
  • This session start/stop indications can be introduced, which will be sent from the application layer in the UE to the UE AS and from the UE AS to the RAN.
  • a session stop indication may be implicit in the form of a QoE report sent when the application session and the associated QoE measurement session are concluded.
  • the RAN may decide to release a QoE configuration in a UE at any time, as an implementation-based decision. Typically, it is done when the UE has moved outside an area configured for the QoE measurements, commonly referred to as the area scope.
  • One opportunity provided by legacy solutions is also to be able to keep the QoE measurement for the whole session, even during a handover situation. It is also discussed to let the UE continue with the QoE measurements on an ongoing application session until the application session ends, even if the UE in the meantime moves out of the configured area scope.
  • RVQoE RAN visible QoE
  • the RVQoE metrics are derived from the regular QoE metrics, collected and compiled in reports by the UE application layer and delivered to the RAN, so that the RAN may use the reports for various types of optimizations.
  • the RAN can perform adaptive actions to impact the QoE of the concerned application session while the application session is ongoing, such as change various parameters related to the scheduling of the UE and the data flows related to the application session.
  • One aspect of the present disclosure provides a method performed by a User Equipment for performing at least one Quality of Experience (QoE) measurement.
  • the method comprises receiving, from a first Radio Access Network (RAN) Node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and performing the at least one first QoE measurement when the UE is in the first RRC state.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • Another aspect of the present disclosure provides a method performed by a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the method comprises sending, to a User Equipment (UE), at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and receiving, from the UE, information identifying results of the at least one first QoE measurement.
  • UE User Equipment
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • a further aspect of the present disclosure provides a method performed by a network node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the method comprises sending, to a first Radio Access Network (RAN) node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which a User Equipment (UE) is to perform at least one first QoE measurement, and receiving, from a second RAN node, information identifying results of the at least one first QoE measurement by the UE.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • UE User Equipment
  • a still further aspect of the present disclosure provides a User Equipment (UE) for performing at least one Quality of Experience (QoE) measurement.
  • the UE comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the UE is operable to receive, from a first Radio Access Network (RAN) Node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and perform the at least one first QoE measurement when the UE is in the first RRC state.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • An additional aspect of the present disclosure provides a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the first RAN node comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the first RAN node is operable to send, to a User Equipment (UE), at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and receive, from the UE, information identifying results of the at least one first QoE measurement.
  • UE User Equipment
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • the network node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the network node comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the network node is operable to send, to a first Radio Access Network (RAN) node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which a User Equipment (UE) is to perform at least one first QoE measurement, and receive, from a second RAN node, information identifying results of the at least one first QoE measurement by the UE.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • a further aspect of the present disclosure provides a User Equipment (UE) for performing at least one Quality of Experience (QoE) measurement.
  • the UE is configured to receive, from a first Radio Access Network (RAN) Node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and perform the at least one first QoE measurement when the UE is in the first RRC state.
  • RRC Radio Resource Control
  • a still further aspect of the present disclosure provides a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement.
  • RAN Radio Access Network
  • the first RAN node is configured to send, to a User Equipment (UE), at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement, and receive, from the UE, information identifying results of the at least one first QoE measurement.
  • UE User Equipment
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • the network node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the network node is configured to send, to a first Radio Access Network (RAN) node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which a User Equipment (UE) is to perform at least one first QoE measurement, and receive, from a second RAN node, information identifying results of the at least one first QoE measurement by the UE.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • UE User Equipment
  • Figure 1 depicts an example of a method performed by a User Equipment for performing at least one Quality of Experience (QoE) measurement;
  • QoE Quality of Experience
  • Figure 2 depicts an example of a method performed by a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement;
  • RAN Radio Access Network
  • QoE Quality of Experience
  • FIG. 3 depicts another method in accordance with particular embodiments
  • Figure 4 shows an example of a communication system in accordance with some embodiments
  • Figure 5 shows a UE in accordance with some embodiments
  • Figure 6 shows a network node in accordance with some embodiments
  • FIG. 7 is a block diagram of a host in accordance with various aspects described herein;
  • Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 9 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.
  • QoE measurements are collected only in RRC_CONNECTED state, but there is no possibility to configure the UE with QoE measurements when the UE is in non-connected RRC states (e.g.
  • RRCJNACTIVE RRCJDLE
  • MBS Mobility Management Entity
  • examples of this disclosure may provide a solution that enables the collection of QoE measurements and RVQoE measurements in specific UE RRC states and after transitions between the RRC states.
  • the main new aspect is to configure a UE to measure QoE and/or RVQoE indicating one or more RRC states where the UE shall perform the measurements.
  • the UE may also be configured with indications indicating one or more RRC states where the UE shall start, or to continue or to stop performing QoE/RVQoE measurements upon transitioning from one RRC state to another RRC state.
  • examples of this disclosure may provide a possibility to configure QoE measurements/ RAN visible QoE measurements to be performed in specific RRC states, after transitions between the RRC states, and depending on the RRC state
  • FIG. 1 depicts a method 100 in accordance with particular embodiments, for example a method performed by a User Equipment for performing at least one Quality of Experience (QoE) measurement.
  • the method 100 may be performed by a UE or wireless device (e.g. the UE QQ112 or UE QQ200 as described later with reference to Figures 4 and 5 respectively).
  • the method begins at step 102 with receiving, from a first Radio Access Network (RAN) Node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement; and step 104 with performing the at least one first QoE measurement when the UE is in the first RRC state.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • FIG. 2 depicts a method 200 in accordance with particular embodiments, for example a method performed by a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the method 200 may be performed by a network node (e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively).
  • the method begins at step 202 with sending, to a User Equipment (UE), at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement; and step 204 with receiving, from the UE, information identifying results of the at least one first QoE measurement.
  • UE User Equipment
  • QoE Quality of Experience
  • RRC Radio Resource Control
  • Figure 3 depicts a method in accordance with particular embodiments, for example a method performed by a network node for receiving results of at least one Quality of Experience (QoE) measurement.
  • the method 300 may be performed by a network node (e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively).
  • a network node e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively.
  • the method begins at step 302 with sending, to a first Radio Access Network (RAN) node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which a User Equipment (UE) is to perform at least one first QoE measurement; and step 304 with receiving, from a second RAN node, information identifying results of the at least one first QoE measurement by the UE.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • split RAN entities refers to Central Unit-Control Plane (CU-CP), Distributed Unit (DU) and Central Unit- User Plane (CU-UP), unless stated otherwise.
  • CU-CP Central Unit-Control Plane
  • DU Distributed Unit
  • CU-UP Central Unit- User Plane
  • RAN node is used herein to denote (depending on the context), a gNodeB (gNB), eNodeB (eNB), gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, Integrated Access and Backhaul (lAB)-donor, lAB-donor-CU, lAB-donor-CU-CP, gNB-CU-UP, eNB-CU-UP, lAB-donor-CU-UP, gNB-DU, lAB-donor-DU, or eNB-DU.
  • gNB gNodeB
  • eNB eNodeB
  • gNB-CU gNodeB
  • gNB-CU-CP Integrated Access and Backhaul
  • lAB-donor-CU lAB-donor-CU-CP
  • gNB-CU-UP eNB-CU-UP
  • lAB-donor-CU-UP gNB-DU
  • a network node can be a Radio Access Network (RAN) node, an Operations, Administration and Maintenance (QAM), a Core Network node, a Service Management and Orchestration (SMO), a Network Management System (NMS), a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT- RIC), a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB, a Cloud-based network function, a Cloud-based centralized training node.
  • RRC state transition The terms “RRC state transition”, “state
  • QoE configuration refers to all configuration parameters that impact or control the configured entity(entities), or behavior related to application layer measurements, i.e., QoE measurements, in a UE.
  • a QoE configuration contains different configuration parameters for a UE, that is, when the configured entity is a UE, and for a RAN node, e.g., a gNB or an eNB, i.e., when the configured entity is a RAN node.
  • the QoE configuration for a UE comprises at least the parameters in a MeasConfigAppLayer-r17 IE (with the possible exception of the parameters for RVQoE (see below)).
  • the QoE configuration fora RAN node comprises the parameters related to QoE measurement and QoE measurement reporting the RAN node receives from the QAM system (for configuration of management-based QoE measurements) or the parameters related to QoE measurement and QoE measurement reporting the RAN node receives from the CN (e.g. an AMF or an MME) (for configuration of signaling-based QoE measurements).
  • the QAM system for configuration of management-based QoE measurements
  • the CN e.g. an AMF or an MME
  • An RVQoE configuration e.g. consisting of the RVQoE related parameters in a MeasConfigAppLayer-r17 IE may be seen as an integral part of the QoE configuration or as a separate configuration associated with the QoE configuration (and then inherently tied to the QoE configuration).
  • a QoE configuration provided to a UE contains information that the UE uses to determine in which states, e.g. Radio resource Control (RRC) states, it may perform QoE measurements (and/or may start QoE measurements) in accordance with the QoE configuration.
  • RRC Radio resource Control
  • this information consists of a list of RRC states in which the QoE configuration may be considered as valid or active, i.e. the RRC states in which the UE should perform QoE measurements in accordance with the QoE configuration, provided that any other existing conditions are fulfilled, such as that a session is ongoing for an application of the service type that is indicated in the QoE configuration.
  • the term “list” should be interpreted in a generalized sense, such that even a single indication of an RRC state is to be considered as a (trivial form of a) list (e.g., a list with the maximum length of one list item).
  • the list of RRC states in which the QoE configuration may be considered as valid or active can assume cumulative values, e.g. indicating “all RRC states”, or “all NR RRC states”, or “all NR and E-UTRA RRC states”, i.e. the RRC states relevant for QoE configuration are not indicated individually, but rather in an aggregated form, the aggregation being with respect to one specific Radio Access Technology (RAT), or for any RAT.
  • the list can be implemented as:
  • bitmap • as a bitmap, where a bit in a specific position maps to a specific state or combination of states, and the value of the bit indicates whether the state or combination of states is considered as valid or active.
  • the QoE configuration provided to the UE contains two lists of states, e.g. lists of RRC states: one list of states (a first list) in which QoE measurements in accordance with the QoE configuration may be started, and one list of states (a second list) in which QoE measurements in accordance with the QoE configuration may continue, irrespective of which state the QoE measurement was started in.
  • the two lists together thus govern in which RRC states the QoE measurements may be started, and which RRC state transitions the QoE measurements may survive (i.e. continue across or after).
  • these are lists in the general sense which means that each list may also be a single indication of a single state (e.g. a list with the maximum length of one item).
  • at least one of the two lists of RRC states in which the QoE configuration may be considered as valid or active can assume a cumulative value, as described earlier for the case of single list.
  • the two lists may be completely disjunct (i.e. having no common state), partly overlapping (i.e. having a substate of the states in common) or fully overlapping (i.e. being identical with all the listed states in common).
  • a certain state may be part of one of the lists but not the other, or may be part of both lists or may not be included in any of the lists. Note however that a QoE measurement can always continue in the same state as it was started in. That is, for example, if a certain state, e.g.
  • state X is included in the list of states in which the QoE measurement may be started, but not included in the second list, then if the QoE measurement is started in state X, the QoE measurement may continue while the UE remains in state X (and may also continue after transition to one of the RRC states included in the second list in some examples).
  • a certain RRC state e.g. state X
  • the first list i.e. the list of states in which the QoE measurement may be started, but not included in the second list.
  • the QoE measurement may be started in state X, and then, after a state transition to state Y which is included in the second list, continues in state Y, and then the UE transits back to state X.
  • the QoE measurement is allowed to continue after the state transition back to state X in this scenario (because the QoE measurement was started in state X).
  • the QoE measurement is not allowed to continue after the state transition back to state X in this scenario (because state X is not included in the second list).
  • RRC state transitions which QoE measurements may survive (i.e. continue across), e.g. RRC state transitions from state X to state Y, from state X to state Z, but not from state Y to state Z.
  • the indications may indicate that a QoE measurement may survive state transitions from state X to state Z, from state X to state Q and from state Y to state Z but not from state Y to state Q. More details about indications of state transitions a QoE measurement may survive (or should not survive) according to a QoE configuration can be found below.
  • indications of transitions between RRC states a QoE measurement may survive can be implemented as cumulative indications (similarly to the case of cumulative indication of states). For example, it maybe indicated that the QoE measurements should continue for any change of state within NR, or that QoE measurements should be deconfigured upon changing the RAT servicing the UE/towards which the UE is connected to/camped on, from NR to ELITRA.
  • the indication(s) of states in a QoE configuration may in some examples originate in the QAM system, where the overall QoE configuration is created.
  • the indication(s) may be included in the QMC configuration file (which is an XML file interpreted by the UE application that is the end receiver).
  • the indication(s) may be included in the QoE configuration outside the QMC configuration file.
  • the QoE configuration is conveyed to the RAN in accordance with legacy means, i.e. directly from the QAM system to the RAN in case of configuration of management-based QoE measurements, or via the CN (e.g. via the UDM and an AMF in 5G or via the HSS and an MME in 4G) in case of configuration of signaling-based QoE measurements.
  • the indication(s) of states in a QoE configuration may originate in the RAN (e.g. in a gNB or in an eNB). That is, the RAN node would receive a QoE configuration from the QAM system or from the CN and before sending the relevant QoE configuration information to a UE, the RAN node would generate the indication(s) and add it/them to the QoE configuration information to be sent to the UE.
  • the RRC states are an example of states that may be included in the list in the first group of embodiments, or in any of the two lists in the second group of embodiments.
  • only two of the RRC states e.g. RRC_CONNECTED and RRCJNACTIVE, may be included in the list in the first group of embodiments, or in any of the two lists in the second group of embodiments.
  • states that may be included in the list in the first group of embodiments, or in any of the two lists in the second group of embodiments, include substates of RRC states, such as substates the UE may be in during the procedure of transition between two RRC states.
  • states that may be included in the list in the first group of embodiments, or in any of the two lists in the second group of embodiments, include Non- Access Stratum (NAS) level states, such as EMM states or ESM states.
  • NAS Non- Access Stratum
  • RVQoE configurations may include similar state indications as described above for QoE configurations.
  • the indication(s) may be generated in the RAN, but as an alternative, the indication(s) may be sent from the CAM system (via the CN for configuration of signaling-based QoE measurements), to be used for potential RVQoE measurements if any RVQoE measurements are configured by the RAN to be associated with the QoE configuration.
  • the state indication(s) in the QoE configuration apply to any associated RVQoE configuration too.
  • RVQoE measurements in accordance with an RVQoE configuration associated with a QoE configuration may only be performed when the UE is in RRC_CONNECTED state, irrespective of the state indication(s) in the QoE configuration.
  • the state indication(s) is/are included in a MeasConfigAppLayer-r17 IE.
  • the UE When a UE transits to a state in which QoE measurements configured by a certain QoE configuration are not allowed to be performed, in some examples, the UE deletes the QoE configuration. In some examples, when a UE transits to a state in which QoE measurements configured by a certain QoE configuration are not allowed to be started, and no QoE measurement configured by the QoE configuration is ongoing, then the UE deletes the QoE configuration.
  • a RAN node may in some examples independently determine or obtain from another network node (e.g. another RAN node or an QAM node) a QoE/RVQoE configuration indicating a list of RRC states and/or a list of RRC transitions that a UE or a group of UEs should consider to start/pause/stop/resume/deconfigure the QoE and/or RVQoE measurements.
  • the RAN network node sends to a UE a QoE/RVQoE configuration comprising one or more of the following examples: an indication that QoE and/or RVQoE measurements are to be collected in all RRC states; an indication that QoE and/or RVQoE measurements are to be collected only in
  • RRC_CONNECTED state an indication that QoE and/or RVQoE measurements are to be collected only in
  • RRCJNACTIVE state an indication that QoE and/or RVQoE measurements are to be collected only in
  • RRCJDLE state an indication that QoE and/or RVQoE measurements are to be collected only in
  • RRC NACTIVE and RRCJDLE states an indication that QoE and/or RVQoE measurements are to be collected only in
  • RRCJNACTIVE and RRC_CONNECTED states an indication that QoE and/or RVQoE measurements are to be initiated only while the UE is in RRCJNACTIVE and/or RRCJDLE, and/or RRC_CONNECTED state.
  • the indications above may be implemented for example as separate indications, or alternatively as a bit string, where each bit corresponds to a specific state, and if the bit for the specific state is indicated (e.g. set to 1), it means that the UE shall perform QoE measurements for that RRC state.
  • an additional set of conditions for execution thereof may in some examples be defined, where each indication may have a separate set of additional conditions, or the set of additional conditions may apply to any or all or some of the indications.
  • Some non-limiting examples include: “QoE and/or RVQoE measurements can continue upon transitioning from RRC_CONNECTED to RRCJDLE only if a condition A is fulfilled”, or “QoE and/or RVQoE measurements can be start/continue in RRCJNACTIVE if a condition B is fulfilled”.
  • Conditions can refer e.g.
  • the UE may for example be configured to collect QoE and/or RVQoE measurements only during the RRC state transition, and send only one report, (collected during the transition, with the aim of evaluating the QoE during the RRC state transition).
  • the UE can for example be configured to measure and report periodically after the transition, just as it did in the previous state.
  • the indications above may in some examples be configured per measConfigAppLayerld, i.e., per QoE configuration. Alternatively, for example, they may be configured for all QoE configurations.
  • the RAN QoE/RVQoE configuration can comprise an additional indication, that can be combined with any of the previous indication, indicating a specific service type, e.g., MTSI, DASH streaming) to which the indications concerning the RRC states and transitions between RRC states should apply.
  • the RAN QoE/RVQoE configuration can comprise an additional indication, that can be combined with any of the previous indication, indicating a specific type of communication service, (e.g., unicast, broadcast, multicast, MBS) to which the indications concerning the RRC states and transitions between RRC states should apply.
  • a specific type of communication service e.g., unicast, broadcast, multicast, MBS
  • the RAN may in some examples indicate to the UE the Area Scope for the measurements, for the UE to keep track of whether it is in the Area Scope while in RRCJNACTIVE and/or RRCJDLE.
  • the configuration may also contain an instruction to the UE about whether the UE should stop the measurements or continue measuring if it leaves the area scope while in RRC NACTIVE and/or RRCJDLE. Alternatively, it may be left for the UE to decide whether it should stop or continue the measurements when it leaves the Area Scope.
  • the RAN QoE/RVQoE configuration can comprise an additional indication, that can be combined with any of the previous indication, indicating one or more Radio Access Technology to which the indications concerning the RRC states and transitions between RRC states should apply.
  • the RAN QoE/RVQoE configuration can comprise an additional indication, that can be combined with any of the previous indication, indicating one or more network slices (e.g. S-NSSAI) to which the indications concerning the RRC states and transitions between RRC states should apply.
  • network slices e.g. S-NSSAI
  • the RAN QoE/RVQoE configuration can comprise an additional indication, that can be combined with any of the previous indication, indicating whether the indications concerning the RRC states and transitions between RRC states apply or not apply to shared spectrum (e.g. NR-U), or when transitioning from licensed spectrum to shared spectrum or vice versa.
  • shared spectrum e.g. NR-U
  • the different QoE/RVQoE configurations per RRC state may use the same or different measConfigAppLayerld.
  • the different QoE/RVQoE configurations can be per transition between two RRC states. For example, configuration X is used after the UE transits from RRC_CONNECTED to RRC DLE while configuration Y is used after the UE transits from RRC_CONNECTED to RRCJNACTIVE.
  • Figure 4 shows an example of a communication system QQ100 in accordance with some embodiments.
  • the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108.
  • the access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non- 3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 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 QQ100 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 QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs QQ112 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 QQ110 and other communication devices.
  • the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 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 QQ102.
  • the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116.
  • the core network QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108.
  • 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 (ALISF), 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
  • ALISF 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 QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider.
  • the host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, 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 QQ100 of Figure 4 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 QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 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 QQ112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104.
  • 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 QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b).
  • the hub QQ114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs.
  • the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs.
  • the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114.
  • the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub QQ114 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 QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b.
  • the hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d) , and between the hub QQ114 and the core network QQ106.
  • the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection.
  • the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection.
  • the hub QQ114 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 QQ110b.
  • the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, 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 camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted 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
  • LME laptop-embedded equipment
  • LME laptopmounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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 QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 5. 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 QQ202 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 QQ210.
  • the processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).
  • the processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality.
  • the processing circuitry QQ202 may be configured to cause the UE QQ202 to perform the methods as described with reference to Figure 1.
  • the input/output interface QQ206 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 QQ200.
  • 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 QQ208 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 QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.
  • the memory QQ210 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216.
  • the memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • the memory QQ210 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
  • the UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory QQ210 may allow the UE QQ200 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 QQ210, which may be or comprise a device-readable storage medium.
  • the processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212.
  • the communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222.
  • the communication interface QQ212 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 QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface QQ212 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/internet 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/internet 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 QQ212, 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 controls 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 devices which are or which are 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-tracking device
  • 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 3GPP NB-loT 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. 6 shows a network node QQ300 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 NR 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-cel l/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 QQ300 includes processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308, and/or any other component, or any combination thereof.
  • the network node QQ300 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 QQ300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes. For example, 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 QQ300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs).
  • the network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, 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 QQ300.
  • RFID Radio Frequency Identification
  • the processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, network node QQ300 functionality.
  • the processing circuitry QQ302 may be configured to cause the network node to perform the methods as described with reference to Figure 2 and/or 3.
  • the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314.
  • the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips
  • the memory QQ304 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 computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ302.
  • 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
  • the memory QQ304 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 QQ302 and utilized by the network node QQ300.
  • the memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306.
  • the processing circuitry QQ302 and memory QQ304 is integrated.
  • the communication interface QQ306 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 QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322.
  • the radio signal may then be transmitted via the antenna QQ310.
  • the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318.
  • the digital data may be passed to the processing circuitry QQ302.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio frontend circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).
  • the antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.
  • the antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 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 QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 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 QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein.
  • the network node QQ300 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 QQ308.
  • the power source QQ308 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 QQ300 may include additional components beyond those shown in Figure 6 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.
  • FIG. 7 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 4, in accordance with various aspects described herein.
  • the host QQ400 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 QQ400 may provide one or more services to one or more UEs.
  • the host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412.
  • processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412.
  • 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 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.
  • the memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE.
  • Embodiments of the host QQ400 may utilize only a subset or all of the components shown.
  • the host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, 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 QQ414 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 QQ400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs QQ414 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. 8 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 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
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications QQ502 (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 QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.
  • the VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506.
  • Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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 QQ508 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 QQ508, and that part of hardware QQ504 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 QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.
  • Hardware QQ504 may be implemented in a standalone network node with generic or specific components.
  • Hardware QQ504 may implement some functions via virtualization.
  • hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502.
  • hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.
  • host QQ602 Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host QQ602 also includes software, which is stored in or accessible by the host QQ602 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 QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection QQ650.
  • the network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606.
  • the connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 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 QQ606 with the support of the host QQ602.
  • an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602.
  • 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 QQ650 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 connection QQ650.
  • the OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606.
  • the connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host QQ602 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 QQ606.
  • the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction.
  • the host QQ602 initiates a transmission carrying the user data towards the UE QQ606.
  • the host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606.
  • the request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606.
  • the transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602. In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602.
  • the user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604.
  • step QQ620 in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.
  • factory status information may be collected and analyzed by the host QQ602.
  • the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host QQ602 may store surveillance video uploaded by a UE.
  • the host QQ602 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 QQ602 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 QQ602 and/or UE QQ606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. 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 QQ602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.
  • a method performed by a User Equipment for performing at least one Quality of Experience (QoE) measurement comprising: receiving, from a first Radio Access Network (RAN) Node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement; and performing the at least one first QoE measurement when the UE is in the first RRC state.
  • QoE Quality of Experience
  • the one or more RRC messages comprise one or more RRCReconfigurationComplete, UElnformationResponse, RRCResumeComplete, RRCSetupComplete, RRCReestablishmentComplete, MeasurementReport and/or MeasurementReportAppLayer messages.
  • the second RAN node is the same RAN node as the first RAN node or is a different RAN node to the first RAN node.
  • the QoE configuration includes an indication to the UE to start performing the at least one first QoE measurement when the UE enters a first RRC state and/or stop performing the at least one first QoE measurement when the UE enters a second RRC state different to the first state.
  • the at least one QoE measurement configuration identifies a second RRC state in which the UE is to perform at least one second QoE measurement, and wherein the first RRC state is different to the second RRC state, and the method comprises: performing at least the one second QoE measurement according to the at least one QoE measurement configuration.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the second RRC state, in which the UE is to perform at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, in which the UE is to stop performing at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, wherein the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; one or more further RRC states, different to the second RRC state, wherein the UE is to stop performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; and/or one or more further RRC states different to the second R
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one second QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to perform when the UE transitions from the second RRC state to the one of the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing when the UE transitions from the second RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one second QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the second RRC state.
  • the at least one QoE configuration identifies one or more second conditions
  • the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are not fulfilled.
  • the at least one QoE measurement configuration comprises at least one RAN visible QoE (RVQoE) measurement configuration
  • the at least one first QoE measurement comprises at least one first RVQoE measurement.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the first RRC state, in which the UE is to perform at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, in which the UE is to stop performing at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, wherein the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; one or more further RRC states, different to the first RRC state, wherein the UE is to stop performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; and/or one or more further RRC states different to the
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one first QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to perform when the UE transitions from the first RRC state to the one of the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing when the UE transitions from the first RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one first QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the first RRC state.
  • the at least one QoE configuration identifies one or more first conditions
  • the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are not fulfilled.
  • the at least one QoE measurement configuration identifies one or more of: one or more services and/or service types for which the UE is to perform the at least one first QoE measurement; one or more Radio Access Technologies (RATs), wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more RATs; one or more network slices, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more network slices; one or more spectrum types, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on a cell using a frequency corresponding to one of the one or more spectrum types; one or more connection service types, wherein the UE is to perform the at least one QoE measurement for the one or more connection service types.
  • RATs Radio Access Technologies
  • the one or more spectrum types comprise licensed spectrum and/or unlicensed/shared spectrum; and/or the one or more connection service types comprise unicast, broadcast, multicast and/or Multimedia Broadcast Service (MBS).
  • MBS Multimedia Broadcast Service
  • the first RRC state comprises a RRC connected state, RRC non-connected state, RRC idle state, RRC inactive state and/or transition state between different RRC states.
  • a method performed by a first Radio Access Network (RAN) node for receiving results of at least one Quality of Experience (QoE) measurement comprising: sending, to a User Equipment (UE), at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which the UE is to perform at least one first QoE measurement; and receiving, from the UE, information identifying results of the at least one first QoE measurement.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • RRC messages comprise one or more RRCReconfigurationComplete, UElnformationResponse, RRCResumeComplete, RRCSetupComplete, RRCReestablishmentComplete, MeasurementReport and/or MeasurementReportAppLayer messages.
  • the QoE configuration includes an indication to the UE to start performing the at least one first QoE measurement when the UE enters a first RRC state and/or stop performing the at least one first QoE measurement when the UE enters a second RRC state different to the first state.
  • the method comprises: receiving, from the UE, information identifying results of the at least one second QoE measurement.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the second RRC state, in which the UE is to perform at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, in which the UE is to stop performing at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, wherein the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; one or more further RRC states, different to the second RRC state, wherein the UE is to stop performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; and/or one or more further RRC states different to the second RRC
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one second QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to perform when the UE transitions from the second RRC state to the one of the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing when the UE transitions from the second RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one second QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the second RRC state.
  • the at least one QoE configuration identifies one or more second conditions, and includes an indication that the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are not fulfilled.
  • the at least one QoE measurement configuration comprises at least one RAN visible QoE (RVQoE) measurement configuration
  • the at least one first QoE measurement comprises at least one first RVQoE measurement.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the first RRC state, in which the UE is to perform at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, in which the UE is to stop performing at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, wherein the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; one or more further RRC states, different to the first RRC state, wherein the UE is to stop performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; and/or one or more further RRC states
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one first QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to perform when the UE transitions from the first RRC state to the one of the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing when the UE transitions from the first RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one first QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the first RRC state.
  • any of embodiments 36 to 38 wherein the at least one QoE configuration identifies one or more first conditions, an includes an indication that the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are not fulfilled.
  • TCE T race Collector Entity
  • MCE Measurement Collector Entity
  • QAM Operations Administration and Maintenance
  • SMO Service Management Orchestration
  • the at least one QoE measurement configuration identifies one or more of: one or more services and/or service types for which the UE is to perform the at least one first QoE measurement; one or more Radio Access Technologies (RATs), wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more RATs; one or more network slices, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more network slices; one or more spectrum types, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on a cell using a frequency corresponding to one of the one or more spectrum types; one or more connection service types, wherein the UE is to perform the at least one QoE measurement for the one or more connection service types.
  • RATs Radio Access Technologies
  • the one or more spectrum types comprise licensed spectrum and/or unlicensed/shared spectrum; and/or the one or more connection service types comprise unicast, broadcast, multicast and/or Multimedia Broadcast Service (MBS).
  • MBS Multimedia Broadcast Service
  • the first RRC state comprises a RRC connected state, RRC non-connected state, RRC idle state, RRC inactive state and/or transition state between different RRC states.
  • a method performed by a network node for receiving results of at least one Quality of Experience (QoE) measurement comprising: sending, to a first Radio Access Network (RAN) node, at least one Quality of Experience (QoE) measurement configuration that identifies a first Radio Resource Control (RRC) state in which a User Equipment (UE) is to perform at least one first QoE measurement; and receiving, from a second RAN node, information identifying results of the at least one first QoE measurement by the UE.
  • RAN Radio Access Network
  • QoE Quality of Experience
  • the QoE configuration includes an indication to the UE to start performing the at least one first QoE measurement when the UE enters a first RRC state and/or stop performing the at least one first QoE measurement when the UE enters a second RRC state different to the first state.
  • the method comprises: receiving, from the second network node, information identifying results of the at least one second QoE measurement by the UE.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the second RRC state, in which the UE is to perform at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, in which the UE is to stop performing at least a subset of the at least one second QoE measurement; one or more further RRC states, different to the second RRC state, wherein the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; one or more further RRC states, different to the second RRC state, wherein the UE is to stop performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states; and/or one or more further RRC states different to the second R
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one second QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to perform when the UE transitions from the second RRC state to the one of the one or more further RRC states; the at least a subset of the at least one second QoE measurement that the UE is to stop performing when the UE transitions from the second RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one second QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the second RRC state.
  • the at least one QoE configuration identifies one or more second conditions, and includes an indication that the UE is to continue performing at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one second QoE measurement when the UE transitions from the second RRC state to one of the one or more further RRC states if the one or more second conditions are not fulfilled.
  • the at least one QoE second measurement comprises at least one second RVQoE measurement.
  • the at least one QoE measurement configuration comprises at least one RAN visible QoE (RVQoE) measurement configuration
  • the at least one first QoE measurement comprises at least one first RVQoE measurement.
  • the at least one QoE measurement configuration identifies at least one of: one or more further RRC states, different to the first RRC state, in which the UE is to perform at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, in which the UE is to stop performing at least a subset of the at least one first QoE measurement; one or more further RRC states, different to the first RRC state, wherein the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; one or more further RRC states, different to the first RRC state, wherein the UE is to stop performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states; and/or one or more further RRC states, different to the first RRC state, different to the first R
  • the at least one QoE configuration includes an indication to the UE to, if all QoE measurements according to the at least one QoE measurement configuration are stopped when the UE transitions from the first RRC state to one of the one or more further RRC states, deconfigure or delete the at least one QoE measurement configuration.
  • the at least one QoE configuration identifies at least one of: the at least a subset of the at least one first QoE measurement that the UE is to perform in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing in the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to perform when the UE transitions from the first RRC state to the one of the one or more further RRC states; the at least a subset of the at least one first QoE measurement that the UE is to stop performing when the UE transitions from the first RRC state to the one of the one or more further RRC states; and/or the at least a subset of the at least one first QoE measurement that the UE is to start performing when the UE transitions from one of the one or more further RRC states to the first RRC state.
  • the at least one QoE configuration identifies one or more first conditions, an includes an indication that the UE is to continue performing at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are fulfilled, and the UE is to stop performing the at least a subset of the at least one first QoE measurement when the UE transitions from the first RRC state to one of the one or more further RRC states if the one or more first conditions are not fulfilled.
  • the network node comprises a Trace Collector Entity (TCE), Measurement Collector Entity (MCE), an Operations Administration and Maintenance (QAM) node or a Service Management Orchestration (SMO) node.
  • TCE Trace Collector Entity
  • MCE Measurement Collector Entity
  • QAM Operations Administration and Maintenance
  • SMO Service Management Orchestration
  • the at least one QoE measurement configuration identifies one or more of: one or more services and/or service types for which the UE is to perform the at least one first QoE measurement; one or more Radio Access Technologies (RATs), wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more RATs; one or more network slices, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on one of the one or more network slices; one or more spectrum types, wherein the UE is to perform the at least one QoE measurement when the UE is connected to or camped on a cell using a frequency corresponding to one of the one or more spectrum types; one or more connection service types, wherein the UE is to perform the at least one QoE measurement for the one or more connection service types.
  • the one or more spectrum types comprise licensed spectrum
  • the first RRC state comprises a RRC connected state, RRC non-connected state, RRC idle state, RRC inactive state and/or transition state between different RRC states.
  • a user equipment comprising: processing circuitry configured to cause the user equipment 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.
  • a network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • a user equipment 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
  • 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.
  • UE user equipment
  • 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. 77. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • 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.
  • a method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • 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.
  • a method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • 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.
  • the communication system of the previous embodiment further comprising: the network node; and/or the user equipment.
  • 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.
  • the method of the previous embodiment further comprising at the network node, transmitting the received user data to the host.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des procédés et un appareil sont divulgués. Dans un exemple, l'invention concerne un procédé mis en œuvre par un équipement utilisateur pour mettre en œuvre au moins une mesure de qualité d'expérience (QoE). Le procédé comprend la réception, en provenance d'un premier nœud de réseau d'accès radio (RAN), d'au moins une configuration de mesure de qualité d'expérience (QoE) qui identifie un premier état de commande de ressource radio (RRC) dans lequel l'UE doit mettre en œuvre au moins une première mesure de QoE. Le procédé comprend également la mise en œuvre de l'au moins une première mesure de QoE lorsque l'UE est dans le premier état RRC.
PCT/SE2023/050748 2022-08-04 2023-07-20 Mesure de qualité d'expérience WO2024030059A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263395040P 2022-08-04 2022-08-04
US63/395,040 2022-08-04

Publications (1)

Publication Number Publication Date
WO2024030059A1 true WO2024030059A1 (fr) 2024-02-08

Family

ID=87474049

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050748 WO2024030059A1 (fr) 2022-08-04 2023-07-20 Mesure de qualité d'expérience

Country Status (1)

Country Link
WO (1) WO2024030059A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022075903A1 (fr) * 2020-10-09 2022-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de mesure de qualité d'expérience
US20220217560A1 (en) * 2021-01-05 2022-07-07 Qualcomm Incorporated Handling of nr qoe measurements and qoe reporting in rrc modes

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022075903A1 (fr) * 2020-10-09 2022-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de mesure de qualité d'expérience
US20220217560A1 (en) * 2021-01-05 2022-07-07 Qualcomm Incorporated Handling of nr qoe measurements and qoe reporting in rrc modes

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Handling of NR QoE measurements", vol. RAN WG2, no. Electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), XP051974268, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_113-e/Docs/R2-2101338.zip R2-2101338 - Handling of NR QoE measurements.docx> [retrieved on 20210115] *

Similar Documents

Publication Publication Date Title
WO2023014255A1 (fr) Gestion de configuration de qoe basée sur un événement
WO2024030059A1 (fr) Mesure de qualité d&#39;expérience
US20240334226A1 (en) Early radio measurement relaxation reporting
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
WO2024027838A1 (fr) Procédé et appareil pour arrêter un rapport de localisation
US20240298203A1 (en) Signalling based minimization of drive test configuration availability
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2024096796A1 (fr) Configuration qoe flexible pour gestion de qoe
WO2024210794A1 (fr) Vérification de plmn pour des mesures de quoe pendant la mobilité d&#39;un ue dans différents états rrc
WO2024033811A1 (fr) Signalisation de contexte d&#39;ue et de données de ng-ran à un réseau cœur
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
WO2024172726A1 (fr) Systèmes et procédés de signalisation de paramètres de différenciation de radiomessagerie
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2024144446A1 (fr) Optimisation de plan de commande pendant un changement d&#39;amf
EP4430885A1 (fr) Systèmes et procédés d&#39;interdiction d&#39;itinérance en cas de sinistre par des équipements d&#39;utilisateur dans des cellules réservées à une utilisation par un opérateur
WO2024035311A1 (fr) Minimisation de portée de configuration de tests de disque pour différents types de réseau
WO2024181906A1 (fr) Procédés et appareils pour libérer ou suspendre une ou plusieurs configurations de qualité d&#39;expérience lors d&#39;un transfert entre des technologies d&#39;accès radio
WO2024210799A1 (fr) Transmission d&#39;indications de début et d&#39;arrêt de session d&#39;application en double connectivité pour des mesures qoe/rvqoe
WO2023068977A1 (fr) Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n&#39;importe quel état de sélection de cellule
WO2023187685A1 (fr) Collecte de données à partir d&#39;un équipement utilisateur sur une utilisation de politique de sélection d&#39;itinéraire d&#39;équipement utilisateur
WO2023095037A1 (fr) Rapport mdt journalisé faisant intervenir une mobilité inter-rat
WO2023014264A1 (fr) Réduction de rapports de relaxation de mesure radio inutile
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
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence

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

Country of ref document: EP

Kind code of ref document: A1