WO2022075903A1 - Configuration de mesure de qualité d'expérience - Google Patents

Configuration de mesure de qualité d'expérience Download PDF

Info

Publication number
WO2022075903A1
WO2022075903A1 PCT/SE2021/050879 SE2021050879W WO2022075903A1 WO 2022075903 A1 WO2022075903 A1 WO 2022075903A1 SE 2021050879 W SE2021050879 W SE 2021050879W WO 2022075903 A1 WO2022075903 A1 WO 2022075903A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
network
measurement configuration
qoe
qoe measurement
Prior art date
Application number
PCT/SE2021/050879
Other languages
English (en)
Inventor
Luca LUNARDI
Ali PARICHEHREHTEROUJENI
Pradeepa Ramachandra
Johan Rune
Filip BARAC
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 WO2022075903A1 publication Critical patent/WO2022075903A1/fr

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0044—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of quality context information

Definitions

  • Examples of the present disclosure relate to Quality of Experience (QoE) measurement configuration, for example for a wireless device.
  • QoE Quality of Experience
  • QoE measurements have been specified for Long Term Evolution (LTE) and Universal Mobile Telecommunications System (UMTS).
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • 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 IP Multimedia Subsystem, IMS) services are supported.
  • Quality of Experience Measurement Collection enables configuration of application layer measurements in the UE and transmission of QoE measurement result files by means of Radio Resource Control (RRC) signalling.
  • RRC Radio Resource Control
  • Application layer measurement configuration received from Operations, Administration and Maintenance (QAM) or Core Network (CN) is encapsulated in a transparent container, which is forwarded to UE in a downlink RRC message.
  • Application layer measurements received from UE's higher layer are encapsulated in a transparent container and sent to network in an uplink RRC message.
  • the result container at forwarded to a TCE, Trace Collector Entity.
  • NR New Radio
  • QoE management in NR will not just collect the experience parameters of streaming services but also consider the typical performance requirements of diverse services (e.g. Augmented Reality/Virtual Reality and Ultra Reliable Low Latency Communications, URLLC).
  • the NR study will also include more adaptive QoE management schemes that enable network intelligent optimization to satisfy user experience for diverse services.
  • the measurements may be initiated towards the Radio Access Network (RAN) in management-based manner, i.e. from an O&M node in a generic way e.g. for a group of UEs, or they may also be initiated in a signaling-based manner, i.e. initiated from CN to Radio Access Network (RAN) e.g. for a single User Equipment (UE).
  • RAN Radio Access Network
  • the configuration of the measurement includes the measurement details, which is encapsulated in a container that is transparent to RAN.
  • the measurement When initiated via the core network, the measurement is started towards a specific UE.
  • the "TRACE START" S1AP message is used, which carries, among others, the details about the measurement configuration the application should collect (in the “Container for application layer measurement configuration” IE, transparent to the RAN) and the details to reach the trace collection entity to which the measurements should be sent.
  • the RAN is not aware of when the streaming session is ongoing in the UE Access Stratum is also not aware of when the measurements are ongoing. It is an implementation decision when RAN stops the measurements. Typically, it is done when the UE has moved outside the measured area.
  • One opportunity provided by the legacy solution is also to be able to keep the QoE measurement for the whole session, even during handover situation.
  • UTRAN can request the UE to report its capability via “UE Capability Enquiry”.
  • the UE can provide its capability using the “UE Capability Information” RRC message.
  • the “UE Capability Information” message can include the “UE radio access capability”.
  • the “Measurement Capability” IE can be used from the UE to transfer to the UMTS Terrestrial Radio Access Network (UTRAN) the information related to the capability to perform the QoE meaurement collection for streaming services and/or Multimedia Telephony Service for IMS (MTSI) services.
  • UTRAN UMTS Terrestrial Radio Access Network
  • the LITRAN can send a “Measurement Control” RRC message containing “Application layer measurement configuration”.
  • the UE can send QoE measurement results via UTRAN to the Collecting Entity using the “Measurement Report” RRC message and including the “Application layer measurement reporting” IE.
  • the UE may also perform Cell Update with cause “application layer measurement report available” in order to initiate the transfer of application layer measurement report.
  • Signalling Radio Bearer SRB4 shall be used for the MEASUREMENT REPORT message carrying the IE "Application layer measurement reporting”.
  • the UE capability transfer is used to transfer UE radio access capability information from the UE to E-UTRAN.
  • the UE-EUTRA-Capability IE is used to convey the E-UTRA UE Radio Access Capability Parameters and the Feature Group Indicators for mandatory features to the network.
  • the UE can include the “UE- EUTRA-Capability” IE.
  • the “UE-EUTRA-Capability” IE may include the UE-EUTRA- Capability-v1530-1 E which can be used by the UE to indicate whether the UE supports or not QoE Measurement Collection for streaming services and/or MTSI services, as detailed in the “MeasParameters-v1530” encoding below.
  • a UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when measConfigAppLayer has been configured by E-UTRAN.
  • the RRCConnectionReconfiguration message is used to reconfigure the UE to setup or release the UE for Application Layer measurements. This is signaled in the measConfigAppLayer-15 IE within the “OtherConfig” IE.
  • the setup includes the transparent container measConfigAppLayerContainer which specifies the QoE measurement configuration for the Application of interest and the serviceType IE to indicates the Application (or service) for which the QoE measurements are being configured.
  • Supported services are streaming and MTSI.
  • the measConfigAppLayerToAddModList-r16 may be used to add or modify multiple QoE measurement configurations (up to maxQoE-Measurement-r16).
  • the measConfigAppLayerToReleaseList-r16 IE may be used to remove multiple QoE measurement configuration (up to maxQoE-Measurement-r16).
  • the MeasReportAppLayer RRC message is used by the UE to send to the E-UTRAN node the QoE measurement results of an Application (or service).
  • the service for which the report is being sent is indicated in the “serviceType” IE.
  • a UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when measConfigAppLayer has been configured by E-UTRAN.
  • the “UE Application layer measurement configuration” IE is described in 3GPP TS 36.413 V16.3.0, which is incorporated herein by reference.
  • the area scope parameter defines the area in terms of cells or Tracking Area/Routing Area/Location Area where the QMC shall take place. If the parameter is not present the QMC shall be done throughout the Public Land Mobile Network (PLMN) specified in PLMN target.
  • PLMN Public Land Mobile Network
  • the area scope parameter in UMTS is either:
  • CGI Cell Global Identity
  • LAI Location Area Identity
  • the area scope parameter in LTE is either: list of cells, identified by E-UTRAN-CGI. Maximum 32 CGI can be defined.
  • TAC T racking Area Code
  • the parameter is mandatory if area based QMC is requested.
  • an HSDN cell has higher priority than other cells for cell reselection for HSDN capable UE in a High-mobility state as described below (3GPP TS 36.304, clause 5.2.4.1):
  • the UE shall always consider the HSDN cells to be the highest priority (i.e. higher than any other network configured priorities).
  • the UE shall always consider HSDN cells to be the lowest priority (i.e. lower than network configured priorities).
  • An HSDN cell is signaled in TS 36.331 V16.0.0 by the field hsdn-Cell, broadcasted in the System Information.
  • Non-Public networks are intended for the sole use of a private entity such as an enterprise, and may be deployed in a variety of configurations, utilizing both virtual and physical elements. Specifically, they may be deployed as completely standalone networks, they may be hosted by a PLMN, or they may be offered as a slice of a PLMN.
  • unauthorized UEs those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs may be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs may be able to access both a non-public network and a PLMN where specifically allowed.
  • NPN Non-Public Network
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • SNPN PLMN Stand-alone Non- Public Network
  • a SNPN network is identified by the combination of a PLMN ID and a Network identifier (NID).
  • NID Network identifier
  • PNI-NPNs Public Network Integrated NPNs
  • Public Network Integrated NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN.
  • PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN.
  • the UE shall have a subscription for the PLMN in order to access PNI-NPN.
  • a Closed Access Group identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG.
  • CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s).
  • a CAG cell is a cell broadcasting at least one CAG identity.
  • a CAG-only cell is a cell that is only available for normal service for CAG UEs.
  • a NPN-only Cell is a cell that is only available for normal service for NPNs' subscriber.
  • An NPN-capable UE determines that a cell is NPN-only Cell by detecting that the cellReservedForOtherUse IE is set to true while the npn- IdentitylnfoList IE is present in CellAccessRelatedlnfo. lAB-nodes
  • An Integrated Access and Backhaul (lAB)-node is a RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes.
  • the NG-RAN supports IAB by the lAB-node wirelessly connecting to the gNB capable of serving the lAB-nodes, named lAB-donor.
  • the lAB-donor consists of an lAB-donor-CU and one or more lAB-donor-DU(s).
  • the lAB-donor may consist of an lAB-donor- CLI-CP, multiple lAB-donor-CU-UPs and multiple lAB-donor-DUs.
  • the lAB-node connects to an upstream lAB-node or an lAB-donor-DU via a subset of the UE functionalities of the NR llu interface (named IAB-MT function of lAB-node).
  • the lAB- node provides wireless backhaul to the downstream lAB-nodes and UEs via the network functionalities of the NR Uu interface (named IAB-DU function of lAB-node).
  • IAB The overall architecture of IAB is shown in 3GPP TS 38.401 V16.3.0, which is incorporated herein by reference.
  • an IAB node connecting itself to an upstream node can indicate that it is an IAB node (rather than a regular UE) by setting the iab-Nodelndication-r16 to ‘true’ in the RRCSetupComplete message.
  • a Network Slice instance is defined within a PLMN and shall include:
  • the W-AGF function to the Wireline Access Network Network slices may differ for supported features and network functions optimisations, in which case such Network Slices may have e.g. different S-NSSAIs with different Slice/Service Types.
  • An S-NSSAI identifies a Network Slice and it is comprised of:
  • SST A Slice/Service type (SST), which refers to the expected Network Slice behavior in terms of features and services;
  • SD Slice Differentiator
  • Standardized SST values provide a way for establishing global interoperability for slicing so that PLMNs can support the roaming use case more efficiently for the most commonly used Slice/Service Types.
  • the SSTs which are standardised are in Table 5.15.2.2- 1 from TS 23.501 V16.6.0.
  • MBMS Multimedia Broadcast Multicast Services
  • An example architecture for MBMS consists of Evolved Packet Core (EPC) functional entities and E-UTRAN nodes.
  • EPC Evolved Packet Core
  • Functions of MBMS EPC entities are defined in TS 23.246 V16.1.0, which is incorporated herein by reference.
  • Functions of MBMS E-UTRAN nodes are defined in TS 36.300 V16.3.0, which is incorporated herein by reference. It should be noted that TS 36.300 also allows MCE be deployed inside eNodeB.
  • M3, M2 interfaces are pure control plane interfaces.
  • M3 interface between Mobility Management Entity (MME) and Multi- cell/multicast Coordination Entity (MCE) mainly carries MBMS session management signaling.
  • a MCE is connected to one or more than one eNBs within the same Multicast-broadcast single-frequency network (MBSFN) through M2 interface mainly for MBMS session management signaling and radio configuration signaling.
  • M1 interface is a pure user plane interface.
  • a MBMS gateway (GW) is connected to multiple eNBs through M1 interface for data distribution.
  • MIB-MBMS MasterlnformationBlock-MBMS
  • SIB1-MBMS SystemlnformationBlockType1-MBMS
  • MasterlnformationBlock-MBMS defines the most essential physical layer information of the cell required to receive further system information on MBMS-dedicated cell
  • SystemlnformationBlockType1-MBMS contains information relevant for receiving MBMS service and defines the scheduling of other system information blocks on MBMS-dedicated cell;
  • Narrowband-Internet of Things provides access to network services using physical layer optimized for very low power consumption (e.g. full carrier bandwidth is 180 kHz, subcarrier spacing can be 3.75 kHz or 15 kHz).
  • MIB- NB MasterlnformationBlock-NB
  • SIBs-NB SystemlnformationBlocks-NB
  • MasterlnformationBlock-NB defines the most essential information of the cell required to receive further system information
  • SystemlnformationBlockType1-NB contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information blocks;
  • SystemlnformationBlockType2-NB contains common radio resource configuration information
  • SystemlnformationBlockType3-NB contains cell re-selection information for intrafrequency, inter-frequency
  • SystemlnformationBlockType4-NB contains neighboring cell related information relevant for intra-frequency cell re-selection
  • SystemlnformationBlockType5-NB contains neighboring cell related information relevant for inter-frequency cell re-selection
  • SystemlnformationBlockType14-NB contains information about access barring
  • SystemlnformationBlockType15-NB contains information related to mobility procedures for MBMS reception
  • SystemlnformationBlockType16-NB contains information related to GPS time and Coordinated Universal Time (UTC);
  • SystemlnformationBlockType20-NB contains information related to SC-PTM
  • SystemlnformationBlockType22-NB contains common radio resource configuration information for paging and random access procedure on non-anchor carriers; • SystemlnformationBlockType23-NB contains common additional radio resource configuration information for random access procedure on anchor and non-anchor carriers;
  • SystemlnformationBlockType27-NB contains assistance information for inter-RAT cell selection to E-UTRAN and/or GERAN.
  • LAA Licensed-Assisted Access
  • the configured set of serving cells for a UE therefore always includes at least one SCell operating in the unlicensed spectrum according to Frame structure Type 3, also called LAA SCell.
  • LAA eNB and UE apply Listen-Before-Talk (LBT) before performing a transmission on LAA SCell.
  • LBT Listen-Before-Talk
  • the transmitter listens to/senses the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission; otherwise, it does not perform the transmission.
  • NR-U NR in shared/unlicensed spectrum
  • NR Radio Access operating with shared spectrum channel access can operate in different modes where either PCell, PSCell, or SCells can be in shared spectrum and an SCell may or may not be configured with uplink.
  • NR Radio Access operating with shared spectrum channel access can support the following deployment scenarios:
  • Scenario A Carrier aggregation between NR in licensed spectrum (PCell) and NR in shared spectrum (SCell);
  • Scenario B Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell);
  • Scenario D NR cell in shared spectrum and uplink in licensed spectrum
  • Scenario E Dual connectivity between NR in licensed spectrum and NR in shared spectrum. Carrier aggregation of cells in shared spectrum is applicable to all deployment scenarios.
  • the gNB operates in either dynamic or semi-static channel access mode as described in TS 37.213 V16.3.0.
  • the gNB and UE may apply Listen- Before-Talk (LBT) before performing a transmission on a cell configured with shared spectrum channel access.
  • LBT Listen- Before-Talk
  • the transmitter listens to/senses the channel to determine whether the channel is free or busy and performs transmission only if the channel is sensed free.
  • Non-Terrestrial Networks support
  • a non-terrestrial network refers to a network, or segment of networks using RF resources on board a satellite (or UAS platform).
  • a Non-Terrestrial Network typically features the following elements:
  • a GEO satellite is fed by one or several sat-gateways which are deployed across the satellite targeted coverage (e.g. regional or even continental coverage).
  • sat-gateways which are deployed across the satellite targeted coverage (e.g. regional or even continental coverage).
  • Non-GEO satellite served successively by one or several sat-gateways at a time.
  • the system ensures service and feeder link continuity between the successive serving sat- gateways with sufficient time duration to proceed with mobility anchoring and hand-over
  • a satellite which may implement either a transparent or a regenerative (with on board processing) payload.
  • the satellite or UAS platform
  • the footprints of the beams are typically of elliptic shape.
  • the field of view of a satellites (or UAS platforms) depends on the on board antenna diagram and min elevation angle.
  • a transparent payload Radio Frequency filtering, Frequency conversion and amplification. Hence, the waveform signal repeated by the payload is un-changed;
  • - A regenerative payload Radio Frequency filtering, Frequency conversion and amplification as well as demodulation/decoding, switch and/or routing, coding/modulation. This is effectively equivalent to having all or part of base station functions (e.g. gNB) on board the satellite (or UAS platform).
  • base station functions e.g. gNB
  • ISL Inter-satellite links
  • ISL may operate in RF frequency or optical bands.
  • - User Equipment are served by the satellite (or UAS platform) within the targeted service area.
  • One aspect of the present disclosure provides a method performed by a wireless device.
  • the method comprises receiving a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • the method also comprises applying the QoE measurement configuration.
  • Another aspect of the present disclosure provides a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurements.
  • the method comprises sending a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • a further aspect of the present disclosure provides a wireless device comprising a processor and a memory.
  • the memory contains instructions executable by the processor such that the wireless device is operable to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration, and apply the QoE measurement configuration.
  • QoE Quality of Experience
  • a still further aspect of the present disclosure provides a network node for configuring a wireless device for Quality of Experience (QoE) measurements.
  • the network node comprises a processor and a memory.
  • the memory containing instructions executable by the processor such that the network node is operable to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • Another aspect of the present disclosure provides a wireless device configured to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration, and apply the QoE measurement configuration.
  • QoE Quality of Experience
  • An additional aspect of the present disclosure provides a network node for configuring a wireless device for performing and/or reporting Quality of Experience (QoE) measurements.
  • the network node is configured to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • Figure 1 shows an example of a method in accordance with some embodiments
  • Figure 2 shows an example of a method in accordance with some embodiments
  • Figure 3 shows an example of a method in accordance with some embodiments
  • FIG. 4 shows virtualization apparatus in accordance with some embodiments
  • FIG. 5 shows virtualization apparatus in accordance with some embodiments
  • FIG. 6 shows virtualization apparatus in accordance with some embodiments
  • Figure 7 shows an example of a wireless network in accordance with some embodiments
  • Figure 8 shows an example of a User Equipment (UE) in accordance with some embodiments
  • Figure 9 is a schematic block diagram illustrating a virtualization environment in accordance with some embodiments
  • Figure 10 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • Figure 11 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • Figure 12 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 13 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 14 shows methods implemented in a communication system in accordance with some embodiments.
  • Figure 15 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the QoE measurement configuration may be enhanced by extending the definition of the Area Scope with at least one or a combination of two or more of the following characteristics:
  • the Radio Access Technology (RAT) in use (e.g., the Area Scope may be restricted based on the RAT used in the cell or the RAT the concerned UE is using.)
  • the Area Scope may be restricted by the slice the concerned UE is using, such that a cell is considered to be part of the Area Scope only if the UE is associated with certain slice(s) when being connected in the cell (and provided that the cell fulfills any other restrictions included in the Area Scope configuration).
  • SST Slice support
  • the Area Scope may be restricted to cells supporting certain slice(s).
  • LAA Licensed Assisted Access
  • NR-U shared/unlicensed spectrum
  • NTN Non-Terrestrial Network
  • Duplex mode Frequency Division Duplex (FDD) or Time Division Duplex (TDD)
  • MDT Minimization of Drive Test
  • one aspect of the present disclosure provides a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting.
  • the method comprises receiving a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration and/or at least one network type associated with the QoE measurement reporting configuration, and applying the QoE measurement reporting configuration.
  • QoE Quality of Experience
  • Another aspect of the present disclosure provides a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting, wherein the wireless device is configured with a Quality of Experience (QoE) measurement reporting configuration, and wherein the QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration and/or at least one network type associated with the QoE measurement reporting configuration.
  • QoE Quality of Experience
  • the method comprises reporting measurements associated with the QoE measurement reporting configuration when connected to a cell that is one of the at least one cell type and/or a network that is one of the at least one network type, or reporting measurements associated with the QoE measurement reporting configuration when connected to a cell that is not one of the at least one cell type and/or network that is not one of the at least one network type.
  • a further aspect of the present disclosure provides a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting.
  • QoE Quality of Experience
  • the method comprises sending a Quality of Experience (QoE) measurement reporting configuration to the wireless device, wherein the QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration and/or at least one network type associated with the QoE measurement reporting configuration.
  • QoE Quality of Experience
  • embodiments may provide one or more of the following technical advantage(s).
  • embodiments of this disclosure may provide enhancements to the QoE measurement configuration to enable a more flexible selection of the Area Scope where QoE measurements are configured.
  • the additional flexibility may enable network operators to realize highly focused QoE measurement campaigns where a high degree of customization is possible in selecting the area of investigation.
  • UE terminal equipment
  • wireless device wireless terminal
  • terminal terminal
  • QoE measurement report QoE report
  • measurement report measurement report
  • measurement configuration QoE measurement
  • service and “application” are used interchangeably.
  • the term “RAN node” used herein may refer in some examples to any of a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB-MT.
  • a “node” or “network node” may be any one of these nodes or may alternatively be another node such as a wireless device/UE or a node in a core network (CN).
  • the term “area scope” is used herein, though this is used interchangeably with a QoE measurement configuration or information included in a QoE measurement configuration.
  • Figure 1 depicts a method 100 in accordance with particular embodiments, for example a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting.
  • the method begins at step 102 with receiving a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration, and continues to step 104 with applying the QoE measurement configuration.
  • QoE Quality of Experience
  • Figure 2 depicts a method 200 in accordance with particular embodiments, for example a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting, wherein the wireless device is configured with a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • the method begins at step 202 with reporting measurements associated with the QoE measurement configuration when connected to a cell that is one of the at least one cell type and/or a network that is one of the at least one network type; or reporting measurements associated with the QoE measurement configuration when connected to a cell that is not one of the at least one cell type and/or network that is not one of the at least one network type.
  • Figure 3 depicts a method 300 in accordance with particular embodiments, for example a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting.
  • the method begins at step 302 with sending a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • Figure 4 illustrates a schematic block diagram of an apparatus 400 in a wireless network (for example, the wireless network shown in Figure 7).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 7).
  • Apparatus 400 is operable to carry out the example method 100 described with reference to Figure 1 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 1 is not necessarily carried out solely by apparatus 400. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving unit 402, applying unit 404, and any other suitable units of apparatus WW00 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 400 includes receiving unit 402 configured to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration, and applying unit 404 configured to apply the QoE measurement configuration.
  • QoE Quality of Experience
  • Figure 5 illustrates a schematic block diagram of an apparatus 500 in a wireless network (for example, the wireless network shown in Figure 7).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 7).
  • Apparatus 500 is operable to carry out the example method 200 described with reference to Figure 2 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 2 is not necessarily carried out solely by apparatus 500. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • apparatus 500 includes reporting unit 502 configured to report measurements associated with the QoE measurement configuration when connected to a cell that is one of the at least one cell type and/or a network that is one of the at least one network type, or report measurements associated with the QoE measurement configuration when connected to a cell that is not one of the at least one cell type and/or network that is not one of the at least one network type.
  • Figure 6 illustrates a schematic block diagram of an apparatus 600 in a wireless network (for example, the wireless network shown in Figure 7).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 7).
  • Apparatus 600 is operable to carry out the example method 300 described with reference to Figure 3 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 3 is not necessarily carried out solely by apparatus 600. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus VWV20 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause sending unit 602, and any other suitable units of apparatus 600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 600 includes sending unit 602 configured to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration and/or at least one network type associated with the QoE measurement configuration.
  • QoE Quality of Experience
  • the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration.
  • the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell that is one of the at least one cell type.
  • the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell that is not one of the at least one cell type (e.g. none of the at least one cell type).
  • the QoE measurement configuration may identify multiple cell types, and may perform and/or report measurements associated with the QoE measurement configuration when connected to a cell that is one of the types, perform and/or report measurements associated with the QoE measurement configuration when connected to a cell that is none of the types, or perform and/or report measurement associated with the QoE measurement configuration when connected to a cell that is one (or more) of the types but not when connected to a cell that is one of the other types.
  • the QoE measurement configuration identifies at least one network type associated with the QoE measurement configuration.
  • the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a network that is one of the at least one network type.
  • the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a network that is not one of the at least one network type (e.g. none of the at least one network type).
  • the QoE measurement configuration may identify multiple network types, and may perform and/or report measurements associated with the QoE measurement configuration when connected to a network that is one of the types, perform and/or report measurements associated with the QoE measurement configuration when connected to a network that is none of the types, or perform and/or report measurement associated with the QoE measurement configuration when connected to a network that is one (or more) of the types but not when connected to a network that is one of the other types.
  • the method comprises performing at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is one of the at least one cell type or a network that is one of the at least one network type.
  • the method comprises reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type.
  • the QoE measurement configuration identifies the at least one application layer QoE metric.
  • the QoE measurement configuration identifies at least two of: (i) one or more cell identifiers, wherein the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell having one of the one or more cell identifiers;
  • one or more tracking area identifiers wherein the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • MBMS Multimedia Broadcast Multicast Services
  • NTN non-terrestrial network
  • (x) a narrowband internet of things (NB-loT) cell
  • the QoE measurement configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • PNI-NPN public network integrated NPN
  • the QoE measurement configuration identifies a speed condition
  • the wireless device reports measurements associated with the QoE measurement configuration when the wireless device satisfies the speed condition.
  • the QoE measurement configuration identifies an area scope that identifies the at least one cell type and/or the at least one network type.
  • the QoE measurement configuration is received from a network node, which may be for example a core network node, a RAN node, a gNB, eNB, en-gNB, ng- eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB MT.
  • a network node which may be for example a core network node, a RAN node, a gNB, eNB, en-gNB, ng- eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB MT.
  • the QoE measurement configuration is received in a RRC message, which may be for example a RRCConnectionReconfiguration message.
  • the method 100 may include performing and/or reporting measurements associated with the QoE measurement reporting configuration when connected to a cell that is one of the at least one cell type and/or a network that is one of the at least one network type, or performing and/or reporting measurements associated with the QoE measurement reporting configuration when connected to a cell that is not one of the at least one cell type and/or network that is not one of the at least one network type.
  • the configuration may identify (i) cell type(s) where the wireless device reports measurements when connected to a cell of one of those type(s); (ii) cell type(s) where the wireless device performs and/or reports measurements when connected to a cell that is not of one of those type(s); (iii) network type(s) where the wireless device performs and/or reports measurements when connected to a network of one of those type(s); and/or (iv) network type(s) where the wireless device reports measurements when connected to a network that is not of one of those type(s).
  • the method 200 comprises performing and/or reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is one of the at least one cell type or a network that is one of the at least one network type. In some examples, the method comprises performing and/or reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type. Additionally or alternatively, for example, the QoE measurement configuration identifies the at least one application layer QoE metric.
  • the QoE measurement configuration identifies at least two of:
  • the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • MBMS Multimedia Broadcast Multicast Services
  • NTN non-terrestrial network
  • (x) a narrowband internet of things (NB-loT) cell
  • the QoE measurement configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • SNPN standalone NPN
  • PNI-NPN public network integrated NPN
  • the QoE measurement configuration identifies a speed condition, and the wireless device reports measurements associated with the QoE measurement configuration when the wireless device satisfies the speed condition (e.g. when the wireless device is moving at or above a speed threshold).
  • the QoE measurement configuration identifies an area scope that identifies the at least one cell type and/or the at least one network type.
  • the measurements are reported to a network node, e.g. a base station or core network node.
  • the network node comprises a core network node, a RAN node, a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU- CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB MT.
  • the QoE measurement configuration identifies at least one cell type associated with the QoE measurement configuration, and wherein: the QoE measurement configuration causes the wireless device to perform and/or report measurements associated with the QoE measurement configuration when connected to a cell that is one of the at least one cell type; or the QoE measurement configuration causes the wireless device to perform and/or report measurements associated with the QoE measurement configuration when connected to a cell that is not one of the at least one cell type.
  • the QoE measurement configuration identifies at least one network type associated with the QoE measurement configuration, and wherein: the QoE measurement configuration causes the wireless device to perform and/or report measurements associated with the QoE measurement configuration when connected to a network that is one of the at least one network type; or the QoE measurement configuration causes the wireless device to perform and/or report measurements associated with the QoE measurement configuration when connected to a network that is not one of the at least one network type.
  • the configuration may identify (i) cell type(s) where the wireless device performs and/or reports measurements when connected to a cell of one of those type(s); (ii) cell type(s) where the wireless device performs and/or reports measurements when connected to a cell that is not of one of those type(s); (iii) network type(s) where the wireless device performs and/or reports measurements when connected to a network of one of those type(s); and/or (iv) network type(s) where the wireless device performs and/or reports measurements when connected to a network that is not of one of those type(s).
  • the method comprises receiving at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is one of the at least one cell type or a network that is one of the at least one network type.
  • the method 300 comprises performing and/or reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type.
  • the QoE measurement configuration may for example identify the at least one application layer QoE metric.
  • the QoE measurement configuration identifies at least two of:
  • one or more tracking area identifiers wherein the wireless device performs and/or reports measurements associated with the QoE measurement configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • a closed subscriber group (CSG) cell (ii) Multimedia Broadcast Multicast Services (MBMS) dedicated cell;
  • CSG closed subscriber group
  • MBMS Multimedia Broadcast Multicast Services
  • NTN non-terrestrial network
  • (x) a narrowband internet of things (NB-loT) cell
  • the QoE measurement configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • PNI-NPN public network integrated NPN
  • the QoE measurement configuration identifies a speed condition and causes the wireless device to perform and/or report measurements associated with the QoE measurement configuration when the wireless device satisfies the speed condition.
  • the QoE measurement configuration identifies an area scope that identifies the at least one cell type and/or the at least one network type.
  • the network node comprises a core network node, a RAN node, a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, IAB- donor DU, lAB-donor-CU, IAB-DU or IAB MT.
  • the QoE measurement configuration is sent to the wireless device in a RRC message, such as for example a RRCConnectionReconfiguration message.
  • the choice of Area scope of QMC is extended to indicate a multi-RAT scenario, e.g. if the Area Scope is received by an eNB, the area scope extends also to NR RAT. In other words, the area scope consists of cells of different RATs.
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an HSDN cell, wherein the filter may be inclusive (such that only HSDN cells are included) or exclusive (such that HSDN cells are excluded).
  • the filter may be inclusive (such that only HSDN cells are included) or exclusive (such that HSDN cells are excluded).
  • o CSG support in the cells ⁇
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is a CSG cell, wherein the filter may be inclusive (such that only CSG cells are included) or exclusive (such that CSG cells are excluded).
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an NPN-only cell that broadcasts one of a certain set of NID(s), wherein the filter may be inclusive (such that only NPN-only cells broadcasting one of a certain set of specific NID(s) are included) or exclusive (such that NPN-only cells broadcasting one of a certain set of specific NID(s) are excluded).-NPN support in the cells
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an NPN-only cell that broadcasts one of a certain set of CAG identity/identities, wherein the filter may be inclusive (such that only NPN-only cells broadcasting one of a certain set of specific CAG identity/identities are included) or exclusive (such that NPN-only cells broadcasting one of a certain set of specific CAG identity/identities are excluded).
  • the filter may be inclusive (such that only NPN-only cells broadcasting one of a certain set of specific CAG identity/identities are included) or exclusive (such that NPN-only cells broadcasting one of a certain set of specific CAG identity/identities are excluded).
  • IAB cells i.e. cells served by IAB node(s)
  • a cell inclusion in the Area Scope is filtered based on whether the cell is served by an IAB node (e.g. a gNB being connected to another gNB via IAB (i.e. via the llu interface)), wherein the filter may be inclusive (such that only cells served by IAB nodes are included) or exclusive (such that cells served by IAB nodes are excluded).
  • An IAB Cell is included in/excluded from the Area Scope if it is served by an IAB node that is located a certain number of hops from the IAB donor (e.g. measurements are taken only in cells served by IAB nodes located 3 or more hops from the IAB donor).
  • An IAB Cell is included in/excluded from the Area Scope if it is served by an IAB node that is located, in the IAB topology, upstream or downstream from a certain IAB node (this “certain” IAB node is e.g. an IAB node that is a bottleneck).
  • An IAB Cell is included in/excluded from the Area Scope if it is served by an IAB node that is single- or multiconnected with the donor (using NR-DC or EN-DC).
  • An IAB cell is included in/excluded from the Area Scope if the traffic for the UEs served by this cell is carried:
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell supports at least one of a certain set of network slice(s) (SST(s)), wherein the filter may be inclusive (such that only cells supporting at least one of a certain set of specific network slice(s) are included) or exclusive (such that cells supporting at least one of a certain set of specific network slice(s) are excluded) .
  • the criterion may logically classify a cell as being part of the Area Scope or not being part of the Area Scope based on the network slice the QoE data collecting UE is using.
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell supports MBMS, wherein the filter may be inclusive (such that only cells supporting MBMS are included) or exclusive (such that cells supporting MBMS are excluded)
  • the UE is configured to log the QoE measurements when the UE receives a service over either multicast or broadcast service.
  • the UE is configured to log the QoE measurements when the cell to which the UE is connected to supports the MBMS service. loT support in the cells
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell supports NB-loT, wherein the filter may be inclusive (such that only cells supporting NB-loT are included) or exclusive (such that cells supporting NB-loT are excluded).
  • LAA sed Assisted Access
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an LAA cell, wherein the filter may be inclusive (such that only LAA cells are included) or exclusive (such that LAA cells are excluded).
  • the UE is configured to perform the QoE measurements logging when at least one of the serving cell for the UE is operating in an unlicensed spectrum (i.e., the UE needs to perform LBT before transmissions).
  • ep RACH support in the cells ⁇
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell supports 2-step Random Access (RA), wherein the filter may be inclusive (such that only cells supporting 2-step RA are included) or exclusive (such that cells supporting 2- step RA are excluded). operating in shared/unlicensed spectrum (NR-ll).
  • RA 2-step Random Access
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an NR-ll cell, wherein the filter may be inclusive (such that only NR-ll cells are included) or exclusive (such that NR-ll cells are excluded).
  • NTN -Terrestrial Network
  • a cell’s inclusion in the Area Scope is filtered based on whether the cell is an NTN cell, wherein the filter may be inclusive (such that only NTN cells are included) or exclusive (such that NTN cells are excluded).
  • the filter criterion may be that a cell is included in the Area Scope if it is a LEO NTN cell or that the cell is excluded from the Area Scope if it is a LEO NTN cell.
  • the filter criterion may also comprise a set of NTN types.
  • the filter criterion may be that a cell is included in the Area Scope if it is a GEO NTN cell or a MEO NTN cell, or that the cell is excluded from the Area Scope if it is a GEO NTN cell or a MEO NTN cell.port for resource coordination and interference mitigation in the cells
  • the inclusion of a cell in the Area Scope is based on whether mechanism(s) for resource coordination and interference mitigation mechanism are activated/supported in the cell (i.e. at the RAN node serving the cell)
  • the said mechanisms may include and are not limited to cross-link interference management, remote interference management, cell-level resource coordination (e.g. spectrum sharing), UE-level resource coordination, as defined in TS 38.300 v16.2.0, TS 38.401 v16.2.0, TS 38.473 V16.2.0, TS 38.423 v16.2.0, TS 36.423 v16.2.0 and TS 38.413 V16.2.0.
  • cell-level resource coordination e.g. spectrum sharing
  • UE-level resource coordination e.g. spectrum sharing
  • the Area Scope is defined using geographical parameters and/or geometrical shape (e.g. polygons or ellipses) parameters, instead of, or as a complement to, cells and areas consisting of cells. Parameters for such area definitions are already specified in various standard specifications (e.g. 3GPP TS 36.331 (e.g. in the Locationinfo IE), 3GPP TS 23.041 and ATIS 0700041 : "WEA 3.0: Device-Based Geo-Fencing”) and can be reused.
  • 3GPP TS 36.331 e.g. in the Locationinfo IE
  • 3GPP TS 23.041 and ATIS 0700041 "WEA 3.0: Device-Based Geo-Fencing
  • the RAN node may determine which UEs are within the geographical Area Scope definition based on location information retrieved from the UEs, e.g. location information the UEs’ obtained from GNSS measurements. Alternatively, and preferably, the gNB leaves to the UEs to determine whether they are within the geographical definition of the Area Scope. This alternative is preferable, since a UE’s position may frequently or continuously change, which the UE has much better possibilities to track than the RAN.
  • the RAN selects UEs in cells which overlap with the geographical definition of the Area Scope (where these UEs also may have to satisfy other criteria related to the Area Scope or other parts of the QMC configuration) and provides the QoE measurement configuration (including the geographical Area Scope definition) to the selected UEs. These selected UEs will then keep track of whether they are inside or outside the geographical Area Scope and perform or refrain from performing QoE data collection accordingly.
  • a scenario could for instance be that the network/operator is interested in QoE data collected by UEs travelling on a certain road or stretch of railroad and then the geographical area could be defined to narrowly follow the road or railroad, so that UE’s located beside the road or railroad, but connected in the cells that cover the road/railroad would be excluded, i.e. they would not collect QoE data.
  • a new type of geographical area definition tailored for roads and railroads. It could consist of some kind of indication of line (e.g. a sequence of points/positions which the UE/application turns into a smooth line, e.g. using well-known algorithms for fitting a smooth line to a set of points) with an associated width indication.
  • An area definition covering a road or railroad could be complemented by a speed condition to exclude QoE data collection by UEs not actually travelling on the road/railroad, e.g. so that the condition for activating QoE data collection is (besides that the concerned application is active and other possible conditions) that the UE is within the geographical area AND is moving at a speed above a threshold.
  • the collected data could be associated with detailed location and speed data when reported to the network.
  • the UE would have to use its GNSS (e.g. GPS) receiver and a consequent option could be that the UE indicates in its capability information that it has GNSS capability (and accepts to use it for this purpose).
  • GNSS e.g. GPS
  • a geographical area definition (rather than a list of cells) would be beneficial could be a mall in which the operator wants to monitor the QoE. Then a geographical definition of the mail’s footprint would be much more accurate than a list of the cells whose coverage areas to some extent overlap with the mall.
  • An additional variant could be to leverage a navigation application in the UE, such as Google Maps or the like, when defining the area.
  • the network could for instance configure the UE to collect QoE data while it is traveling on a certain highway, such as the E4 European highway (optionally combined with a speed condition).
  • the navigation application (such e.g.
  • the Area Scope definition could consist of an indication of a certain road or highway (rather than geographical parameters), optionally complemented by geographical indications of start and end points on the road/highway between which QoE data collection should be performed (i.e. this way certain parts of a road/highway could be pointed out for QoE data collection.
  • This method could possibly be extended to other geographical “artifacts” which has a special representation on maps and in navigation application, e.g. squares/plazas and special buildings, such as railroad stations, sports arenas and malls.
  • the RAN may choose to configure UEs based on their capability to determine its own position, e.g. based on their support for GNSS measurements (and possibly also their (or their users’) acceptance to use the positioning means for QoE measurement purposes).
  • a speed condition could be part of the Area Scope or filter criterion, such that QoE data collection is active only while the UE is moving at a speed exceeding a configured threshold.
  • ⁇ This may be beneficially combined with a geographical definition in the Area Scope, such as the above described area definition tracking a road or railroad, wherein the speed condition would serve to even more accurately ensure that only UEs actually travelling along the road or railroad performs the QoE measurements.
  • the condition of performing QoE data collection could be that the UE is within the geographical area AND is moving at a speed above a threshold.
  • the collected data could be associated with detailed location and speed data when reported to the network.
  • the UE may have to use its GNSS (e.g. GPS) receiver and a consequent option could be that the UE indicates in its capability information that it has GNSS capability (and accepts to use it for this purpose).
  • GNSS e.g. GPS
  • this app could further be utilized to determine the UE’s speed.
  • the speed should exceed a threshold and the movement direction should be in line with a concerned road or railroad (which could also be expressed in geographical terms of geographical terms, such as angle in relation to the north direction).
  • Another way of combining magnitude and direction of speed/velocity in a condition could be that the velocity’s vector component, or vector projection, in a certain direction must exceed a certain threshold in order for QoE data collection to be performed.nectivity mode
  • a condition could be that the UE should only collect QoE data when in one or more of certain connectivity modes:
  • NGEN-DC lex mode ⁇ instead of, or in combination with, an area scope, a condition could be that the UE should only collect QoE data when in certain duplex mode:
  • a condition could be that the UE should only collect QoE data when certain other features are activated in the cell, e.g. that MDT is also configured for the UE in the particular cell. cation of QoE data collection applicability broadcast in each cell
  • the condition for activating QoE data collection could be that the serving cell broadcasts (in the system information) a flag indicating that QoE data collection should be performed in the cell (by UEs configured for QoE data collection/reporting), e.g. setting a system information parameter called “qoe-DataCollection” to “true”.
  • qoe-DataCollection a system information parameter called “qoe-DataCollection” to “true”.
  • the Area Scope could be defined by any combination of at least two of:
  • a QoE measurement configuration (or a measurement reporting configuration) comprising filter criterion/criteria for the UE to evaluate to determine whether and when the UE should activate QoE data collection in the concerned cell.
  • Example of implementation for LTE An example of an implementation of embodiments of this disclosure is provided below for LTE (TS 36.413, which is incorporated herein by reference), where underlined text relates to for example the example implementation: in the tables below, at least some of the nonunderlined text has been removed for conciseness, but may still be present in example implementations.
  • the IE defines configuration information for the QoE Measurement Collection (QMC) function.
  • the IE defines configuration information for the QoE Measurement Collection (QMC) function.
  • One possibility is to reuse as parent IE an Information Element similar to the “UE Application layer measurement configuration” used for LTE (see examples of implementation proposals for S1AP and X2AP).
  • a wireless network such as the example wireless network illustrated in Figure 7.
  • the wireless network of Figure 7 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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
  • 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 may then also 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 multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.
  • network node QQ160 illustrated in the example wireless network of Figure 7 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 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.
  • network node QQ160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 QQ160.
  • Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 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 information obtained by processing circuitry QQ170 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 QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
  • some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computerexecutable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170.
  • 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
  • Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node QQ160 may include additional components beyond those shown in Figure 7 that may be responsible 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.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehiclemounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LOE laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD 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 WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ110 includes antenna QQ111 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.
  • Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114.
  • antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port.
  • Antenna QQ111 , interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna QQ111 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111.
  • WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111 . Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 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 WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ110 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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.
  • Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or nonvolatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
  • Figure 8 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or 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 to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE QQ200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 8 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 8, or only a subset of the components. 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.
  • processing circuitry QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, 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 QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE QQ200.
  • the output device may be 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.
  • UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • the input device may 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, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).
  • the transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201.
  • ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a removable
  • Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or 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 in storage medium QQ221 , which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231 .
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, LITRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 may include 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.
  • communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 9 is a schematic block diagram illustrating a virtualization environment QQ300 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • 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.
  • virtual machine QQ340 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 virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 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.
  • control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
  • a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411 , such as a radio access network, and core network QQ414.
  • Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c.
  • Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c.
  • a second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420.
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 10 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491.
  • base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer QQ510 further comprises software QQ511 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ511 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530.
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 11) served by base station QQ520.
  • Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510.
  • Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 11 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 10, respectively.
  • the inner workings of these entities may be as shown in Figure 11 and independently, the surrounding network topology may be that of Figure 10.
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the flexibility of QoE measurement and/or reporting and thereby provide benefits such as improved network performance, etc.
  • 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 OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 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 QQ511 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • FIG 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11 .
  • the host computer provides user data.
  • substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11 .
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11 .
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11 .
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • QoE Quality of Experience
  • QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration and/or at least one network type associated with the QoE measurement reporting configuration
  • the QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration, and wherein: the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a cell that is one of the at least one cell type; or the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a cell that is not one of the at least one cell type.
  • the QoE measurement reporting configuration identifies at least one network type associated with the QoE measurement reporting configuration, and wherein: the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a network that is one of the at least one network type; or the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a network that is not one of the at least one network type.
  • the method of any of embodiments 1 to 4 comprising reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type.
  • the method of embodiment 4 or 5 wherein the QoE measurement reporting configuration identifies the at least one application layer QoE metric.
  • the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement reporting configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • MBMS Multimedia Broadcast Multicast Services
  • NTN non-terrestrial network
  • NB-loT narrowband internet of things
  • IAB integrated access and backhaul
  • (xviii) a cell supporting resource coordination and interference mitigation.
  • the QoE measurement reporting configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • PNI-NPN public network integrated NPN
  • (v) a network connected to a 5G core (5GC) network.
  • the method of any of embodiments 1 to 10 wherein the QoE measurement reporting configuration identifies an area scope that identifies the at least one cell type and/or the at least one network type.
  • the method of any of embodiments 1 to 11 wherein the QoE measurement reporting configuration is received from a network node.
  • the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB-MT.
  • the QoE measurement reporting configuration is received in a RRC message.
  • the RRC message comprises a RRCConnectionReconfiguration message.
  • the method of embodiment 16 comprising performing at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is one of the at least one cell type or a network that is one of the at least one network type.
  • the method of embodiment 17, comprising reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type.
  • the method of embodiment 17 or 18, wherein the QoE measurement reporting configuration identifies the at least one application layer QoE metric.
  • the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement reporting configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • MBMS Multimedia Broadcast Multicast Services
  • LAA license assisted access
  • NR-ll new radio unlicensed
  • NTN non-terrestrial network
  • (x) a narrowband internet of things (NB-loT) cell
  • (xviii) a cell supporting resource coordination and interference mitigation.
  • the QoE measurement reporting configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • PNI-NPN public network integrated NPN
  • (v) a network connected to a 5G core (5GC) network.
  • the network node comprises a gNB, eNB, en-gNB, ng- eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, IAB- donor-CU, IAB-DU or IAB-MT.
  • a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting comprising:
  • QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration and/or at least one network type associated with the QoE measurement reporting configuration.
  • QoE Quality of Experience
  • the QoE measurement reporting configuration identifies at least one cell type associated with the QoE measurement reporting configuration, and wherein: the QoE measurement reporting configuration causes the wireless device to report measurements associated with the QoE measurement reporting configuration when connected to a cell that is one of the at least one cell type; or the QoE measurement reporting configuration causes the wireless device to report measurements associated with the QoE measurement reporting configuration when connected to a cell that is not one of the at least one cell type.
  • the QoE measurement reporting configuration identifies at least one network type associated with the QoE measurement reporting configuration, and wherein: the QoE measurement reporting configuration causes the wireless device to report measurements associated with the QoE measurement reporting configuration when connected to a network that is one of the at least one network type; or the QoE measurement reporting configuration causes the wireless device to report measurements associated with the QoE measurement reporting configuration when connected to a network that is not one of the at least one network type.
  • the method of any of embodiments 28 to 30, comprising receiving at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is one of the at least one cell type or a network that is one of the at least one network type.
  • the method of any of embodiments 28 to 31 comprising reporting at least one measurement of at least one application layer QoE metric when the wireless device is connected to a cell that is not one of the at least one cell type or a network that is not one of the at least one network type.
  • the method of embodiment 31 or 32, wherein the QoE measurement reporting configuration identifies the at least one application layer QoE metric.
  • the method of any of embodiments 28 to 33, wherein the QoE measurement reporting configuration identifies at least two of:
  • the wireless device reports measurements associated with the QoE measurement reporting configuration when connected to a cell within a tracking area identified by one of the one or more tracking area identifiers.
  • the QoE measurement reporting configuration identifies the at least one cell type, wherein the at least one cell type comprises one or more of:
  • HSDN High Speed Dedicated Network
  • MBMS Multimedia Broadcast Multicast Services
  • NTN non-terrestrial network
  • (x) a narrowband internet of things (NB-loT) cell
  • (xviii) a cell supporting resource coordination and interference mitigation.
  • the QoE measurement reporting configuration identifies the at least one network type, wherein the at least one network type comprises one or more of:
  • NPN non public network
  • PNI-NPN public network integrated NPN
  • (v) a network connected to a 5G core (5GC) network.
  • the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, IAB- node, lAB-donor DU, lAB-donor-CU, IAB-DU or IAB-MT.
  • the QoE measurement reporting configuration is sent to the wireless device in a RRC message.
  • the RRC message comprises a RRCConnectionReconfiguration message.
  • a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a base station for configuring a wireless device for Quality of Experience (QoE) measurement reporting comprising:
  • - power supply circuitry configured to supply power to the base station.
  • 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;
  • 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
  • a communication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • a user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment wherein the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • a communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the host computer receiving user data transmitted to the base station from the LIE, wherein the LIE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising, at the LIE, providing the user data to the base station.
  • the method of the previous 2 embodiments further comprising:
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (LIE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 69.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

Landscapes

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

Abstract

L'invention concerne des procédés et un appareil, et notamment, dans un exemple, un procédé exécuté par un dispositif sans fil. Le procédé comprend la réception d'une configuration de mesure de qualité d'expérience (QoE), la configuration de mesure de QoE identifiant au moins un type de cellule associé à la configuration de mesure de QoE et/ou au moins un type de réseau associé à la configuration de mesure de QoE. Le procédé comprend également l'application de la configuration de mesure de QoE.
PCT/SE2021/050879 2020-10-09 2021-09-14 Configuration de mesure de qualité d'expérience WO2022075903A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063089598P 2020-10-09 2020-10-09
US63/089,598 2020-10-09

Publications (1)

Publication Number Publication Date
WO2022075903A1 true WO2022075903A1 (fr) 2022-04-14

Family

ID=78032477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/050879 WO2022075903A1 (fr) 2020-10-09 2021-09-14 Configuration de mesure de qualité d'expérience

Country Status (1)

Country Link
WO (1) WO2022075903A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023206334A1 (fr) * 2022-04-29 2023-11-02 Qualcomm Incorporated Techniques pour faciliter des améliorations de qualité d'expérience pour des scénarios de grande mobilité
WO2023225932A1 (fr) * 2022-05-26 2023-11-30 Lenovo (Beijing) Limited Procédé et appareil de prise en charge de collecte de mesure de qualité d'expérience (qoe)
WO2024012296A1 (fr) * 2022-07-15 2024-01-18 华为技术有限公司 Procédé de configuration de mesure, dispositif de réseau d'accès et dispositif terminal
WO2024026808A1 (fr) * 2022-08-05 2024-02-08 Qualcomm Incorporated Configuration de qualité d'expérience pour un service de multidiffusion ou de diffusion
WO2024030059A1 (fr) * 2022-08-04 2024-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Mesure de qualité d'expérience
WO2024027691A1 (fr) * 2022-08-03 2024-02-08 大唐移动通信设备有限公司 Procédé et appareil de mesure de qualité d'expérience de mbs
WO2024061161A1 (fr) * 2022-09-21 2024-03-28 华为技术有限公司 Procédé et appareil de mesure, et dispositif associé
WO2024168733A1 (fr) * 2023-02-16 2024-08-22 Nokia Shanghai Bell Co., Ltd. Dispositifs, procédés, appareils et support de stockage lisible par ordinateur pour des communications

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3583804A1 (fr) * 2017-02-14 2019-12-25 Telefonaktiebolaget LM Ericsson (PUBL) Procédé et noeuds de réseau pour gérer une collecte de mesure de qoe durant un réadressage ou un transfert

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3583804A1 (fr) * 2017-02-14 2019-12-25 Telefonaktiebolaget LM Ericsson (PUBL) Procédé et noeuds de réseau pour gérer une collecte de mesure de qoe durant un réadressage ou un transfert

Non-Patent Citations (22)

* Cited by examiner, † Cited by third party
Title
3GPP TR 38.821
3GPP TS 23.041
3GPP TS 23.246
3GPP TS 23.501
3GPP TS 25.331
3GPP TS 28.405
3GPP TS 36.300
3GPP TS 36.304
3GPP TS 36.331
3GPP TS 36.413
3GPP TS 36.423
3GPP TS 38.300
3GPP TS 38.304
3GPP TS 38.331
3GPP TS 38.401
3GPP TS 38.413
3GPP TS 38.423
ERICSSON: "NR QoE Measurement Triggering, Configuration, Collection and Reporting", vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), XP051911074, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2007600.zip R2-2007600 - NR QoE Measurement Triggering, Configuration, Collection and Reporting.docx> [retrieved on 20200806] *
ERICSSON: "Outstanding problem with QoE configuration", vol. RAN WG2, no. Reno, US; 20171127 - 20171201, 16 November 2017 (2017-11-16), XP051371015, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F100/Docs/> [retrieved on 20171116] *
ERICSSON: "Solution enhancement for QoE Measurements", vol. RAN WG2, no. Prague, Czech Republic; 20171009 - 20171013, 5 October 2017 (2017-10-05), XP051355884, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_99bis/Docs/> [retrieved on 20171005] *
HUAWEI ET AL: "Discussion on QoE measurement collection for RDC", vol. RAN WG2, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), XP051603206, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F105/Docs/R2%2D1901857%2Ezip> [retrieved on 20190215] *
POTEVIO: "Intra-frequency small cell detection in HetNet", 3GPP DRAFT; R2-122362_INTRA-FREQUENCY SMALL CELL DETECTION IN HETNET, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20120521 - 20120525, 14 May 2012 (2012-05-14), XP050606928 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023206334A1 (fr) * 2022-04-29 2023-11-02 Qualcomm Incorporated Techniques pour faciliter des améliorations de qualité d'expérience pour des scénarios de grande mobilité
WO2023225932A1 (fr) * 2022-05-26 2023-11-30 Lenovo (Beijing) Limited Procédé et appareil de prise en charge de collecte de mesure de qualité d'expérience (qoe)
WO2024012296A1 (fr) * 2022-07-15 2024-01-18 华为技术有限公司 Procédé de configuration de mesure, dispositif de réseau d'accès et dispositif terminal
WO2024027691A1 (fr) * 2022-08-03 2024-02-08 大唐移动通信设备有限公司 Procédé et appareil de mesure de qualité d'expérience de mbs
WO2024030059A1 (fr) * 2022-08-04 2024-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Mesure de qualité d'expérience
WO2024026808A1 (fr) * 2022-08-05 2024-02-08 Qualcomm Incorporated Configuration de qualité d'expérience pour un service de multidiffusion ou de diffusion
WO2024061161A1 (fr) * 2022-09-21 2024-03-28 华为技术有限公司 Procédé et appareil de mesure, et dispositif associé
WO2024168733A1 (fr) * 2023-02-16 2024-08-22 Nokia Shanghai Bell Co., Ltd. Dispositifs, procédés, appareils et support de stockage lisible par ordinateur pour des communications

