Quality of experience measurement collection over sidelink communications

Abstract

Methods, systems, and devices are described for wireless communication that provide for a user equipment (UE) to collect and report quality of experience (QoE) metrics for sidelink connections between the UE and one or more other UEs. The network entity may configure one or more UEs to provide QoE for sidelink communications, and one or more of the sidelink UEs may collect and report QoE measurements for the sidelink connection. One or more of the UEs may receive the QoE configuration and measure various associated parameters of the sidelink connection with one or more other UEs, and send a QoE measurement report to the network entity. The relay UE may also send the QoE configuration to a remote UE, receive a QoE measurement report from the remote UE, and send the QoE measurement report to a network.

Description

Technical Field

[0001] The following pertains to wireless communication, including the collection of experience quality measurements over sidelink communication. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0003] In some wireless communication systems, a UE can communicate with one or more network entities via one or more network links (e.g., via a Uu interface). In some systems, one or more UEs can also communicate directly with one or more other UEs via one or more sidelinks (e.g., via a PC5 interface) or peer-to-peer connections. Efficient techniques for monitoring sidelink communication can help enhance the efficiency and reliability of wireless communication. Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting the collection of Quality of Experience (QoE) measurements over sidelink communications. For example, the described technology provides the collection and reporting of QoE measurements by a User Equipment (UE) for a sidelink connection between the UE and one or more other UEs. In some aspects, a network entity may configure one or more UEs to provide QoE for a sidelink (e.g., via a PC5 interface), and one or more of the sidelink UEs may collect and report QoE measurements for the sidelink connection. In some aspects, a relay UE may provide a relay connection to a remote UE, the relay UE may receive a QoE configuration and measure various associated parameters of the sidelink connection with the remote UE, and the relay UE may send a QoE measurement report to a network entity. In some aspects, the relay UE may also send a QoE configuration to a remote UE, receive a QoE measurement report from the remote UE, and send a QoE measurement report to the network. The techniques discussed herein can be used for service-based QoE (e.g., where a network entity provides a remote UE ID with QoE configuration) or management-based QoE (e.g., where a network entity instructs that the configuration applies to all capable remote UEs connected to the relay UE) configuration and reporting.

[0005] A method for wireless communication by a first UE is described. The method may include: receiving signaling indicating an experience quality measurement configuration for a sidelink connection with a second UE; obtaining an experience quality measurement set for the sidelink connection with the second UE based on the experience quality measurement configuration; and transmitting an experience quality measurement report for the sidelink connection with the second UE based on the experience quality measurement set.

[0006] A first UE for wireless communication is described. The first UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the first UE to: receive signaling indicating a quality of experience (QAs) measurement configuration for a sidelink connection with a second UE; obtain a set of QAs for the sidelink connection with the second UE based on the QAs configuration; and transmit a QAs report for the sidelink connection with the second UE based on the QAs set.

[0007] Another first UE for wireless communication is described. The first UE may include: components for receiving signaling indicating an experience quality measurement configuration for a sidelink connection with a second UE; components for obtaining an experience quality measurement set for the sidelink connection with the second UE based on the experience quality measurement configuration; and components for transmitting an experience quality measurement report for the sidelink connection with the second UE based on the experience quality measurement set.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive at a first UE signaling an experience quality measurement configuration for a sidelink connection with a second UE; obtain an experience quality measurement set for the sidelink connection with the second UE based on the experience quality measurement configuration; and transmit an experience quality measurement report for the sidelink connection with the second UE based on the experience quality measurement set.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the quality of experience (QEE) measurement configuration is received from a network entity using an access link connection, and the QEE measurement report for a sidelink connection with a second UE is sent to the network entity using the access link connection. Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving signaling indicating that the QEE measurement configuration is applied to direct communication between a first UE and a second UE using a sidelink connection.

[0010] The methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending experience quality measurement configurations to a second UE using a sidelink connection. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining a set of experience quality measurements may include operations, features, components, or instructions for receiving a set of experience quality measurements, such as those measured at the second UE, from the second UE using a sidelink connection.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining a set of experience quality measurements may include operations, features, components, or instructions for receiving, as measured at the application layer of the first UE, a set of experience quality measurements for a sidelink connection with the second UE. Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for providing the access layer of the first UE with a sidelink connection interface indication and a set of experience quality measurements for transmission in an experience quality measurement report.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the receiving may include operations, features, components, or instructions for receiving from a network entity a set of multiple radio access network visible experience quality parameters associated with an experience quality measurement report, and an indication of the set of multiple radio access network visible experience quality parameters associated with a sidelink connection with a second UE. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, obtaining the experience quality measurement set may include operations, features, components, or instructions for obtaining auxiliary information from a relay UE and a set of multiple radio access network visible experience quality measurements.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, auxiliary information includes one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application Internet Protocol address, or any combination thereof. Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: determining one or more quality of experience parameters based on a quality of experience measurement configuration, the one or more quality of experience parameters including one or more of a container identifier, a type of service indication, a radio resource control identifier, or a UE identifier of a second UE; and transmitting one or more quality of experience parameters to the second UE.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the quality of experience measurement configuration may include an indication of whether a first UE should forward the configuration to one or more remote UEs, and these methods, UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for sending the quality of experience measurement configuration to at least a second UE in response to determining that a second UE has the capability to provide a quality of experience measurement report.

[0015] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, obtaining a set of experience quality measurements includes using a sidelink connection to receive an experience quality report container from a radio resource control message from a second UE; and sending the experience quality measurement report includes using an access link connection to send the experience quality report container to a network entity. In some examples of the methods, UEs, and non-transitory computer-readable media described herein, obtaining a set of experience quality measurements includes using a sidelink connection to receive a radio access network visible experience quality report from a second UE; and sending the experience quality measurement report includes deriving auxiliary information associated with the experience quality report and the identifier of the second UE, and using an access link connection to send the experience quality report and the auxiliary information to a network entity, wherein the auxiliary information includes one or more of a resource allocation mode associated with the sidelink connection, a sidelink data radio bearer configuration, or a sidelink connection stream ID.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Quality of Experience (QISA) report provides one or more of the following: an indication of a set of QISA measurements associated with direct communication with a second UE using a sidelink connection; an indication from the first UE to the second UE of a Layer 2 UE-to-network relay; an indication from the first UE to the second UE of a Layer 3 UE-to-network relay; an indication of a container associated with the QISA measurement set; or an indication in a radio resource control signaling message that the QISA report includes a set of QISA measurements visible to the radio access network.

[0017] A method for wireless communication by a network entity is described. The method may include: sending signaling to a first UE indicating an experience quality measurement configuration for a sidelink connection between the first UE and a second UE, wherein the experience quality measurement configuration indicates a set of experience quality measurements to be reported for the sidelink connection between the first UE and the second UE; and receiving from the first UE an experience quality measurement report for the sidelink connection between the first UE and the second UE, including the experience quality measurement set.

[0018] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute the code so that the network entity: sends signaling to a first UE instructing an experience quality measurement configuration for a sidelink connection between the first UE and a second UE, wherein the experience quality measurement configuration indicates a set of experience quality measurements to be reported for the sidelink connection between the first UE and the second UE; and receives from the first UE an experience quality measurement report for the sidelink connection between the first UE and the second UE, including the set of experience quality measurements.

[0019] Another network entity for wireless communication is described. This network entity may include: components for sending signaling to a first UE instructing experience quality measurement configurations for a sidelink connection between the first UE and a second UE, wherein the experience quality measurement configurations indicate a set of experience quality measurements to be reported for the sidelink connection between the first UE and the second UE; and components for receiving from the first UE an experience quality measurement report for the sidelink connection between the first UE and the second UE, including the set of experience quality measurements.

[0020] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to send signaling to a first UE instructing a configuration for experience quality measurements of a sidelink connection between the first UE and a second UE, wherein the experience quality measurement configuration indicates a set of experience quality measurements to be reported for the sidelink connection between the first UE and the second UE; and to receive from the first UE an experience quality measurement report for the sidelink connection between the first UE and the second UE, including the set of experience quality measurements.

[0021] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the quality of experience (QEE) measurement configuration is transmitted to a first UE using an access link connection, and the QEE measurement report for a sidelink connection between the first UE and a second UE is received from the first UE using the access link connection. Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting signaling indicating that the QEE measurement configuration is for direct communication between the first UE and the second UE using a sidelink connection.

[0022] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the quality of experience (QISA) measurement configuration indicates that a first UE will use a sidelink connection to send the QISA measurement configuration to a second UE. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the QISA measurement set is measured at the application layer at either the first or second UE for the sidelink connection between the first and second UE. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the QISA measurement report includes an indication of the QISA measurement set associated with the second UE.

[0023] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the quality of experience (QEE) measurement configuration may include: sending to a first UE a set of multiple radio access network (RAN) visible QEE parameters associated with an QEE measurement report, and an indication that this set of RRA visible QEE parameters is associated with a sidelink connection to a second UE. In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the QEE measurement report includes ancillary information and a set of multiple RRA visible QEE measurements for the first UE, wherein the ancillary information includes one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application Internet Protocol (IP) address, or any combination thereof. In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the QEE measurement configuration includes an indication to the first UE whether to forward the configuration to one or more remote UEs.

[0024] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Quality of Experience (QISA) report provides one or more of the following: an indication of a set of QISA measurements associated with direct communication between a first UE and a second UE using a sidelink connection; an indication from the first UE to the second UE of a Layer 2 UE to a network relay; an indication from the first UE to the second UE of a Layer 3 UE to a network relay; an indication of a container associated with the QISA measurement set; or an indication in a radio resource control signaling message that the QISA report includes a set of QISA measurements visible to the radio access network. Attached Figure Description

[0025] Figure 1 An example of a wireless communication system for collecting quality of experience (QoE) measurements on a support sidelink communication in accordance with one or more aspects of this disclosure is shown.

[0026] Figure 2 An example of a portion of a wireless communication system with sidelink communication is shown, which supports QoE measurement collection on sidelink communication according to one or more aspects of this disclosure.

[0027] Figures 3 to 7 An example of a process flow for collecting QoE measurements over a support sidelink communication according to one or more aspects of this disclosure is shown.

[0028] Figure 8 and Figure 9 A block diagram of an apparatus for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown.

[0029] Figure 10 A block diagram of a communication manager for collecting QoE measurements on a supporting sidelink communication according to one or more aspects of this disclosure is shown.

[0030] Figure 11 A diagram of a system including a device supporting QoE measurement collection over sidelink communication, according to one or more aspects of this disclosure, is shown.

[0031] Figure 12 and Figure 13 A block diagram of an apparatus for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown.

[0032] Figure 14 A block diagram of a communication manager for collecting QoE measurements on a supporting sidelink communication according to one or more aspects of this disclosure is shown.

[0033] Figure 15 A diagram of a system including a device supporting QoE measurement collection over sidelink communication, according to one or more aspects of this disclosure, is shown.

[0034] Figures 16 to 23 A flowchart illustrating a method for collecting QoE measurements over a support-sidelink communication according to one or more aspects of this disclosure is shown. Detailed Implementation

[0035] In some examples of wireless communication, a wireless device (e.g., a user equipment (UE)) may communicate with a network node (which may also be referred to herein as a network entity) via a direct link or access link (e.g., via a Uu interface). A UE may also communicate with a second UE via a side link (e.g., via a PC5 interface). The second UE may have a direct link to the network node, or may not have a direct link to the network node, in which case communication with the network may be relayed via one or more other UEs. In some cases, communication connected via a side link may provide content to the user, and the delivery of such content may have associated quality metrics. For example, in some networks, Quality of Experience (QoE) information collection may be used to provide detailed information about multiple UEs at the session level. QoE of end-user services may provide operators with QoE information that may not be available from physical layer performance measurements in the network (e.g., from channel state information (CSI)-based measurement reports). QoE information may be collected at the application layer of the UE and used at the network for analysis, Key Parameter Indicator (KPI) calculation, or both (e.g., to ensure that extended reality (XR) type applications running at the UE meet performance targets). Traditional QoE metrics can be provided for connections using access links (e.g., Uu interfaces), but currently there is no mechanism for providing this information for sidelink connections where two or more UEs communicate directly with each other. It may be desirable to maintain QoE targets for sidelink connections to ensure applications meet performance objectives, and therefore, technologies for QoE configuration and reporting of sidelink connections are desired.

[0036] Various techniques are provided for collecting QoE measurements for sidelink communication. In some aspects, a network entity may configure a UE to provide QoE for a sidelink connection (e.g., a PC5 connection) and enable the sidelink UE to collect and report QoE measurements for that connection. In cases where the UE can provide a relay connection to a remote UE, the relay UE may receive a QoE configuration and measure various parameters associated with the sidelink connection to the remote UE, and may send a QoE measurement report to the network. The relay UE may also send the QoE configuration to the remote UE, receive the QoE measurement report from the remote UE, and send the QoE measurement report to the network. The QoE measurement report may include one or more indications associated with the sidelink connection and the associated UE, such as the sidelink bearer ID, PC5 flow ID (PFI), the application ID of the associated application at the UE, the IP address of the application at the UE, or any combination thereof. In some aspects, the described process can be used for service-based QoE (e.g., where a network entity provides a remote UE ID with QoE configuration) or management-based QoE (e.g., where a network entity indicates that the configuration applies to all capable remote UEs connected to a relay UE) configuration and reporting. QoE measurement reports may include container-based reports (e.g., where a remote UE has an end-to-end connection to the network, and the reporting container is forwarded by the relay UE without decoding its contents) or RAN-visible QoE (RVQoE) reports (e.g., where the reported parameters are visible to both the relay UE and the serving network entity).

[0037] The techniques discussed in this article can provide end users with enhanced Quality of Service (QoE) reports, allowing the network to ensure QoE objectives for maintaining sidelink connectivity. In some cases, efficient signaling techniques can allow the UE to provide QoE reports to network entities for analysis and link maintenance, which can enhance the end-user experience.

[0038] The various aspects of this disclosure are first described in the context of a wireless communication system. Further illustrations, and references, are made to apparatus diagrams, process flows, system diagrams, and flowcharts relating to QoE measurement collection over sidelink communication to further describe the various aspects of this disclosure.

[0039] Figure 1An example of a wireless communication system 100 supporting QoE measurement collection over sidelink communication according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0040] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0041] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices such as Figure 1 The other UE 115 or network entity 105 shown communicates.

[0042] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0043] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0044] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0045] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0046] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0047] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0048] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support QoE measurement collection over sidelink communications as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0049] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0050] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0051] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0052] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0053] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0054] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0055] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0056] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0057] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0058] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0059] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0060] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0061] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0062] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0063] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0064] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0065] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0066] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0067] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0068] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0069] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0070] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0071] Depending on various aspects, two or more UEs 115 may have sidelink connections using D2D communication link 135, and may support the collection and reporting of QoE metrics for the sidelink connections. In some aspects, network entity 115 may configure one or more UEs 115 to provide QoE for the sidelink (e.g., via a PC5 interface), and one or more of the sidelink UEs 115 may collect and report QoE measurements for the sidelink connections. Techniques as discussed herein may be used for service-based QoE (e.g., where network entity 115 provides a remote UE ID with QoE configuration) or management-based QoE (e.g., where network entity 115 instructs configuration applicable to all capable remote UEs 115 connected to the relay UE) configuration and reporting.

[0072] Figure 2 An example of a wireless communication system 200 supporting QoE measurement collection over sidelink communication according to one or more aspects of this disclosure is shown. The wireless communication system 200 can implement, as... Figure 1 The aspects of the wireless communication system 100 described herein may be implemented by or by aspects of the wireless communication system. For example, the wireless communication system 200 may include network entity 105-a, first UE 115-a and second UE 115-b, which may be as described in reference Figure 1 Examples of network entities 105 and UE 115 are described. In some examples, the wireless communication system 200 may support a variety of radio access technologies, including 4G systems (such as LTE systems, LTE-A systems, or LTE-A Pro systems), 5G systems (which may be referred to as NR systems), 6G systems, or other systems. The wireless communication system 200 may support QoE measurement and reporting, and in some examples, may facilitate wireless communication for maintaining QoE targets of services provided via sidelink connections.

[0073] exist Figure 2 In the example, the first UE 115-a and network entity 105-a can communicate via at least a first link 205, which can be an access link provided via a Uu interface. Figure 2In this example, there is no access link between the second UE 115-b and network entity 105-a. However, in other examples, multiple different UEs 115 may have both access links and sidelink connections. In this example, the first UE 115-a and the second UE 115-b may also communicate via sidelink connection 210, which may be a D2D connection provided via a PC5 interface. In some cases, network entity 105-a may transmit configuration information related to QoE measurement collection and reporting to the first UE 115-a and the second UE 115-b. For example, network entity 105-a may provide QoE measurement configuration 215 to the first UE 115-a, and the first UE 115-a may provide a corresponding QoE measurement report 220 to network entity 105-a.

[0074] As discussed herein, in some respects, network entity 105-a may instruct the collection of QoE measurements. In some cases, the QoE management component (QMC) at the core network may activate QoE measurements and reporting, for example, by using a signaling-based QoE activation procedure. In this procedure, the Operations, Administration, and Maintenance (OAM) entity at the core network may initiate QoE measurement activation for a specific UE 115 via the core network and further to network entity 105-a (e.g., gNB). In other cases, a management-based QoE activation procedure may be used, in which the OAM transmits one or more QoE measurement configurations to network entity 105-a. During any activation procedure, network entity 105-a may receive one or more QoE measurement configurations from the OAM or the core network, wherein each QoE configuration may include, for example, a QMC configuration container (e.g., an XML file), a QoE reference, a type of service, an IP address (e.g., an MCE IP address), a region range, a slice range, minimized drive test (MDT) alignment information, available RAN-visible QoE (RVQoE) metrics, or any combination thereof. For example, network entity 105-a may provide QoE measurement configuration 215 via RRC signaling (e.g., in an RRCReconfiguration message), and the configuration information may include a QMC configuration container (e.g., an XML file), the UE's identifier (e.g., determined by RRC parameters), and other relevant information. measConfigAppLayerID The provided RRC ID), the service type used for QoE reporting, or any combination thereof. In some cases, the UE identifier (e.g., measConfigAppLayerID The mapping between the network entity and the QoE reference is maintained in network entity 105-a.