Similar Documents

Publication Publication Date Title
US11641603B2 (en) Report NSA/SA NR indicator
WO2022075903A1 (fr) Configuration de mesure de qualité d&#39;expérience
AU2018370453B2 (en) Notification control over RAN interfaces
US20220039082A1 (en) Sidelink Resource Allocation for Enhanced Mobility
US20220361069A1 (en) Sidelink Configuration
CN111801981B (zh) 用于高效早期数据的传感器数据批处理
US20230362725A1 (en) Connection Configuration Change
EP3662599B1 (fr) Évitement de multiples retransmissions de signalisation transportées par un transport nas 5g
EP3994901A1 (fr) Déclencheur de communication de groupe v2x et prise de décision
US12022554B2 (en) N2 notification procedure improvement
WO2021044375A1 (fr) Signalisation de capacité à connectivité multiple pour nœuds multiservices
US20230213933A1 (en) Tele-operated driving event prediction, adaption and trigger
US20240155470A1 (en) Duplicated SIB Handling in Sidelink Relay
WO2020218959A1 (fr) Fourniture d&#39;informations de faisceaux
US20240056872A1 (en) Methods, Apparatus and Machine-Readable Media Related to Storage of QoE Data
US20230072998A1 (en) Measurement Reporting Configuration
WO2022154730A1 (fr) Zones à capacité limitée pour dispositifs sans fil
EP4229904A1 (fr) Gestion de configurations de groupes de cellules maîtresses et secondaires
WO2021066728A1 (fr) Configuration de mesure de mode veille/inactif

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21783599

Country of ref document: EP

Kind code of ref document: A1