[0075] Based on QoE measurement configuration 215, the first UE 115-a can provide one or more QoE measurement reports 220. In some cases, QoE measurements can be disabled or released by the network. In some cases, OAM can transmit a trigger to disable the QoE measurement collection job list. Disabling QoE measurement collection can be achieved by providing a list with QoE references, and network entity 105-a can release one or more application layer measurement configurations at any time via RRC signaling (e.g., in an RRCReconfiguration message). Additionally, in some cases, if the first UE 115-a enters an idle state, it can release all QoE measurement configurations. Upon receiving a release command, the RRC layer 245 at the first UE 115-a (or at any other UE 115 that receives the release command) can inform one or more upper layers (e.g., application layer 235 or NAS layer 240) to release the QoE measurement configurations.

[0076] QoE measurement report 220 may include various QoE metrics collected according to QoE measurement configuration 215. QoE measurement collection may be handled by application layer 235, which may provide a QoE report container to RRC layer 245. In some cases, the application layer 235 measurement report may be encapsulated in a transparent container for use via RRC signaling (e.g., on a signaling radio bearer (SRB) such as SRB4). MeasurementReportAppLayer (Sent in RRC message). UE ID (e.g., measConfigAppLayerId This can be used to identify an application layer measurement configuration and report between network entity 105-a and the first UE 115-a. The application layer measurement report can be forwarded by network entity 105-a to the OAM along with the QoE reference. In some cases, RRC signaling can be enabled by network entity 105-a (e.g., MeasurementReportAppLayer The message segmentation allows for the sending of application layer measurement reports exceeding the maximum size (e.g., the maximum PDCP SDU size), and the established RRC segmentation mechanism can be applied.

[0077] QoE measurement report 220 can indicate QMC, where a unique identifier exists for each QMC. In the application layer 235 or MCE at the OAM server, a QoE reference can be used to identify each QMC job, where the QoE reference can be globally unique (e.g., composed of MCC+MNC+QMC ID), and the QoE reference is included in the application layer configuration container and reporting container. In the RRC layer 245, the UE ID (e.g., ...) is used. measConfigAppLayerID ) can be used to identify a QoE configuration, where the UE ID (e.g., measConfigAppLayerIDThe UE ID can be assigned by network entity 105-a, which has a length of 4 bits, and for each UE 115, there is a one-to-one mapping between the UE ID and the QoE reference, and this mapping is maintained in the network entity. The RRC layer 245 can assign the UE ID (e.g., ...) measConfigAppLayerID The UE ID is forwarded to the application layer 235 along with the QoE configuration container, and the application layer 235 may deliver the UE ID along with the QoE report container, while the RRC layer 245 does not maintain the UE ID (e.g., measConfigAppLayerID The mapping between the UE ID and the QoE reference. Network entity 105-a can determine the MCE address based on the received UE ID included in the RRC report message and forward the report accordingly.

[0078] In some aspects, network entity 105-a may obtain one or more RVQoE measurements. In some cases, RVQoE measurements may be configured by network entity 105-a, wherein a subset of QoE metrics is reported from the first UE 115-a (or any other UE) in a form readable by network entity 105-a (e.g., an explicit information element (IE) readable by network entity 105-a). In some cases, a list of available RVQoE metrics (e.g., a subset of configured general QoE metrics) may be received by network entity 105-a from the OAM or core network. For example, for some streaming or virtual reality services, RVQoE metrics may include buffer levels and playback latency for media initiation. Where network entity 105-a is part of a split architecture, the central unit (CU) may generate the RVQoE configuration. In some aspects, RVQoE and general QoE (e.g., RAN-transparent container-based QoE) may be configured together or separately. In cases where RVQoE is configured separately, it can be configured after the legacy QoE is configured, and network entity 105-a can release the list of RVQoE configurations without releasing the corresponding regular QoE configurations. If a regular QoE configuration is released, the corresponding RVQoE configuration is also released. As indicated, an RVQoE configuration may include at least one or more RAN-visible QoE metrics to be reported, service type, and RRC identifier (e.g., measConfigAppLayerIDUpon receiving the RVQoE measurement configuration, the UE RRC layer 245 can forward the configuration to the application layer 235 to indicate the service type and RRC identifier. In some cases, multiple simultaneous RVQoE measurements can be configured at one or more UEs 115. When RVQoE is configured, the QoE measurement report 220 can have RVQoE measurements with a reporting periodicity different from that of regular QoE. If the reporting periodicity is not defined in the RVQoE configuration, the RVQoE report can be transmitted along with the regular QoE report. The UE 115 can also report the PDU session ID corresponding to the service undergoing the QoE measurement along with the RVQoE measurement results.

[0079] As discussed herein, conventional systems stipulate that QoE measurements are collected only by applications that transmit via access links (e.g., via Uu paths). For applications that transmit via sidelink connection 210 between the first UE 115-a and the second UE 115-b, no QoE reporting mechanism is provided, and therefore, it may be impossible to adjust conventional services provided via sidelinks (such as via sidelink connection 210) to improve user experience based on QoE information. Various aspects discussed herein specify that sidelink QoE configuration 225 and sidelink QoE reports 230 can be exchanged via sidelink connection 210. Additionally, information from the sidelink QoE report 230 may be provided to network entity 105-a, such as in a QoE measurement report 220. In some aspects, QoE measurements and reports can be configured for sidelink communications (e.g., PC5 direct communication) to enable QoE measurement collection for sidelink communications. In another aspect, QoE measurement and reporting can be configured for Layer 3 (L3) UE-to-network (U2N) relay operations to enable QoE measurement collection for Layer 3-based U2N relay sidelink communications. In yet another aspect, QoE measurement and reporting can be configured for L2-based U2N relay sidelink communications to enable QoE measurement collection for Layer 2-based U2N relay sidelink communications. Figures 3 to 7 Various exemplary techniques for QoE measurement configuration and reporting for sidelink communication are described.

[0080] Figure 3 An example of a process flow 300 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. In some examples, process flow 300 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the UE and network entities, or those implemented by them. For example, process flow 300 may be implemented by OAM / core network (CN) 305, network entity 105-b, first UE 115-c and second UE 115-d, which may be as referenced. Figure 1and Figure 2 Examples of corresponding devices described. Process flow 300 can be implemented by OAM / CN 305, network entity 105-b, and UE 115 to exchange signaling to facilitate reliable communication that meets the QoE objectives of one or more services provided via sidelink communication. In the following description of process flow 300, operations between OAM / CN 305, network entity 105-b, first UE 115-c, and second UE 115-d may be sent in a different order than the example order shown, or operations performed by OAM / CN 305, network entity 105-b, first UE 115-c, and second UE 115-d may be performed in a different order or at different times. Some operations may also be omitted from process flow 300, and other operations may be added to process flow 300.

[0081] At 310, OAM / CN 305 can provide network entity 105-b with QoE configurations for PC5 links. For example, the Measurement Collection Entity (MCE) can indicate one or more configurations for container-based QoE and can indicate to network entity 105-b whether each QoE configuration is applied to sidelink communication (e.g., PC5 direct communication).

[0082] At point 315, network entity 105-b may send QoE configuration to first UE 115-c. The QoE configuration may be sent via RRC signaling through the access link (e.g., a Uu link) with first UE 115-c. In some cases, network entity 105-b may indicate to first UE 115-c whether each QoE configuration applies to sidelink communication. In some cases, first UE 115-c may collect and report QoE measurements based on its own measurements of the sidelink connection with second UE 115-d, and may not need to provide QoE configuration to second UE 115-d. In other cases, first UE 115-c may provide QoE configuration to second UE 115-d.

[0083] At point 320, where QoE configuration is provided to the second UE 115-d, the first UE 115-c may forward the QoE configuration to the second UE 115-d. The QoE configuration may be provided, for example, via PC5 RRC signaling for the sidelink connection between the first UE 115-c and the second UE 115-d.

[0084] At locations 325-a and 325-b, one or both of the first UE 115-c and the second UE 115-d may collect QoE measurements. For example, the receiving UE application layer may retrieve interface information (e.g., PC5 interface information) from the NAS layer and collect QoE measurements for the interface (e.g., the PC5 interface). The receiving UE application layer may include the interface information (e.g., PC5 interface information) in a QoE report container and deliver it to the receiving UE access layer (AS) layer.

[0085] At point 330, where the second UE 115-d reports QoE, the second UE 115-d can use a sidelink RRC message (e.g., a PC5 RRC message) to forward the QoE report container to the first UE 115-c (e.g., the sending UE). At point 335, the first UE 115-c can forward the QoE report container to network entity 105-b. Where a QoE report container is received from the second UE 115-d, the first UE 115-c can forward the received QoE report container. Where the first UE 115-c collects its own QoE measurements, the first UE 115-c can forward its own QoE report container. QoE reports can be sent, for example, via the Uu interface in one or more RRC messages.

[0086] At 340, network entity 105-b can forward QoE reports to OAM / CN 305. In some cases, MCE post-processing can be performed based on the reports, where the MCE can determine the QoE measurements collected for a sidelink interface (e.g., the PC5 interface) and can adjust one or more parameters to enhance or optimize the sidelink configuration (e.g., modify transmit resource allocation or transmit bearer configuration, etc.).

[0087] Figure 4 An example of a process flow 400 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. In some examples, process flow 400 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the UE and network entities, or those implemented by them. For example, process flow 400 may be implemented by MCE 405, network entity 105-c, first UE 115-e, and second UE 115-f, which may be as referenced. Figure 1 and Figure 2Examples of corresponding devices described. Process flow 400 can be implemented by MCE 405, network entity 105-c, and UE 115 to exchange signaling to facilitate reliable communication to meet the QoE objectives of one or more services provided via sidelink communication. In the following description of process flow 400, operations between MCE 405, network entity 105-c, first UE 115-e, and second UE 115-f may be sent in a different order than the example order shown, or operations performed by MCE 405, network entity 105-c, first UE 115-e, and second UE 115-f may be performed in a different order or at different times. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0088] At 410, MCE 405 may provide QoE assistance information to network entity 105-c. For example, the MCE may indicate one or more configurations for RVQoE and may indicate to network entity 105-c that the QoE assistance information is for sidelink communication (e.g., indicating to network entity 105-c that the RVQoE assistance information will be used for PC5 RVQoE collection).

[0089] At point 415, network entity 105-c may send QoE configuration to the first UE 115-e. The QoE configuration may be sent via RRC signaling through the access link (e.g., a Uu link) with the first UE 115-e. In some cases, network entity 105-c may indicate to the first UE 115-e that the RVQoE configuration is intended for use on the PC5 interface. In some cases, the first UE 115-e may collect and report QoE measurements based on its own measurements of its sidelink connection with the second UE 115-f, and may not need to provide QoE configuration to the second UE 115-f. In other cases, the first UE 115-e may provide QoE configuration to the second UE 115-f.

[0090] At 420, where QoE configuration is provided to the second UE 115-f, the first UE 115-e may forward the QoE configuration to the second UE 115-f. The QoE configuration may be provided, for example, via PC5 RRC signaling for the sidelink connection between the first UE 115-e and the second UE 115-f.

[0091] At locations 425-a and 425-b, one or both of the first UE 115-e and the second UE 115-f may collect QoE measurements. For example, the receiving UE's application layer may collect RVQoE measurements and indicate auxiliary information along with the RVQoE measurements to the AS layer. In some cases, the auxiliary information may include one or more of the following: sidelink bearer ID, PFI, application information (e.g., application, IP address), or any combination thereof.

[0092] At 430, where the second UE 115-f reports QoE, the second UE 115-f can use a sidelink RRC message (e.g., a PC5 RRC message) to forward the RVQoE measurement along with auxiliary information to the first UE 115-e (e.g., the sending UE). Where the first UE 115-e reports its own QoE measurement, the first UE can obtain the collected RVQoE measurement and auxiliary information (e.g., from the application layer). At 435, the first UE 115-e can derive one or more of the PFI, sidelink bearer ID, or resource allocation mode.

[0093] At 440, the first UE 115-e may forward the QoE report to network entity 105-c. In some cases, the QoE report may be provided via RRC signaling over the Uu link. In some cases, network entity 105-c may process RVQoE measurements and may determine one or more parameters that can be adjusted to enhance or optimize the sidelink configuration (e.g., modifying one or more of the transmit resource allocation, sidelink data radio bearer (DRB) configuration, or discontinuous reception (DRX) configuration).

[0094] Figure 5 An example of a process flow 500 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. In some examples, process flow 500 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the UE and network entities, or those implemented by them. For example, process flow 500 may be implemented by CN 505, network entity 105-d, first UE 115-g, and second UE 115-h, which may be as referenced. Figure 1 and Figure 2Examples of corresponding devices described. Process flow 500 can be implemented by CN 505, network entity 105-d, and UE 115 to exchange signaling to facilitate reliable communication that meets the QoE objectives of one or more services provided via sidelink communication. In the following description of process flow 500, operations between CN 505, network entity 105-d, first UE 115-g, and second UE 115-h may be sent in a different order than the example order shown, or operations performed by CN 505, network entity 105-d, first UE 115-g, and second UE 115-h may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0095] In this example, signaling-based QoE activation is provided for the sidelink connection between the first UE 115-g and the second UE 115-h, where the second UE 115-h is a remote UE that communicates with network entity 105-c via the first UE 115-g, which acts as a relay UE. At 510, when network entity 105-d is provided with QoE configuration information (e.g., one or more configurations for container-based QoE) for the associated relay UE (which in this example is the first UE 115-g), CN 505 (e.g., the Access and Mobility Function (AMF) at CN) may provide a remote ID to network entity 105-d.

[0096] At point 515, network entity 105-d may send QoE configuration to the first UE 115-g. The QoE configuration may be sent via an access link (e.g., a Uu link) with the first UE 115-g using RRC signaling. In some cases, network entity 105-d may indicate to the first UE 115-g the expected remote UE identifier (e.g., the identifier of the second UE 115-h, which may include a Subscription Hidden Identifier (SUCI) or a Prose Remote User Key ID (PRUK-ID)).

[0097] At position 520, the first UE 115-g can forward the QoE configuration to the second UE 115-h. The QoE configuration can be provided, for example, via PC5 RRC signaling used for the sidelink connection between the first UE 115-g and the second UE 115-h. The QoE configuration may include container information, service type, and the UE identifier (e.g., RRC ID) of the second UE 115-h.

[0098] At 525, the second UE 115-h can collect QoE measurements. For example, the UE application layer can collect QoE measurements. At 530, the second UE 115-h can use a sidelink RRC message (e.g., a PC5 RRC message) to forward a QoE report, including QoE measurements, to the first UE 115-g (e.g., a relay UE).

[0099] At 535, the first UE 115-g can forward the QoE report container to network entity 105-d. In some cases, QoE reports can be provided via RRC signaling over the Uu link. At 540, network entity 105-d can forward the QoE report to CN505. In some cases, post-processing can be performed based on the report, where CN 505 can determine the QoE measurements collected for a sidelink interface (e.g., the PC5 interface) and can adjust one or more parameters to enhance or optimize the sidelink configuration (e.g., modify transmit resource allocation or transmit bearer configuration, etc.).

[0100] Figure 6 An example of a process flow 600 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. In some examples, process flow 600 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the UE and network entities, or those implemented by them. For example, process flow 600 can be implemented by OAM 605, network entity 105-e, first UE 115-i, and second UE 115-j, which can be as referenced. Figure 1 and Figure 2 Examples of corresponding devices described. Process flow 600 can be implemented by OAM 605, network entity 105-e, and UE 115 to exchange signaling to facilitate reliable communication that meets the QoE objectives of one or more services provided via sidelink communication. In the following description of process flow 600, operations between OAM 605, network entity 105-e, first UE 115-i, and second UE 115-j may be sent in a different order than the example order shown, or operations performed by OAM 605, network entity 105-e, first UE 115-i, and second UE 115-j may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0101] In this example, managed QoE activation is provided for the sidelink connection between a first UE 115-i and a second UE 115-j, where the second UE 115-j is a remote UE that communicates with network entity 105-c via the first UE 115-i, which acts as a relay UE. At 610, OAM 605 may provide network entity 105-e with QoE configuration information (e.g., one or more configurations for container-based QoE) for the associated relay UE, which in this example is the first UE 115-i.

[0102] At point 615, network entity 105-e may send QoE configuration to first UE 115-i. The QoE configuration may be sent via an access link (e.g., a Uu link) with first UE 115-i using RRC signaling. In some cases, network entity 105-e may indicate to first UE 115-i that the configuration will be provided to a remote UE.

[0103] At 620, the first UE 115-i may select one or more remote UEs to receive QoE configuration information. In some cases, the remote UE may include a second UE 115-j, and may be selected based on the reporting capabilities of the remote UE (e.g., in capability reports from each UE) to provide QoE measurement reports for sidelink connections.

[0104] At position 625, the first UE 115-i may forward the QoE configuration to the second UE 115-j. The QoE configuration may be provided, for example, via PC5 RRC signaling used for the sidelink connection between the first UE 115-i and the second UE 115-j. The QoE configuration may include container information, service type, and the UE identifier (e.g., RRC ID) of the second UE 115-j.

[0105] At 630, the second UE 115-j can collect QoE measurements. For example, the UE application layer can collect QoE measurements. At 635, the second UE 115-j can use a sidelink RRC message (e.g., a PC5 RRC message) to forward a QoE report, including QoE measurements, to the first UE 115-i (e.g., a relay UE).

[0106] At 640, the first UE 115-i can forward the QoE report container to network entity 105-e. In some cases, QoE reports can be provided via RRC signaling over the Uu link. At 645, network entity 105-e can forward the QoE report to OAM 605. In some cases, post-processing can be performed based on the report, and one or more parameters can be adjusted to enhance or optimize the sidelink configuration (e.g., modify transmit resource allocation (e.g., for sidelink resource pools) or transmit bearer configuration, etc.).

[0107] Figure 7 An example of a process flow 700 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. In some examples, process flow 700 may be implemented as described in the reference. Figure 1 and Figure 2 The described aspects of the UE and network entities, or those implemented by them. For example, process flow 700 can be implemented by MCE 705, network entity 105-f, first UE 115-k, and second UE 115-l, which can be as referenced. Figure 1 and Figure 2 Examples of corresponding devices described. Process flow 700 can be implemented by MCE 705, network entity 105-f, and UE 115 to exchange signaling to facilitate reliable communication that meets the QoE objectives of one or more services provided via sidelink communication. In the following description of process flow 700, operations between MCE 705, network entity 105-f, first UE 115-k, and second UE 115-l may be sent in a different order than the example order shown, or operations performed by MCE 705, network entity 105-f, first UE 115-k, and second UE 115-l may be performed in a different order or at different times. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0108] In this example, QoE for L3-based U2N relay communication via a sidelink can be provided. As discussed herein, this report can be used for container-based QoE reporting or for RVQoE reporting. At 710, the second UE 115-l can collect QoE measurements. For example, the UE application layer can collect QoE measurements. At 715, the second UE 115-l can use a sidelink RRC message (e.g., a PC5 RRC message) to forward a QoE report including QoE measurements or an RVQoE report to the first UE 115-k (e.g., the relay UE). If a QoE reporting container is present, the second UE 115-l can include the RRC ID in the RRC message and transmit the QoE report to the relay UE. If RVQoE is provided, the second UE 115-l can include the SL bearer ID, PFI, and application information (e.g., application ID, IP address) in the RVQoE report. In some cases, a QoE report can be provided in an RRC message defined for such a QoE report.

[0109] At 720, the first UE 115-k may forward a QoE report container or an RVQoE report to network entity 105-f. In some cases, the QoE report container or RVQoE report may be provided via a Uu link using RRC signaling. Where a QoE report container is present, the first UE 115-k may include the RRC ID received from the second UE 115-l. Additionally, in some cases, the first UE 115-k may include the UE ID of the second UE 115-l. Where RVQoE is provided, the first UE 115-k may derive auxiliary information (e.g., resource allocation mode, sidelink SL DRB configuration information, PFI) for forwarding to network entity 105-f along with the RVQoE report. Optionally, the first UE 115-k may utilize the QoE report to indicate the UE ID of the second UE 115-l.

[0110] At 725, network entity 105-f can forward QoE reports to MCE 705. In some cases, post-processing can be performed based on the reports, and one or more parameters can be adjusted to enhance or optimize sidelink configurations (e.g., modifying transmit resource allocation (e.g., for sidelink resource pools) or transmit bearer configurations, etc.).

[0111] In some respects, one or more QoE reports in the described QoE report may provide an indication of the communication mode used for the sidelink UE. For example, it may provide an indication that the QoE collection is for PC5 direct communication, L2 U2N relay communication, or L3 U2N relay communication. In some cases, for container QoE, the UE may indicate the communication mode in the container for each measurement. In some cases, for RVQoE, the UE may indicate the communication mode in the RRC message.

[0112] Figure 8 A block diagram 800 of a device 805 for collecting QoE measurements over supported sidelink communication according to one or more aspects of this disclosure is shown. Device 805 may be an example of various aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0113] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to QoE measurement collection on sidelink communications). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0114] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to QoE measurement collection over sidelink communication), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0115] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of QoE measurement collection on sidelink communications as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0116] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0117] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0118] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or integrate with or in combination with the receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0119] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. The communication manager 820 may be capable of, configured to, or operable to support components for obtaining a set of QoE measurements for a sidelink connection with the second UE based on the QoE measurement configuration. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting a QoE measurement report for a sidelink connection with the second UE based on the set of QoE measurements.

[0120] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for configuring and reporting QoE measurements for the services provided using sidelink communication, which can improve communication reliability, reduce latency, and improve user experience.

[0121] Figure 9A block diagram 900 of a device 905 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to QoE measurement collection on sidelink communications). The information may be delivered to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0123] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to QoE measurement collection on sidelink communications), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0124] Device 905 or its various components may be examples of parts used to perform various aspects of QoE measurement collection on sidelink communications as described herein. For example, communication manager 920 may include QoE configuration manager 925, QoE measurement manager 930, sidelink QoE reporting manager 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0125] The communication manager 920 can support wireless communication according to the examples disclosed herein. The QoE configuration manager 925 is capable of, configured to, or operable to support components for receiving signaling indicating a QoE measurement configuration for a sidelink connection with the second UE. The QoE measurement manager 930 is capable of, configured to, or operable to support components for obtaining a set of QoE measurements for the sidelink connection with the second UE based on the QoE measurement configuration. The sidelink QoE reporting manager 935 is capable of, configured to, or operable to support components for sending a QoE measurement report for the sidelink connection with the second UE based on the QoE measurement set.

[0126] Figure 10 A block diagram 1000 of a communication manager 1020 supporting QoE measurement collection over sidelink communication according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of QoE measurement collection over sidelink communication as described herein. For example, the communication manager 1020 may include a QoE configuration manager 1025, a QoE measurement manager 1030, a sidelink QoE reporting manager 1035, a QoE auxiliary information manager 1040, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0127] Communication Manager 1020 may support wireless communication according to examples disclosed herein. QoE Configuration Manager 1025 is capable of, configured to, or operable to support components for receiving signaling indicating a QoE measurement configuration for a sidelink connection with the second UE. QoE Measurement Manager 1030 is capable of, configured to, or operable to support components for obtaining a set of QoE measurements for the sidelink connection with the second UE based on the QoE measurement configuration. Sidelink QoE Report Manager 1035 is capable of, configured to, or operable to support components for sending a QoE measurement report for the sidelink connection with the second UE based on the QoE measurement set. In some examples, the QoE measurement configuration is received from a network entity using an access link connection, and the QoE measurement report for the sidelink connection with the second UE is sent to the network entity using the access link connection.

[0128] In some examples, the QoE configuration manager 1025 is capable of, configured to, or operable to support components for receiving signaling indicating that QoE measurement configuration is applied to direct communication between a first UE and a second UE using a sidelink connection. In some examples, the QoE configuration manager 1025 is capable of, configured to, or operable to support components for sending QoE measurement configuration to a second UE using a sidelink connection.

[0129] In some examples, to support obtaining a set of QoE measurements, the QoE measurement manager 1030 is capable of, configured to, or operable to support components for receiving a set of QoE measurements, such as those measured at the second UE, from a second UE using a sidelink connection. In some examples, to support obtaining a set of QoE measurements, the QoE measurement manager 1030 is capable of, configured to, or operable to support components for receiving a set of QoE measurements, such as those measured at the application layer of the first UE, for a sidelink connection with the second UE, from an application layer of the first UE.

[0130] In some examples, the sidelink QoE report manager 1035 is capable of, configured to, or operable to support components for providing the access layer of the first UE with a sidelink connection interface indication and a set of QoE measurements for transmission in the QoE measurement report. In some examples, to support reception, the QoE configuration manager 1025 is capable of, configured to, or operable to support components for receiving from a network entity a set of multiple radio access network visible QoE parameters associated with the QoE measurement report, and an indication of the set of multiple radio access network visible QoE parameters associated with the sidelink connection of the second UE.

[0131] In some examples, to support the acquisition of a set of QoE measurements, the QoE Auxiliary Information Manager 1040 can be, configured, or operated to support components for obtaining auxiliary information from the relay UE and a set of QoE measurements visible across multiple radio access networks. In some examples, the auxiliary information includes one or more of the following: a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application Internet Protocol address, or any combination thereof.

[0132] In some examples, the QoE measurement manager 1030 is capable of, configured to, or operable to support components for determining one or more QoE parameters based on a QoE measurement configuration, including one or more of a container identifier, a type of service indication, a radio resource control identifier, or a UE identifier of a second UE. In some examples, the sidelink QoE reporting manager 1035 is capable of, configured to, or operable to support components for sending one or more QoE parameters to a second UE.

[0133] In some examples, the QoE measurement configuration includes an indication of whether a first UE should forward the configuration to one or more remote UEs, and the QoE configuration manager 1025 is capable, configured, or operable to support components for sending the QoE measurement configuration to at least a second UE in response to determining that a second UE has the capability to provide a QoE measurement report. In some examples, obtaining the QoE measurement set includes using a sidelink connection to receive a QoE report container from a radio resource control message from the second UE. In some examples, sending the QoE measurement report includes using an access link connection to send the QoE report container to a network entity.

[0134] In some examples, obtaining the QoE measurement set includes using a sidelink connection to receive a radio access network visible QoE report from a radio resource control message from the second UE. In some examples, sending the QoE measurement report includes deriving auxiliary information associated with the QoE report and the identifier of the second UE, and using an access link connection to send the QoE report and auxiliary information to a network entity, wherein the auxiliary information includes one or more of a resource allocation mode associated with the sidelink connection, a sidelink data radio bearer configuration, or a sidelink connection stream ID.

[0135] In some examples, the QoE measurement report provides one or more of the following: an indication of a QoE measurement set associated with direct communication with a second UE using a sidelink connection; an indication from the first UE to the second UE of a Layer 2 UE-to-network relay; an indication from the first UE to the second UE of a Layer 3 UE-to-network relay; an indication of a container associated with the QoE measurement set; or an indication in a radio resource control signaling message that the QoE measurement report includes a radio access network visible QoE measurement set.

[0136] Figure 11A diagram of a system 1100 including device 1105 supporting QoE measurement collection over sidelink communication, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1145).

[0137] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0138] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 as described herein, or via a wired or wireless link. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0139] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable, computer-executable code 1135, including instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1130 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0140] At least one processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., various functions or tasks supporting QoE measurement collection over sidelink communication). For example, device 1105 or components of device 1105 may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to at least one processor 1140, wherein at least one processor 1140 and at least one memory 1130 are configured to perform the various functions described herein. In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, capable of being configured, or operable to cause device 1105 to perform one or more of the functions described herein. Additionally, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1130 or otherwise.

[0141] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be configured or operable to support components for receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. The communication manager 1120 may be configured or operable to support components for obtaining a set of QoE measurements for the sidelink connection with the second UE based on the QoE measurement configuration. The communication manager 1120 may be configured or operable to support components for transmitting a QoE measurement report for the sidelink connection with the second UE based on the set of QoE measurements.

[0142] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for configuring and reporting QoE measurements for the services provided using sidelink communication, which can improve communication reliability, reduce latency, and improve user experience.

[0143] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) in cooperation with transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported by or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause device 1105 to perform various aspects of QoE measurement collection over sidelink communication as described herein, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0144] Figure 12 A block diagram 1200 of a device 1205 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. Device 1205 may be an example of various aspects of network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205, or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0145] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0146] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0147] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of QoE measurement collection on sidelink communications as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0148] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0149] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0150] In some examples, the communication manager 1220 may be configured to use or otherwise cooperate with the receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0151] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for sending signaling to a first UE indicative of a QoE measurement configuration for a sidelink connection between the first UE and a second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving from the first UE a QoE measurement report for the sidelink connection between the first UE and the second UE, including the set of QoE measurements.

[0152] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for configuring and reporting QoE measurements for the services provided using sidelink communication, which can improve communication reliability, reduce latency, and improve user experience.

[0153] Figure 13 A block diagram 1300 of a device 1305 for collecting QoE measurements over a supporting sidelink communication according to one or more aspects of this disclosure is shown. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305, or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, and communication manager 1320), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0154] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0155] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0156] Device 1305 or its various components may be examples of components used to perform various aspects of QoE measurement collection on sidelink communications as described herein. For example, communication manager 1320 may include QoE configuration manager 1325, sidelink QoE reporting manager 1330, or any combination thereof. Communication manager 1320 may be an example of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use receiver 1310, transmitter 1315, or both, or otherwise cooperate with receiver 1310, transmitter 1315, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0157] Communication manager 1320 may support wireless communication according to examples disclosed herein. QoE configuration manager 1325 is capable of, configured to, or operable to support components for sending signaling to a first UE indicative of QoE measurement configuration for a sidelink connection between the first UE and a second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. Sidelink QoE reporting manager 1330 is capable of, configured to, or operable to support components for receiving from the first UE a QoE measurement report for the sidelink connection between the first UE and the second UE, including the set of QoE measurements.

[0158] Figure 14A block diagram 1400 is shown of a communication manager 1420 supporting QoE measurement collection over sidelink communication according to one or more aspects of this disclosure. The communication manager 1420 may be an example of aspects of the communication manager 1220, communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of QoE measurement collection over sidelink communication as described herein. For example, the communication manager 1420 may include a QoE configuration manager 1425, a sidelink QoE reporting manager 1430, a QoE measurement manager 1435, a QoE auxiliary information manager 1440, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0159] Communication manager 1420 may support wireless communication according to examples disclosed herein. QoE configuration manager 1425 is capable of, configured to, or operable to support components for sending signaling to a first UE indicative of QoE measurement configuration for a sidelink connection between the first UE and a second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. Sidelink QoE reporting manager 1430 is capable of, configured to, or operable to support components for receiving from the first UE a QoE measurement report for the sidelink connection between the first UE and the second UE, including the set of QoE measurements.

[0160] In some examples, the QoE measurement configuration is sent to the first UE using an access link connection, and the QoE measurement report for the sidelink connection between the first UE and the second UE is received from the first UE using the access link connection. In some examples, the QoE configuration manager 1425 is capable of, configured to, or operable to support components for sending signaling indicating that the QoE measurement configuration is for direct communication between the first UE and the second UE using a sidelink connection. In some examples, the QoE measurement configuration indicates that the first UE will send the QoE measurement configuration to the second UE using a sidelink connection. In some examples, the QoE measurement set is measured at the application layer at either the first UE or the second UE for the sidelink connection between the first UE and the second UE. In some examples, the QoE measurement report includes an indication that the QoE measurement set is associated with the second UE.

[0161] In some examples, to support the transmission of QoE measurement configuration, the QoE configuration manager 1425 can be configured or operated to support components for transmitting to the first UE a set of multiple RVQoE parameters associated with a QoE measurement report and a set of multiple radio access network visible QoE parameters associated with a sidelink connection to the second UE. In some examples, the QoE measurement report includes ancillary information and a set of multiple RVQoE measurements of the first UE, wherein the ancillary information includes one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application Internet Protocol address, or any combination thereof.

[0162] In some examples, the QoE measurement configuration includes an indication of whether the first UE should forward the configuration to one or more remote UEs. In some examples, the QoE measurement report provides one or more of the following: an indication of the QoE measurement set being associated with direct communication between the first UE and the second UE using a sidelink connection; an indication of the first UE providing a Layer 2 UE-to-network relay to the second UE; an indication of the first UE providing a Layer 3 UE-to-network relay to the second UE; an indication of the container associated with the QoE measurement set; or an indication in a radio resource control signaling message that the QoE measurement report includes a radio access network visible QoE measurement set.

[0163] Figure 15 A diagram of a system 1500 including device 1505 supporting QoE measurement collection over sidelink communication, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and obtaining communication, such as a communication manager 1520, a transceiver 1510, an antenna 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1540).

[0164] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processors or one or more memory components or configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515 and one or more processors or one or more memory components (e.g., at least one processor 1535, at least one memory 1525, or both) may be included in a chip or chip assembly mounted in device 1505. In some examples, transceiver 1510 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0165] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by one or more processors of at least one processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by one of the at least one processor 1535, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1525 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0166] At least one processor 1535 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1535. At least one processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1525) to cause device 1505 to perform various functions (e.g., various functions or tasks supporting QoE measurement collection over sidelink communication). For example, device 1505 or components of device 1505 may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in at least one processor 1535, wherein at least one processor 1535 and at least one memory 1525 are configured to perform the various functions described herein. At least one processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1530) host functions for performing the functions of device 1505. At least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within one or more memories in at least one memory 1525). In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1535 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1535) and memory circuitry (which may include at least one memory 1525)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1535 or a processing system including at least one processor 1535 may be configured, configured to be configured to, or operated to cause the device 1505 to perform one or more of the functions described herein.Additionally, as described herein, “configured to,” “capable of being configured to,” and “capable of being operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1525 or otherwise.

[0167] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, at least one memory 1525, code 1530 and at least one processor 1535 may be located in one component of different components or partitioned between different components).

[0168] In some examples, the communication manager 1520 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1520 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1520 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0169] The communication manager 1520 may support wireless communication according to examples disclosed herein. For example, the communication manager 1520 may be capable of, configured to, or operable to support components for sending signaling to a first UE indicative of a QoE measurement configuration for a sidelink connection between the first UE and a second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. The communication manager 1520 may be capable of, configured to, or operable to support components for receiving from the first UE a QoE measurement report for the sidelink connection between the first UE and the second UE, including the set of QoE measurements.

[0170] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support techniques for configuring and reporting QoE measurements for the services provided using sidelink communication, which can improve communication reliability, reduce latency, and improve user experience.

[0171] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) in cooperation with transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by transceiver 1510, one or more processors in at least one processor 1535, one or more memories in at least one memory 1525, code 1530, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1535, at least one memory 1525, code 1530, or any combination thereof). For example, code 1530 may include instructions that can be executed by one or more processors in at least one processor 1535 to cause device 1505 to perform various aspects of QoE measurement collection over sidelink communication as described herein, or at least one processor 1535 and at least one memory 1525 may be otherwise configured to perform or support such operations individually or jointly.

[0172] Figure 16 A flowchart illustrating a method 1600 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed as described in reference... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0173] At 1605, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1605 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0174] At 1610, the method may include obtaining a set of QoE measurements for a sidelink connection with a second UE based on a QoE measurement configuration. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be derived from references... Figure 10 The QoE Measurement Manager 1030 described is used to perform this.

[0175] At 1615, the method may include sending a QoE measurement report for a sidelink connection with a second UE based on a set of QoE measurements. Operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1615 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0176] Figure 17 A flowchart illustrating a method 1700 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be achieved by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0177] At 1705, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0178] At 1710, the method may include receiving signaling indicating that QoE measurement configuration is applied to direct communication between a first UE and a second UE using a sidelink connection. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0179] At 1715, the method may include obtaining a set of QoE measurements for a sidelink connection with a second UE based on a QoE measurement configuration. Operation of block 1715 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1715 may be derived from references... Figure 10 The QoE Measurement Manager 1030 described is used to perform this.

[0180] At 1720, the method may include sending a QoE measurement report for a sidelink connection with a second UE based on a set of QoE measurements. Operation of block 1720 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1720 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0181] Figure 18 A flowchart illustrating a method 1800 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be performed as described in reference... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0182] At 1805, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1805 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0183] At 1810, the method may include using a sidelink connection to send a QoE measurement configuration to a second UE. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0184] At 1815, the method may include using a sidelink connection to receive a set of QoE measurements, such as those measured at the second UE, from a second UE. Operation of block 1815 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1815 may be derived from references... Figure 10 The QoE Measurement Manager 1030 described is used to perform this.

[0185] At 1820, the method may include sending a QoE measurement report for the sidelink connection with the second UE based on a set of QoE measurements. Operation of block 1820 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1820 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0186] Figure 19 A flowchart illustrating a method 1900 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by a UE or its components as described herein. For example, operation of method 1900 can be achieved by, as referenced... Figures 1 to 11The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0187] At 1905, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0188] At 1910, the method may include receiving a set of QoE measurements for a sidelink connection with a second UE, as measured at the application layer of the first UE, from the application layer of the first UE. Operation of block 1910 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1910 may be provided by reference to [reference needed]. Figure 10 The QoE Measurement Manager 1030 described is used to perform this.

[0189] At 1915, the method may include sending a QoE measurement report for a sidelink connection with a second UE based on a set of QoE measurements. The operation of block 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1915 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0190] Figure 20 A flowchart illustrating a method 2000 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. The operation of method 2000 can be implemented by a UE or its components as described herein. For example, the operation of method 2000 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0191] At 2005, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0192] At 2010, the method may include obtaining a set of QoE measurements for a sidelink connection with a second UE based on a QoE measurement configuration. The operation of block 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2010 may be derived from references... Figure 10 The QoE Measurement Manager 1030 described is used to perform this.

[0193] At 2015, the method may include providing the access layer of the first UE with a sidelink connectivity interface indication and a set of QoE measurements for transmission in a QoE measurement report. Operation of block 2015 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2015 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0194] At 2020, the method may include sending a QoE measurement report for a sidelink connection with a second UE based on a set of QoE measurements. The operation of box 2020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2020 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0195] Figure 21 A flowchart illustrating a method 2100 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. The operation of method 2100 can be implemented by a UE or its components as described herein. For example, the operation of method 2100 can be implemented by, as referenced... Figures 1 to 11 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0196] At 2105, the method may include receiving signaling indicating a QoE measurement configuration for a sidelink connection with a second UE. Operation of block 2105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2105 may be provided by reference to [reference needed]. Figure 10 The QoE Configuration Manager 1025 described is used for execution.

[0197] At 2110, the method may include obtaining auxiliary information from the relay UE and a set of multiple radio access network visible QoE measurements. The operation of block 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2110 may be derived from references... Figure 10 The QoE Auxiliary Information Manager 1040 described herein is used to execute this.

[0198] At 2115, the method may include sending a QoE measurement report for a sidelink connection with a second UE based on a set of QoE measurements. The operation of block 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2115 may be provided by reference to [reference needed]. Figure 10 The sidelink QoE report manager 1035 described is used to perform this.

[0199] Figure 22 A flowchart illustrating a method 2200 for collecting QoE measurements over a supporting sidelink communication according to various aspects of this disclosure is shown. The operation of method 2200 can be implemented by a network entity or its components as described herein. For example, the operation of method 2200 can be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0200] At 2205, the method may include sending signaling to a first UE indicative of a QoE measurement configuration for a sidelink connection between the first UE and the second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. Operation of block 2205 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2205 may be derived from references... Figure 14 The QoE Configuration Manager 1425 described is used for execution.

[0201] At 2210, the method may include receiving from a first UE a QoE measurement report for a sidelink connection between the first UE and a second UE, including a set of QoE measurements. Operation of block 2210 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2210 may be provided by reference to [reference needed]. Figure 14 The sidelink QoE report manager 1430 described is used to perform this.

[0202] Figure 23 A flowchart illustrating method 2300 for collecting QoE measurements over supported sidelink communication according to various aspects of this disclosure is shown. Operation of method 2300 may be implemented by a network entity or its components as described herein. For example, operation of method 2300 may be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0203] At 2305, the method may include sending signaling to a first UE indicative of a QoE measurement configuration for a sidelink connection between the first UE and the second UE, wherein the QoE measurement configuration indicates a set of QoE measurements to be reported for the sidelink connection between the first UE and the second UE. Operation of block 2305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2305 may be derived from references... Figure 14 The QoE Configuration Manager 1425 described is used for execution.

[0204] At 2310, the method may include sending signaling indicating that the QoE measurement configuration is for direct communication between a first UE and a second UE using a sidelink connection. Operation of block 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2310 may be provided by reference to [reference needed]. Figure 14 The QoE Configuration Manager 1425 described is used for execution.

[0205] At 2315, the method may include receiving from a first UE a QoE measurement report for a sidelink connection between the first UE and a second UE, including a set of QoE measurements. Operation of block 2315 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2315 may be derived from references... Figure 14 The sidelink QoE report manager 1430 described is used to perform this.

[0206] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a first UE, the method comprising: receiving signaling indicating an experience quality measurement configuration for a sidelink connection with a second UE; obtaining an experience quality measurement set for the sidelink connection with the second UE based at least in part on the experience quality measurement configuration; and transmitting an experience quality measurement report for the sidelink connection with the second UE based at least in part on the experience quality measurement set.

[0207] Aspect 2: According to the method of aspect 1, wherein the experience quality measurement configuration is received from a network entity using an access link connection, and the experience quality measurement report for the side link connection with the second UE is sent to the network entity using the access link connection.

[0208] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving signaling instructing the experience quality measurement configuration to be applied to direct communication between the first UE and the second UE using the sidelink connection.

[0209] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: using the side link connection to send the experience quality measurement configuration to the second UE.

[0210] Aspect 5: According to the method of aspect 4, obtaining the set of experience quality measurements includes: using the side link connection to receive the set of experience quality measurements from the second UE as measured at the second UE.

[0211] Aspect 6: The method according to any one of Aspects 1 to 5, wherein obtaining the set of experience quality measurements comprises: receiving, from the application layer at the first UE, the set of experience quality measurements for the side link connection with the second UE, as measured at the application layer of the first UE.

[0212] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: providing the access layer of the first UE with a sidelink connection interface indication of the second UE and the experience quality measurement set for transmission in the experience quality measurement report.

[0213] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the receiving includes: receiving from a network entity a plurality of radio access network visible quality of experience parameters associated with the quality of experience measurement report and an indication of the plurality of radio access network visible quality of experience parameters being associated with the sidelink connection of the second UE.

[0214] Aspect 9: The method according to any one of Aspects 1 to 8, wherein obtaining the set of experience quality measurements includes: obtaining auxiliary information from the relay UE and multiple radio access network visible experience quality measurements.

[0215] Aspect 10: According to the method of aspect 9, the auxiliary information includes one or more of the following: sidelink connection stream ID, sidelink bearer ID, application ID, application Internet Protocol address, or any combination thereof.

[0216] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: determining one or more experience quality parameters based at least in part on the experience quality measurement configuration, the one or more experience quality parameters including one or more of a container identifier, a type of service indication, a radio resource control identifier, or a UE identifier of the second UE; and sending the one or more experience quality parameters to the second UE.

[0217] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the quality of experience measurement configuration includes an indication of whether the first UE wants to forward the configuration to one or more remote UEs; and wherein the method further includes: sending the quality of experience measurement configuration to at least the second UE in response to determining that the second UE has the capability to provide a quality of experience measurement report.

[0218] Aspect 13: The method according to any one of Aspects 1 to 12, wherein obtaining the quality of experience measurement set includes using the side link connection to receive a quality of experience report container from the second UE in a radio resource control message from the second UE; and sending the quality of experience measurement report includes using an access link connection to send the quality of experience report container to a network entity.

[0219] Aspect 14: The method according to any one of Aspects 1 to 13, wherein obtaining the experience quality measurement set includes using the sidelink connection to receive a radio access network visible experience quality report from the second UE in a radio resource control message from the second UE; and sending the experience quality measurement report includes deriving auxiliary information associated with the experience quality report and the identifier of the second UE, and using the access link connection to send the experience quality report and the auxiliary information to a network entity, wherein the auxiliary information includes one or more of a resource allocation mode associated with the sidelink connection, a sidelink data radio bearer configuration, or a sidelink connection flow ID.

[0220] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the quality of experience measurement report provides one or more of the following: an indication of the quality of experience measurement set associated with direct communication with the second UE using the side link connection; an indication from the first UE to the second UE of a Layer 2 UE to network relay; an indication from the first UE to the second UE of a Layer 3 UE to network relay; an indication of a container associated with the quality of experience measurement set; or an indication in a radio resource control signaling message that the quality of experience measurement report includes a radio access network visible quality of experience measurement set.

[0221] Aspect 16: A method for wireless communication by a network entity, the method comprising: sending signaling to a first UE indicating an experience quality measurement configuration for a sidelink connection between the first UE and a second UE, wherein the experience quality measurement configuration indicates a set of experience quality measurements to be reported for the sidelink connection between the first UE and the second UE; and receiving from the first UE an experience quality measurement report for the sidelink connection between the first UE and the second UE, including the set of experience quality measurements.

[0222] Aspect 17: According to the method of aspect 16, wherein the experience quality measurement configuration is sent to the first UE using an access link connection, and the experience quality measurement report for the side link connection between the first UE and the second UE is received from the first UE using the access link connection.

[0223] Aspect 18: The method according to any one of Aspects 16 to 17, the method further comprising: sending signaling indicating that the experience quality measurement configuration is for direct communication between the first UE and the second UE using the sidelink connection.

[0224] Aspect 19: The method according to any one of Aspects 16 to 18, wherein the experience quality measurement configuration instructs the first UE to use the side link connection to send the experience quality measurement configuration to the second UE.

[0225] Aspect 20: The method according to any one of Aspects 16 to 19, wherein the set of experience quality measurements is measured at the application layer of the first UE or the second UE for the sidelink connection between the first UE and the second UE.

[0226] Aspect 21: The method according to any one of Aspects 16 to 20, wherein the experience quality measurement report includes an indication of the experience quality measurement set associated with the second UE.

[0227] Aspect 22: The method according to any one of Aspects 16 to 21, wherein sending the quality of experience measurement configuration includes: sending to the first UE a plurality of radio access network visible quality of experience parameters associated with the quality of experience measurement report and an indication of the plurality of radio access network visible quality of experience parameters being associated with the sidelink connection of the second UE.

[0228] Aspect 23: The method according to any one of Aspects 16 to 22, wherein the experience quality measurement report includes auxiliary information and multiple radio access network visible experience quality measurements of the first UE, and wherein the auxiliary information includes one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application Internet Protocol address, or any combination thereof.

[0229] Aspect 24: The method according to any one of Aspects 16 to 23, wherein the experience quality measurement configuration includes an indication of whether the first UE wants to forward the configuration to one or more remote UEs.

[0230] Aspect 25: The method of any one of claims 16 to 24, wherein the quality of experience (QISA) report provides one or more of the following: an indication of the QISA set being associated with direct communication between the first UE and the second UE using the sidelink connection; an indication from the first UE to the second UE of a Layer 2 UE-to-network relay; an indication from the first UE to the second UE of a Layer 3 UE-to-network relay; an indication of a container associated with the QISA set; or an indication in a radio resource control signaling message that the QISA report includes a radio access network visible QISA set.

[0231] Aspect 26: A first UE for wireless communication, the first UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first UE to perform a method according to any one of aspects 1 to 15.

[0232] Aspect 27: A first UE for wireless communication, the first UE comprising at least one component for performing the method according to any one of aspects 1 to 15.

[0233] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0234] Aspect 29: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 16 to 25.

[0235] Aspect 30: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 16 to 25.

[0236] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 16 to 25.

[0237] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0238] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0239] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0240] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0241] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0242] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0243] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0244] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0245] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0246] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0247] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0248] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE), the first user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the first UE to: receive signaling indicating a quality of experience measurement configuration for a sidelink connection with a second UE; obtain, based at least in part on the quality of experience measurement configuration, a set of quality of experience measurements for the sidelink connection with the second UE; and transmit, based at least in part on the set of quality of experience measurements, a quality of experience measurement report for the sidelink connection with the second UE.

2. The first UE of claim 1, wherein the quality of experience measurement configuration is received from a network entity using an access link connection, and the quality of experience measurement report for the sidelink connection with the second UE is transmitted to the network entity using the access link connection.

3. The first UE of claim 1, wherein the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: receive signaling indicating that the quality of experience measurement configuration applies to direct communications between the first UE and the second UE using the sidelink connection.

4. The first UE of claim 1, wherein the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: transmit the quality of experience measurement configuration to the second UE using the sidelink connection.

5. The first UE of claim 4, wherein, To obtain the set of quality of experience measurements, the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: receive, from the second UE using the sidelink connection, the set of quality of experience measurements as measured at the second UE.

6. The first UE of claim 1, wherein, To obtain the set of quality of experience measurements, the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: receive, from an application layer at the first UE, the set of quality of experience measurements for the sidelink connection with the second UE as measured at the application layer of the first UE.

7. The first UE of claim 1, wherein the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: provide, to an access stratum layer of the first UE, a sidelink connection interface indication of the second UE and the set of quality of experience measurements for transmission in the quality of experience measurement report.

8. The first UE of claim 1, wherein, To receive, the one or more processors are capable of operating, alone or in combination, to execute the code to cause the first UE to: receive, from a network entity, a plurality of radio access network visible quality of experience parameters associated with the quality of experience measurement report and an indication that the plurality of radio access network visible quality of experience parameters are associated with the sidelink connection with the second UE.

9. The first UE of claim 1, wherein, To obtain the set of quality of experience measurements, the one or more processors are individually or collectively capable of operating to execute the code to cause the first UE to: obtain, from a relay UE, assistance information and a plurality of radio access network visible quality of experience measurements.

10. The first UE of claim 9, wherein the assistance information comprises one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application internet protocol address, or any combination thereof.

11. The first UE of claim 1, wherein the one or more processors are individually or collectively capable of further operating to execute the code to cause the first UE to: determine one or more quality of experience parameters based at least in part on the quality of experience measurement configuration, the one or more quality of experience parameters comprising one or more of a container identification, a service type indication, a radio resource control identification, or a UE identification of the second UE; and transmit the one or more quality of experience parameters to the second UE.

12. The first UE of claim 1, wherein the quality of experience measurement configuration comprises an indication of whether the first UE is to forward the configuration to one or more remote UEs, and wherein the one or more processors are individually or collectively capable of further operating to execute the code to cause the first UE to: transmit the quality of experience measurement configuration to at least the second UE in response to determining that the second UE has a capability to provide a quality of experience measurement report.

13. The first UE of claim 1, wherein the one or more processors are individually or collectively capable of further operating to execute the code to cause the first UE to: receive, from the second UE using the sidelink connection, a quality of experience report container in a radio resource control message from the second UE; and transmit the quality of experience report container to a network entity using an access link connection.

14. The first UE of claim 1, wherein the one or more processors are individually or collectively capable of further operating to execute the code to cause the first UE to: receive, from the second UE using the sidelink connection, a radio access network visible quality of experience report in a radio resource control message from the second UE; and derive assistance information associated with the quality of experience report and an identification of the second UE, and transmit the quality of experience report and the assistance information to a network entity using an access link connection, wherein the assistance information comprises one or more of a resource allocation pattern associated with the sidelink connection, a sidelink data radio bearer configuration, or a sidelink connection flow ID.

15. The first UE of claim 1, wherein the quality of experience measurement report provides one or more of the set of quality of experience measurements with an indication that the set of quality of experience measurements is associated with direct communications between the second UE using the sidelink connection, an indication that the first UE provides layer 2 UE-to-network relay for the second UE, an indication that the first UE provides layer 3 UE-to-network relay for the second UE, an indication of a container associated with the set of quality of experience measurements, or an indication in a radio resource control signaling message that the quality of experience measurement report includes a set of radio access network visible quality of experience measurements.

16. A network entity, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the network entity to: send, to a first user equipment (UE), signaling indicating a quality of experience measurement configuration for a sidelink connection between the first UE and a second UE, wherein the quality of experience measurement configuration indicates a set of quality of experience measurements to be reported for the sidelink connection between the first UE and the second UE; and receive, from the first UE, a quality of experience measurement report for the sidelink connection between the first UE and the second UE including the set of quality of experience measurements.

17. The network entity of claim 16, wherein the quality of experience measurement configuration is sent to the first UE using an access link connection and the quality of experience measurement report for the sidelink connection between the first UE and the second UE is received from the first UE using the access link connection.

18. The network entity of claim 16, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the network entity to: send signaling indicating that the quality of experience measurement configuration is for direct communications between the first UE and the second UE using the sidelink connection.

19. The network entity of claim 16, wherein the quality of experience measurement configuration indicates that the first UE is to send the quality of experience measurement configuration to the second UE using the sidelink connection.

20. The network entity of claim 16, wherein the set of quality of experience measurements is measured at an application layer at the first UE or the second UE for the sidelink connection between the first UE and the second UE.

21. The network entity of claim 16, wherein the quality of experience measurement report includes an indication that the set of quality of experience measurements is associated with the second UE.

22. The network entity of claim 16, wherein, To send the quality of experience measurement configuration, the one or more processors are capable of operating, alone or in combination, to execute the code to cause the network entity to: transmitting, to the first UE, a plurality of radio access network visible quality of experience parameters associated with the quality of experience measurement report and an indication that the plurality of radio access network visible quality of experience parameters are associated with the sidelink connection with the second UE.

23. The network entity of claim 16, wherein the quality of experience measurement report comprises assistance information and a plurality of radio access network visible quality of experience measurements for the first UE, and wherein the assistance information comprises one or more of a sidelink connection flow ID, a sidelink bearer ID, an application ID, an application internet protocol address, or any combination thereof.

24. The network entity of claim 16, wherein the quality of experience measurement configuration comprises an indication of whether the first UE is to forward the configuration to one or more remote UEs.

25. The network entity of claim 16, wherein the quality of experience measurement report provides one or more of an indication that the set of quality of experience measurements are associated with direct communications between the first UE and the second UE using the sidelink connection, an indication that the first UE provides layer 2 UE-to-network relay for the second UE, an indication that the first UE provides layer 3 UE-to-network relay for the second UE, an indication of a container associated with the set of quality of experience measurements, or an indication in a radio resource control signaling message that the quality of experience measurement report includes a set of radio access network visible quality of experience measurements.

26. A method for wireless communications by a first user equipment (UE), comprising: receiving signaling indicating a quality of experience measurement configuration for a sidelink connection with a second UE; obtaining a set of quality of experience measurements for the sidelink connection with the second UE based at least in part on the quality of experience measurement configuration; and transmitting a quality of experience measurement report for the sidelink connection with the second UE based at least in part on the set of quality of experience measurements.

27. The method of claim 26, further comprising: transmitting the quality of experience measurement configuration to the second UE using the sidelink connection; and receiving the set of quality of experience measurements as measured at the second UE from the second UE using the sidelink connection.

28. The method of claim 26, wherein the receiving comprises: receiving, from a network entity, a plurality of radio access network visible quality of experience parameters associated with the quality of experience measurement report and an indication that the plurality of radio access network visible quality of experience parameters are associated with the sidelink connection with the second UE.

29. A method for wireless communications by a network entity, comprising: transmitting, to a first user equipment (UE), signaling indicating a quality of experience measurement configuration for a sidelink connection between the first UE and a second UE, wherein the quality of experience measurement configuration indicates a set of quality of experience measurements for the sidelink connection between the first UE and the second UE to be reported; and receive, from the first UE, an experience quality measurement report for the sidelink connection between the first UE and the second UE including the set of experience quality measurements.

30. The method of claim 29, wherein the experience quality measurement configuration indicates that the first UE is to transmit the experience quality measurement configuration to the second UE using the sidelink connection.

Images