UE-triggered reconfiguration for quality of experience (QoE) measurement reports

Abstract

Techniques described herein include a solution for reconfiguring a Quality of Experience (QoE) report triggered by a User Equipment (UE). In one aspect, UE report evaluation is performed to evaluate a QoE report based on UE status or previous QoE measurements. The UE then sends a QoE reconfiguration request or notification to a base station (BS) indicating a QoE measurement reconfiguration preference or decision based on the UE report evaluation. Upon receiving an authorization response or acknowledgement from the BS, the UE may suspend, resume, abort, or change the QoE report accordingly.

Description

Technical Field

[0001] Citation of Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 396,239, entitled “UE-TRIGGERED RECONFIGURATION FOR QUALITY OF EXPERIENCE (QOE) MEASUREMENT REPORTING,” filed on August 9, 2022, and U.S. Provisional Patent Application No. 63 / 396,241, entitled “QUALITY OF EXPERIENCE (QOE) MEASUREMENT REPORTING BASED ON UEEEVALUATION,” both of which are incorporated herein by reference in their entirety. Technical Field

[0004] The present disclosure relates to wireless communication networks, including techniques for reporting application layer measurements. Background Art

[0005] A wireless communication network may include user equipment (UE), base stations (BS), and / or other types of wireless devices capable of communicating with each other. For example, during operation, a UE may perform application layer measurements and report the measurement results to the network for radio resource management. Application layer measurement reports are also referred to as quality of experience (QoE) reports. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The present disclosure will be easily understood and implemented through the specific embodiments and the accompanying drawings. The same reference numerals may designate the same features and structural elements. The accompanying drawings and corresponding descriptions are provided as non-limiting examples of aspects, specific implementations, etc. of the present disclosure, and reference to "one" or "an" aspect, specific implementation, etc. may not necessarily refer to the same aspect, specific implementation, etc., and may mean at least one, one or more, etc.

[0007] Figure 1 is a block diagram illustrating a wireless network including a user equipment (UE) and a base station (BS) for UE-triggered QoE measurement reconfiguration according to some aspects of the present disclosure.

[0008] Figure 2 is a diagram illustrating signaling between a UE and a BS for UE-triggered QoE measurement reconfiguration according to some aspects of the present disclosure.

[0009] Figure 3 is a flow chart illustrating a method for a UE to trigger a QoE measurement reconfiguration according to some aspects of the present disclosure.

[0010] Figure 4 is a schematic diagram illustrating signaling between a UE and a BS for UE-triggered QoE measurement reconfiguration according to some additional aspects of the present disclosure.

[0011] Figure 5 is a flow chart illustrating a method for a UE to trigger a QoE measurement reconfiguration according to some additional aspects of the present disclosure.

[0012] Figure 6 is a diagram illustrating signaling between a UE and a BS for UE-evaluated based QoE measurement configuration according to some aspects of the present disclosure.

[0013] Figure 7 is a schematic diagram illustrating signaling between a UE and a BS for UE-evaluated based QoE measurement configuration according to some additional aspects of the present disclosure.

[0014] Figure 8 is a block diagram illustrating a device that may be employed in accordance with some aspects of the present disclosure.

[0015] Fig. 9 is a block diagram illustrating baseband circuitry that may be employed in accordance with some aspects of the present disclosure. DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description, as other specific implementations may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure.

[0017] Users can experience various services such as augmented reality (AR), virtual reality (VR), multicast / broadcast services, and audio / video streaming through user equipment (UE). Quality of experience (QoE) is a metric used to measure the end-to-end performance of such services at the application level from the user's perspective. During operation, the UE can run various applications and perform corresponding QoE measurements. QoE measurements (which are also called application layer measurements) convey information related to the user experience of the application. For example, for a video stream, a QoE measurement related to playout delay may indicate how long a frame has been stuck or how long a video has been buffered. In some cases, QoE measurements may be reported to the network, for example for radio resource management.

[0018] QoE reports fall into two categories. "Regular" QoE measurements (which may also be referred to as "container-based" QoE measurements) and "Radio Access Network (RAN) visible" QoE measurements. Container-based QoE measurements are included in a container that may be sent to a base station (BS) and then forwarded by the BS to a management entity. The contents of the container may not be visible to the BS. Container-based QoE measurements may be used by operations, administration, and maintenance (OAM) for purposes such as analysis. On the other hand, RAN-visible QoE measurements are reported to the BS and include content that is visible to the BS and may be utilized by the BS to improve radio resource management.

[0019] The BS may suspend or change the QoE report to address situations such as RAN overload, reduce energy consumption, and achieve more efficient operation. For example, the BS may use an RRC message including a suspension indication to temporarily prevent the UE from transmitting a QoE report associated with one or more QoE measurement configurations. When the UE receives the QoE measurement report suspension indication, the UE temporarily stores the QoE report in the access layer (AS) layer. When the UE receives the QoE measurement report resumption indication, the UE transmits the stored QoE report to the BS.

[0020] On the other hand, based on the UE state or previous QoE measurement results, from the UE perspective, the UE may intend to suspend or change the QoE reporting pattern. For example, if the UE has low battery power or high mobility, the UE may prefer to suspend or reduce QoE reporting. As another example, if the UE has strict privacy settings, the UE may reject QoE reporting. Therefore, the present disclosure relates to a technology for UE to trigger reconfiguration of QoE reporting. In some aspects, a UE configured to report QoE measurements may perform a UE report evaluation, such as evaluating its own state and / or previous QoE measurement results, and then suspend, resume, suspend or change the QoE report based on the UE report evaluation. In one aspect, the result of the UE report evaluation is indicated by a QoE reconfiguration request transmitted by the UE, indicating the UE's preference for reconfiguration of the QoE report. The QoE reconfiguration request is sent to the BS, and the BS may respond with a QoE measurement reconfiguration. In another alternative aspect, the UE determines the suspension, resumption or change of the QoE report based on the report evaluation without waiting for a response from the BS. In this case, the UE sends a QoE reconfiguration notification to the BS.

[0021] The QoE reconfiguration request or QoE reconfiguration notification may contain information related to the QoE measurement reconfiguration and may be sent through various signaling as explained in more detail in the following examples. By implementing a UE-triggered mechanism for QoE measurement reconfiguration, the UE may provide suggestions or even determinations based on an evaluation of its own state and / or previous measurements. Thus, the UE performance may be further optimized, such as reducing power consumption or channel resource occupancy when the UE is in a low power or low quality connection state.

[0022] Figure 1 1 is a block diagram illustrating a wireless network 100 including a UE 101 and a BS 111 for UE-triggered QoE measurement reconfiguration according to some aspects. When applicable, the features discussed throughout the disclosure associated with other figures may be incorporated into the wireless network 100. In addition, the following description is provided for an example system operating in conjunction with a 5G or NR system standard as provided by the 3GPP technical specifications. However, the example aspects are not limited in this regard, and the aspects may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0023] like Figure 1 As shown, UE 101 and BS 111 may utilize a connection (or channel) including a physical communication interface / layer for downlink and uplink, respectively. In some aspects, at action 102, based on its own state or previous QoE measurement results, UE 101 may utilize the uplink connection to send a QoE measurement reconfiguration request or notification. At action 104, in response to the received QoE measurement reconfiguration request or notification, BS 111 may utilize the downlink connection to send a QoE reconfiguration response or confirmation. In one aspect, as combined Figures 2 to 3 To further illustrate, the QoE measurement reconfiguration request instructs UE 101 to suspend, resume, terminate or change the preference of QoE reporting, and the QoE reconfiguration response from BS 111 may include approval or rejection of the QoE measurement reconfiguration request. Figures 4 to 5 To further illustrate, the QoE measurement reconfiguration notification may notify BS 111 of a decision by UE 101 to suspend, resume, terminate, or change QoE reporting, and BS 111 may or may not transmit an acknowledgment confirming receipt of the decision. In some aspects, UE 101 may perform UE report evaluation based on UE status or previous QoE measurement results to determine QoE measurement reconfiguration.

[0024] In some aspects, such as combining Figure 6To further illustrate, BS 111 may transmit a QoE measurement / report configuration query to UE 101 before configuring UE 101 for QoE measurement / reporting. UE 101 may perform UE report evaluation to determine whether to accept the QoE measurement / report configuration proposed by BS 111, and then transmit a configuration query response to BS 111 based on the UE report evaluation.

[0025] In some additional aspects, such as combining Figure 7 To further illustrate, after QoE reporting is suspended or changed, BS 111 may transmit a QoE report query to UE 101 after a period of time or triggered by a certain condition. In response to the QoE report query, UE 101 may perform a UE report evaluation to determine whether to resume or change QoE reporting, and may transmit a report query response indicating such a decision to BS 111.

[0026] UE 101 is illustrated as a smart phone (e.g., a handheld touch screen mobile computing device capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device, such as a consumer electronic device, a cellular phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashboard mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, a machine type communication (MTC) device, a machine-to-machine (M2M) device, an Internet of Things (IoT) device, etc.

[0027] UE 101 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 110. RAN 110 may include one or more BSs 111. In some aspects, RAN 110 may be a next generation (NG) RAN or 5G RAN, an evolved-UMTS terrestrial RAN (E-UTRAN), or a traditional RAN such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to a RAN 110 operating in an NR or 5G system, while the term "E-UTRAN" or the like may refer to a RAN 110 operating in an LTE or 4G system. According to various aspects, RAN 110 may be implemented as one or more of dedicated physical devices such as macrocell base stations and / or low power (LP) base stations for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macrocells. BS111 can be an E-UTRAN Node B (evolved Node B, eNodeB or eNB), a next-generation Node B (gNodeB or gNB), or other base stations or TRPs (transmit / receive points) in a wireless communication network.

[0028] The connection between UE 101 and BS111 is illustrated as using an air interface to achieve communication coupling and may be consistent with cellular communication protocols, such as GSM protocols, CDMA network protocols, PTT protocols, POC protocols, UMTS protocols, 3GPP LTE protocols, 5G protocols, NR protocols and / or any other communication protocols discussed herein.

[0029] RAN 110 is shown as being communicatively coupled to a core network (CN) 120. CN 120 may include a plurality of network elements configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. The components of CN 120 may be implemented in one physical node or separate physical nodes, which include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some aspects, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0030] Application server 130 may be an element that provides applications associated with QoE measurements performed by UE 101. Application server 130 may interface with CN 120 via an Internet Protocol (IP) using IP bearer resources. Application server 130 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 101 via CN 120. Application server 130 may signal CN 120 to indicate a new service flow and select appropriate QoS and charging parameters using an appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates QoS and charging specified by application server 130.

[0031] Figure 2 A schematic diagram illustrating signaling between a UE 101 and a BS 111 for UE-triggered QoE measurement reconfiguration according to some aspects of the present disclosure is illustrated. In one aspect, the schematic diagram can be understood as being presented from top to bottom along a timeline, but the various actions can also occur in a different timing order. As specified in more detail below, in some aspects, the UE 101 and the BS 111 can exchange preference information and network configuration information to perform suspension, resumption, termination, and reconfiguration of UE-triggered QoE reporting. In some aspects, with Figure 2 The signaling and methods described in association may include Figure 1 further details or additional or alternative features, and may be incorporated with Figure 1 Some or all of the features disclosed in connection with the invention. Figure 2 The various features shown and described in the drawings may not be considered essential or necessary individually, and may be optionally combined in different ways to present different aspects of the present disclosure when applicable. These principles also apply to other drawings throughout the present disclosure.

[0032] At action 202, in some aspects, QoE measurement collection and reporting may be (pre)configured for UE 101. As an example, BS 111 may send a network configuration to UE 101 via an initial random access procedure or an RRC procedure to configure UE 101 for measurement collection and reporting duration, periodicity, or other conditions and specifications for QoE measurement collection and reporting. For example, the QoE measurement configuration may specify one or more service types, report types, report periodicity, whether the UE should send an indication when a session in the application layer starts and stops, whether segmentation of QoE reports is allowed, and the number of QoE reports within a time period. During the RRC connected state, the QoE measurement configuration may be sent from BS 111 to UE 101 in an RRC message. The QoE measurement configuration may also be referred to as an "application layer measurement configuration" or AppLayerMeasConfig as specified in the 3GPP specification.

[0033] At action 203, in some aspects, UE 101 may report measurement results according to the QoE measurement (pre) configuration to BS 111. UE 101 may also perform QoE measurements based on the QoE measurement (pre) configuration.

[0034] At action 204, in some aspects, UE 101 may be configured to perform a QoE report evaluation. The QoE report evaluation may be used to determine whether UE 101 prefers QoE reporting. In some aspects, the QoE report evaluation may be based on UE status or UE feedback. The state parameters of UE 101 used for QoE report evaluation may include, for example, the battery level of UE 101, the mobility level of UE 101, or the memory usage of UE 101, the buffer status of at least one radio bearer, the channel quality, or the application user settings (e.g., user privacy settings). For example, if there are one or more conditions that limit QoE reporting, UE 101 may not approve QoE reporting. Such conditions may include low battery power, high mobility, high memory usage, large buffer size or congested buffer, poor channel quality, strict privacy settings, or any combination of the above. On the other hand, if there is no condition, UE 101 may allow QoE reporting.

[0035] In some additional aspects, the QoE report evaluation at action 204 may be based on UE feedback including previous QoE measurements. For example, if the QoE measurements meet a threshold indicating satisfactory QoE, UE 101 may decide not to send a QoE report to BS 111 in order to save resources.

[0036] At action 206, in some aspects, UE 101 may send a QoE reconfiguration request to BS 111. UE 101 may send a QoE reconfiguration request to suggest a QoE report change based on a QoE report evaluation. For example, if the QoE report evaluation determines that the QoE report is not approved, the QoE reconfiguration request may indicate the UE 101's preference for suspending QoE reporting. Alternatively or additionally, if the QoE report evaluation determines that the QoE report is required or approved, the QoE reconfiguration request may indicate the UE 101's preference for resuming QoE reporting. The QoE reconfiguration request may also indicate the UE 101's preference for reporting configuration in an idle or inactive state. The QoE reconfiguration request may also indicate the UE's preference for configuring QoE reporting in an idle or inactive state, in which case the configuration may be sent, for example, by RRC signaling in an RRC release message or an RRC reconfiguration message.

[0037] UE 101 may send a QoE reconfiguration request to BS 111 in several ways. In one aspect, the QoE reconfiguration request may include or be sent together with a QoE measurement report. In one aspect, the QoE reconfiguration request may be included in a container and transmitted in the container. The container may be a transparent container of the application layer, a container carrying a QoE measurement report, or a container dedicated to configuring QoE measurements and reports. In another aspect, the QoE reconfiguration request is sent in an RRC message independently of the QoE report.

[0038] In some aspects, for example, the QoE reconfiguration request may be sent as part of a UE Assistance Information (UAI) message as defined in the 3GPP specification (clause 5.7.4 of TS 38.331). In some alternative aspects, the QoE reconfiguration request may be sent by a MAC control element (MAC-CE). In some further alternative aspects, the QoE reconfiguration request may be sent by layer 1 physical layer signaling. In some further alternative aspects, the QoE reconfiguration request may be sent in an inactive or idle state. For example, the UE 101 may send the QoE reconfiguration request message in an inactive or idle state via a small data transmission (SDT) mechanism as defined in the 3GPP specification.

[0039] In some aspects, the QoE reconfiguration request includes information related to one or more parameters of the QoE measurement reconfiguration preferred by the UE 101, such as one or more service types, report types, report periodicity, whether the UE should send an indication when a session in the application layer starts and stops, whether segmentation of QoE reports is allowed, and the number of QoE reports within a time period. The service type can be a service type of an application, such as AR / VR, multicast / broadcast services, and audio / video streams. For example, the report type may include conventional QoE or RAN visible QoE. The QoE report occurrence pattern may include a report periodicity or trigger condition, a report duration, the number of QoE reports within a time period, and the like. The QoE reconfiguration request may also include reasoning information indicating the reason why the UE 101 prefers the requested QoE reconfiguration. For example, the reasoning information may include UE state information, such as power level, mobility level, memory usage, buffer status of at least one radio bearer, channel quality, or application user settings. The reasoning information may also include previous QoE measurement results.

[0040] In one aspect, the QoE reconfiguration request is dedicated to one or more specific QoE measurement configurations. The QoE reconfiguration request may specify one or more QoE configuration identifiers from a set of QoE configuration identifiers. The QoE configuration identifier may also be referred to as a QoE configuration ID, or a QoE reference, or a MeasConfigAppLayerId. Each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration as indicated above. In one aspect, some of the QoE measurement configuration parameters are included in the QoE reconfiguration request, but may not be individually included in each QoE configuration identifier in the set of QoE configuration identifiers.

[0041] At action 208, in some aspects, BS 111 may perform an evaluation of the received QoE reconfiguration request. For example, BS 111 may extract the preference information indicated by UE 101 and send it to the core network (e.g., Figure 1 111 may request a change in the QoE measurement collection (QMC) configuration from at least one entity in the CN 120 in the core network or from the OAM. Additionally or alternatively, the BS 111 may directly forward the QoE reconfiguration request to the OAM or at least one entity in the core network. The OAM or at least one entity in the core network may determine whether a new configuration is required. The OAM or at least one entity in the core network may then respond to the determination back to the BS 111.

[0042] At action 210, in some aspects, BS111 may respond to the received QoE reconfiguration request with a reconfiguration request response. The reconfiguration request response may indicate a rejection or approval of the QoE reconfiguration request. When UE 101 expects a reconfiguration request response, the performance of QoE measurements or the reporting of QoE measurement results may be suspended, resumed, suspended, changed, or otherwise reconfigured based on the reconfiguration request response. For example, BS111 may indicate to UE 101 whether QoE reporting may be suspended, resumed, suspended, changed, or otherwise reconfigured. In one aspect, the reconfiguration request response may reuse the QoE suspension / resumption indication in the RRCReconfiguration message.

[0043] In some alternative aspects, it is assumed that the QoE reconfiguration request is authorized, and a reconfiguration request response may be sent only if the requested reconfiguration is not approved. For example, a timer may be used by UE 101 to determine the QoE measurement or reporting reconfiguration. For example, a timer may be started when UE 101 transmits a QoE reconfiguration request, and the timer may be stopped when a reconfiguration request response is received from BS 111. Otherwise, if no response is received from BS 111 before the timer expires, the UE may assume that the QoE reconfiguration request is authorized (or alternatively rejected). UE 101 may then apply (or not apply if the rejection is associated with the expiration of the timer) its preferred QoE reporting settings.

[0044] At act 212, in some aspects, UE 101 performs reconfigured QoE reporting, such as suspending, resuming, or changing previous QoE reporting.

[0045] Figure 3 is a flow chart illustrating a logical flow of a method for a UE to trigger a QoE measurement reconfiguration according to some aspects of the present disclosure. Figure 1 and Figure 2 The associated present UE 101) may receive the QoE measurement configuration, as shown in action 202, and may perform QoE measurement and reporting accordingly, as shown in action 203.

[0046] In some aspects, the UE may evaluate whether the QoE measurement reconfiguration is preferred, as shown in action 204. The UE may perform the QoE report evaluation based on the UE state or the UE feedback. The UE state parameters used to determine the QoE report evaluation may include, for example, the battery level of the UE, the mobility level of the UE, or the memory usage of the UE, the buffer status of at least one radio bearer, the channel quality, or the application user settings such as the user privacy settings. The UE feedback may include, for example, previous QoE measurement results.

[0047] If the QoE measurement reconfiguration is determined to be not preferred, the UE may continue to perform QoE measurement and reporting according to the QoE measurement configuration, as shown in action 203. If the QoE measurement reconfiguration is determined to be preferred, in some aspects, the UE may send a QoE reconfiguration request to BS111, as shown in action 206. The QoE reconfiguration request may suggest suspending, changing, or resuming QoE reporting. For example, if the UE determines that QoE reporting is not favored or unnecessary, the QoE reconfiguration request may indicate the UE's preference for suspending QoE reporting. If the UE determines that QoE reporting is required or favored, the QoE reconfiguration request may indicate the UE's preference for resuming QoE reporting. The QoE reconfiguration request may also indicate the UE's preference for reporting configurations in an idle or inactive state.

[0048] In some aspects, the UE waits to receive a reconfiguration request response from the BS as a reconfiguration indication, as shown in action 210. The reconfiguration request response may indicate a rejection or approval of the QoE reconfiguration request. In some aspects, the reconfiguration request response may reconfigure the QoE reporting so that the UE suspends, resumes, suspends, or changes the QoE reporting. In some alternative aspects, the QoE reconfiguration request is assumed to be authorized by the BS, and the reconfiguration request response may be received only if the reconfiguration of the QoE request is not approved by the BS.

[0049] In some aspects, when the QoE reconfiguration request is sent, a timer may be started for the UE, and when the UE receives a reconfiguration request response, the timer may be stopped. If the reconfiguration request response is not received before the timer expires, the UE may assume that the QoE reconfiguration request is authorized, and then suspend, resume, or change QoE reporting based on the UE's indicated preference for QoE measurement reconfiguration, as shown in action 212. If a reconfiguration request response is received before the timer expires and the reconfiguration request response indicates that the QoE reconfiguration request is rejected, the UE may continue to perform QoE measurements and reporting according to the previous QoE measurement configuration, as shown in action 203.

[0050] Figure 4 A schematic diagram illustrating signaling between a UE 101 and a BS 111 for UE-triggered QoE measurement reconfiguration according to some aspects of the present disclosure is illustrated. In one aspect, the schematic diagram can be understood as being presented from top to bottom along a timeline, but the various actions can also occur in a different timing order. As specified in more detail below, in some aspects, the UE 101 and the BS 111 can exchange capability information and network configuration information to perform suspension, resumption, termination, and reconfiguration of UE-triggered QoE reporting. In some aspects, the UE 101 and the BS 111 can perform a UE-triggered QoE measurement reconfiguration according to some aspects of the present disclosure. Figure 4 The signaling and methods described in association may include Figure 1 and Figure 2 further details or additional or alternative features, and may be incorporated with Figure 1 and Figure 2 In some aspects, actions with the same number (e.g., actions 202, 203, 204, 212) may perform similar functions, and therefore are not described again for simplicity. In some aspects, after UE 101 performs QoE report evaluation at action 204, UE 101 may send a QoE measurement reconfiguration notification at action 207. At action 211, in response to the received QoE measurement reconfiguration notification, BS 111 may send a notification confirmation to confirm (acknowledge) the receipt of the decision.

[0051] At action 207, in some aspects, the UE 101 may send a QoE reconfiguration notification to indicate a QoE reporting change based on the QoE reporting evaluation. For example, if the QoE reporting evaluation determines that QoE reporting is not favored or unnecessary, the QoE reconfiguration notification may indicate the UE 101's determination to suspend QoE reporting. Alternatively or additionally, if the QoE reporting evaluation determines that QoE reporting is required or favored, the QoE reconfiguration notification may indicate the UE 101's determination to resume QoE reporting. The QoE reconfiguration notification may also indicate the UE 101's determination of a reporting configuration in an idle or inactive state, in which case a pre-configuration may be sent, for example, in an RRC release message or an RRC reconfiguration message.

[0052] UE 101 may send a QoE reconfiguration notification to BS 111, similar to that described above for a QoE reconfiguration request. In one aspect, the QoE reconfiguration notification may include or be sent together with a QoE measurement report. In another aspect, the QoE reconfiguration notification is sent in an RRC message independently of the QoE report. The QoE reconfiguration notification may be part of a UAI message. In some alternative aspects, the QoE reconfiguration notification may be sent by MAC-CE. In some further alternative aspects, the QoE reconfiguration notification may be sent by layer 1 physical layer signaling.

[0053] In some aspects, the QoE reconfiguration notification includes information related to one or more parameters of the QoE measurement reconfiguration determined by the UE 101, one or more service types, report types, report periodicity, whether the UE should send an indication when a session in the application layer starts and stops, whether segmentation of QoE reports is allowed, and the number of QoE reports within a time period. The service type can be a service type of an application, such as AR / VR, multicast / broadcast services, and audio / video streams. For example, the report type may include conventional QoE or RAN visible QoE. The QoE report occurrence pattern may include a report periodicity or trigger condition, a report duration, the number of QoE reports within a time period, and the like. The QoE reconfiguration notification may also include reasoning information for the QoE reconfiguration notification. For example, the reasoning information may include UE state information, such as power level, mobility level, memory usage, buffer status of at least one radio bearer, channel quality, or application user settings. The reasoning information may also include previous QoE measurement results.

[0054] In one aspect, the QoE reconfiguration notification is specific to one or more specific QoE measurement configurations. For example, the QoE reconfiguration notification may indicate whether the decision is for reporting conventional QoE, RAN-visible QoE, or both. The QoE reconfiguration notification may specify one or more QoE configuration identifiers from a set of QoE configuration identifiers. Each QoE configuration identifier in the set of QoE configuration identifiers represents parameters of a QoE measurement configuration as described above, such as service type, reporting type (e.g., conventional QoE, RAN-visible QoE, or both), periodicity, duration, etc.

[0055] At action 211, in some aspects, BS 111 may respond to the received QoE reconfiguration notification with a notification confirmation. The notification confirmation may indicate the receipt of the QoE reconfiguration notification. At action 212, in some aspects, UE 101 performs reconfigured QoE reporting, such as pausing, resuming, suspending, or changing a previous QoE report.

[0056] Figure 5 is a flow chart illustrating a logical flow of a method for a UE to trigger a QoE measurement reconfiguration according to some aspects of the present disclosure. In some aspects, the UE may be, for example, Figure 1 and Figure 4 UE 101 is presented in association. The UE may receive the QoE measurement configuration, as shown in action 202, and may perform QoE measurement and reporting accordingly, as shown in action 203.

[0057] In some aspects, the UE may evaluate whether a QoE measurement reconfiguration is needed, as shown in action 204. The UE may perform the QoE report evaluation based on the UE state or the UE feedback. The UE state parameters used to determine the QoE report evaluation may include, for example, a battery level of the UE, a mobility level of the UE, or a memory usage of the UE, a buffer status of at least one radio bearer, a channel quality, or an application user setting such as a user privacy setting. The UE feedback may include, for example, previous QoE measurement results.

[0058] If the QoE measurement reconfiguration is determined not to be required, the UE may continue to perform QoE measurements and reports according to the QoE measurement configuration, as shown in action 203. If the QoE measurement reconfiguration is determined to be required, in some aspects, the UE may send a QoE reconfiguration notification to the BS, as shown in action 207. In some aspects, the BS may be, for example, Figure 1 and Figure 4BS 111 is presented in association. The QoE reconfiguration notification may indicate to the BS that the UE plans to suspend, resume, terminate, or change the QoE report. For example, if the UE determines that the QoE report is not approved or unnecessary, the QoE reconfiguration notification may indicate to suspend the QoE report. If the UE determines that the QoE report is required or approved, the QoE reconfiguration notification may indicate to resume the QoE report.

[0059] In some aspects, the UE may wait to receive a notification confirmation, as shown in action 211, before performing a QoE reconfiguration, such as suspending, resuming, or changing QoE reporting, as shown in action 212. If the notification confirmation is not received within a predetermined time, the UE may retransmit the QoE reconfiguration notification, as shown in action 207. In some aspects, when the QoE reconfiguration notification is sent, a timer may be started for the UE, and when the UE receives the notification confirmation, the timer may be stopped. If the notification confirmation is not received when the timer expires, the UE may resend the QoE reconfiguration notification, as shown in action 207. If the notification confirmation is received before the timer expires, the UE may suspend, resume, or change QoE reporting, as shown in action 212.

[0060] Figure 6 1 is a schematic diagram illustrating signaling between UE 101 and BS 111 for reconfiguration of QoE measurements based on UE evaluation according to some additional aspects of the present disclosure. Prior to configuring or reconfiguring QoE measurements or reports, BS 111 may send a QoE configuration query to UE 101 to query UE 101's preference or ability to perform such QoE measurements or reports. BS 111 may then configure UE 101 based on feedback received from the UE. In one aspect, the schematic diagram may be understood as being presented from top to bottom along a timeline, but the various actions may also occur in a different timing order. In some aspects, reference may be made to FIG. 104 where applicable. Figures 1 to 5 Some or all of the features disclosed may be incorporated by reference Figure 6 For example, actions 602 to 608 described below may be incorporated before or after the UE sends a QoE measurement reconfiguration request or notification, such as with Figures 2 to 5 Alternatively, actions 602 to 608 described below may be independent of the above disclosed actions 206 or 207. Figures 2 to 5 Related aspects.

[0061] For example, at action 602, BS111 may send a QoE configuration query to UE 101. The QoE configuration query may be sent before configuring or reconfiguring the QoE report. In one aspect, the QoE configuration query is dedicated to one or more specific QoE measurement configurations. The QoE configuration query may specify one or more QoE configuration identifiers from a set of QoE configuration identifiers. Each QoE configuration identifier in the set of QoE configuration identifiers represents parameters of the QoE measurement configuration as described above, such as one or more service types, report types, report periodicity, whether the UE should send an indication when a session in the application layer starts and stops, whether segmentation of the QoE report is allowed, and the number of QoE reports within a time period. The service type may be a service type of an application, such as AR / VR, multicast / broadcast services, and audio / video streams. For example, the report type may include conventional QoE or RAN visible QoE. At action 604, in some aspects, in response to the QoE configuration query, the UE 101 may perform a UE report evaluation to determine whether the QoE measurement configuration is preferred or approved by the UE 101. In some aspects, the UE report evaluation at action 604 may be based on the UE state. The state parameters of the UE 101 used to determine the QoE report evaluation may include, for example, a battery level of the UE 101, a mobility level of the UE 101, or a memory usage of the UE 101, a buffer status of at least one radio bearer, a channel quality, or an application user setting (e.g., a user privacy setting). For example, if the UE 101 has some conditions that restrict reporting, such as low battery power, high mobility, high memory usage, a large buffer size, poor channel quality, strict privacy settings, or any combination of the above, the UE 101 may not approve QoE reporting. On the other hand, if one or more conditions are met (such as none of the above conditions exist), the UE 101 may allow QoE reporting.

[0062] At action 606, in some aspects, UE 101 may transmit a configuration query response indicating a QoE reporting preference or approval / disapproval to BS 111. The configuration query response may also include reasoning information indicating why UE 101 disapproves of initiating, resuming, or changing a QoE report. For example, the reasoning information may include UE state information, such as power level, mobility level, memory usage, buffer status of at least one radio bearer, channel quality, or application user settings. In some aspects, if the current response is disapproval or rejection, the configuration query response may also include timing information related to the duration for which UE 101 will be able to use the QoE measurement configuration. In some additional aspects, the configuration query response is dedicated to one or more specific QoE measurement configurations, such as a QoE configuration identifier or a service type. The QoE configuration identifier represents QoE measurement configuration parameters, such as a reporting category (e.g., conventional QoE, RAN visible QoE, or both), periodicity, duration, etc. The service type may be a type of application, such as AR / VR, multicast / broadcast services, and audio / video streams.

[0063] At act 608, in some aspects, BS 111 may configure UE 101 for QoE reporting based on the configuration query response received from UE 101. For example, if the configuration query response favors QoE measurement configuration, BS 111 may configure QoE reporting based on the configuration query response.

[0064] Figure 7 is a schematic diagram illustrating signaling between UE 101 and BS 111 for UE-evaluated QoE measurement reconfiguration according to some additional aspects of the present disclosure. When BS 111 needs to resume or change QoE reporting from QoE suspension, rather than transmitting a resume signal to the UE to directly resume QoE reporting, BS 111 may first transmit a QoE configuration query to UE 101 to check whether UE 101 prefers or is able to resume or change QoE reporting. In one aspect, the schematic diagram may be understood as being presented from top to bottom along a timeline, but various actions may also occur in a different timing order. In some aspects, when applicable, reference is made to Figures 1 to 6 Some or all of the features disclosed may be incorporated by reference Figure 7 For example, actions 701 to 708 described below may be incorporated before or after the UE performs a QoE reconfiguration, such as pausing, resuming or changing QoE reporting, as described in detail in the accompanying drawings. Figures 2 to 5 Alternatively, actions 701 to 708 described below may be independent of the above disclosed actions. Figures 2 to 5 Related aspects.

[0065] For example, at action 702, BS111 may send a QoE report query to UE 101 to inquire whether to resume or change the QoE report. The QoE report query may be sent before reconfiguring the QoE report. Reconfiguration of the UE report may be required after a period of time, or triggered by a specific condition after the QoE report is suspended or changed at action 701. From the perspective of BS111, the QoE report query may indicate that the QoE report needs to be resumed or changed. In one aspect, the QoE report query is dedicated to one or more specific QoE measurement configurations. The QoE report query may specify one or more QoE configuration identifiers from a set of QoE configuration identifiers. Each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of the QoE measurement configuration, such as a report category (e.g., conventional QoE, RAN visible QoE, or both), periodicity, duration, etc. The QoE report query may alternatively or additionally specify a service type for the QoE report query. The service type may be a service type of an application, for example, AR / VR, multicast / broadcast service, and audio / video streaming, etc.

[0066] At action 704, in some aspects, in response to the QoE report query, the UE 101 may perform a UE report evaluation to determine whether the QoE measurement reconfiguration is preferred or approved by the UE 101. In some aspects, the QoE report evaluation at action 704 may be based on the UE state. The state parameters of the UE 101 used to determine the QoE report evaluation may include, for example, a battery level of the UE 101, a mobility level of the UE 101, or a memory usage of the UE 101, a buffer status of at least one radio bearer, a channel quality, or an application user setting (e.g., a user privacy setting). For example, if the UE 101 has some conditions that restrict reporting, such as low battery power, high mobility, high memory usage, a large buffer size, poor channel quality, strict privacy settings, or any combination of the above, the UE 101 may not approve QoE reporting. On the other hand, if one or more conditions are met (such as none of the above conditions exist), the UE 101 may allow QoE reporting.

[0067] At action 706, in some aspects, UE 101 may transmit a report query response indicating a QoE report preference or approval / disapproval to BS111. The report query response may also include reasoning information indicating why UE 101 disapproves of initiating, resuming, or changing a QoE report. For example, the reasoning information may include UE state information, such as power level, mobility level, memory usage, buffer status of at least one radio bearer, channel quality, or application user settings. In some aspects, the report query response may also include information related to when UE 101 will become available for initiation, recovery, or change if the current response is disapproval. In some other aspects, the report query response is dedicated to one or more specific QoE measurement configurations, such as a QoE configuration identifier or a service type. The QoE configuration identifier represents the QoE measurement configuration parameters as described above, one or more service types, report types, report periodicity, whether the UE should send an indication when a session in the application layer starts and stops, whether segmentation of QoE reports is allowed, and the number of QoE reports within a time period, etc. The service type may be a service type of an application, such as AR / VR, multicast / broadcast service, and audio / video streaming, etc. For example, the report type may include normal QoE or RAN visible QoE.

[0068] At action 708, in some aspects, BS 111 may reconfigure UE 101 based on the report query response received from UE 101. For example, if the report query response favors resuming or changing QoE reporting, BS 111 may instruct UE 101 to resume or change QoE reporting. UE 101 then resumes or changes QoE reporting based on the instruction from BS 111.

[0069] Figure 8800 is a diagram illustrating example components of an employable device 800 according to some aspects. In some aspects, the device 800 may include at least an application circuit 802, a baseband circuit 804, a radio frequency (RF) circuit 806, a front end module (FEM) circuit 808, one or more antennas 810, and a power management circuit (PMC) 812 coupled together as shown. The components of the illustrated device 800 may be included in a UE or a RAN node (such as UE 101 or BS111), as described throughout this disclosure. In some specific implementations, the device 800 may include fewer elements (for example, the RAN node may not utilize the application circuit 802, but include a processor / controller to process IP data received from a core network (CN) (which may be a 5GC or an evolved packet core (EPC)). In some specific implementations, the device 800 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 800, etc.) or an input / output (I / O) interface. In other implementations, the components described below may be included in more than one device (eg, the circuitry may be included solely in more than one device for a Cloud-RAN (C-RAN) implementation).

[0070] The application circuitry 802 may include one or more application processors. For example, the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 800. In some specific implementations, the processor of the application circuitry 802 may process IP data packets received from the EPC.

[0071] The baseband circuit 804 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 804 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 806 and generate baseband signals for the transmit signal path of the RF circuit 806. The baseband circuit 804 or one or more baseband processors or control logic components of the baseband circuit 804 may be independent of the UE 101 or BS 111, and perform signaling and operations in the sense described throughout the present disclosure. The baseband circuit 804 may interact with the application circuit 802 to generate and process baseband signals and control the operation of the RF circuit 806. For example, in some implementations, the baseband circuit 804 may include a third generation (3G) baseband processor 804A, a fourth generation (4G) baseband processor 804B, a fifth generation (5G) baseband processor 804C, or other baseband processors 804D of existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 804 (e.g., one or more baseband processors 804A to 804D) may handle various radio control functions that may communicate with one or more radio networks via the RF circuit 806. In other implementations, some or all of the functions of the baseband processors 804A to 804D may be included in a module stored in the memory 804G and executed via the central processing unit (CPU) 804E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, the modulation / demodulation circuitry of the baseband circuitry 804 may include fast Fourier transform (FFT), pre-decoding, or constellation mapping / demapping functionality. In some implementations, the encoding / decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. The implementation of the modulation / demodulation and encoder / decoder functionality is not limited to these examples and may include other suitable functionality in other implementations.

[0072] In some implementations, the baseband circuitry 804 may include one or more audio digital signal processors (DSPs) 804F. The audio DSP 804F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other implementations. In some implementations, the components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some implementations, some or all of the components of the baseband circuitry 804 and the application circuitry 802 may be implemented together, such as, for example, on a system on a chip (SOC).

[0073] In some implementations, the baseband circuitry 804 may provide communications compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 804 may support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Implementations in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0074] The RF circuit 806 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various specific implementations, the RF circuit 806 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 806 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 808 and providing baseband signals to the baseband circuit 804. The RF circuit 806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 804 and providing RF output signals to the FEM circuit 808 for transmission.

[0075] In some implementations, the receive signal path of the RF circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. In some implementations, the transmit signal path of the RF circuit 806 may include a filter circuit 806c and the mixer circuit 806a. The RF circuit 806 may also include a synthesizer circuit 806d for synthesizing the frequencies used by the mixer circuit 806a of the receive signal path and the transmit signal path. In some implementations, the mixer circuit 806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b may be configured to amplify the down-converted signal, and the filter circuit 806c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 804 for further processing. In some implementations, the output baseband signal can be a zero frequency baseband signal, but this is not required. In some implementations, the mixer circuit 806a of the receive signal path can include a passive mixer, but the scope of the implementation is not limited in this respect.

[0076] In some implementations, the mixer circuit 806a of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 806d to generate an RF output signal for the FEM circuit 808. The baseband signal can be provided by the baseband circuit 804 and can be filtered by the filter circuit 806c.

[0077] In some implementations, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some implementations, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some implementations, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.

[0078] In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the implementation is not limited in this respect. In some alternative implementations, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative implementations, the RF circuit 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 804 may include a digital baseband interface to communicate with the RF circuit 806.

[0079] In some dual-mode implementations, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the implementations is not limited in this respect.

[0080] In some implementations, the synthesizer circuit 806d can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, the synthesizer circuit 806d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0081] The synthesizer circuit 806d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 806a of the RF circuit 806. In some implementations, the synthesizer circuit 806d can be a fractional-N / N+1 synthesizer.

[0082] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission via one or more of the one or more antennas 810. In various implementations, amplification via the transmit signal path or the receive signal path may be performed only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

[0083] In some implementations, the FEM circuitry 808 may include a TX / RX switch to switch between transmit mode operation and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 806); and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 810).

[0084] In some implementations, the PMC 812 can manage the power provided to the baseband circuit 804. Specifically, the PMC 812 can control power selection, voltage scaling, battery charging, or DC to DC conversion. When the device 800 is capable of being powered by a battery, for example, when the device is included in a UE, the PMC 812 can generally be included. The PMC 812 can improve power conversion efficiency while providing the desired implementation size and heat dissipation characteristics.

[0085] Although Figure 8 The PMC 812 is shown coupled only to the baseband circuit 804. However, in other implementations, the PMC 812 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 802, the RF circuit 806, or the FEM circuit 808) and perform similar power management operations for the other components.

[0086] In some implementations, the PMC 812 can control or otherwise be part of various power saving mechanisms of the device 800. For example, if the device 800 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 800 can be powered off for short time intervals to save power.

[0087] If there is no data traffic activity for an extended period of time, the device 800 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 800 enters a very low power state, and it performs paging, in which the device wakes up periodically again to listen to the network, and then powers down again. The device 800 may not receive data in this state; in order to receive data, the device may transition back to the RRC_Connected state.

[0088] An additional power saving mode can render the device unavailable to the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data transmitted during this period will be significantly delayed, assuming that the delay is acceptable.

[0089] The processor of the application circuit 802 and the processor of the baseband circuit 804 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 804 can be used alone or in combination to perform the functions of layer 3, layer 2, or layer 1, and the processor of the baseband circuit 804 can utilize the data received from these layers (e.g., packet data) and further perform the functions of layer 4 (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layer). As mentioned herein, layer 3 may include a radio resource control (RRC) layer. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node.

[0090] Fig. 9 A diagram illustrating an example interface of a baseband circuit that may be employed according to some aspects is illustrated. As discussed above, Figure 8 The baseband circuit 804 may include processors 804A to 804E and a memory 804G used by the processors. Each of the processors 804A to 804E may include a memory interface 904A to 904E for sending / receiving data to / from the memory 804G, respectively.

[0091] The baseband circuit 804 may also include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 912 (e.g., an interface for transmitting / receiving data to / from a memory external to the baseband circuit 804); an application circuit interface 914 (e.g., an interface for transmitting / receiving data to / from a memory external to the baseband circuit 804); Figure 8 RF circuit interface 916 (for example, for transmitting / receiving data to / from the application circuit 802); Figure 8 an interface for transmitting / receiving data to / from a RF circuit 806); a wireless hardware connection interface 918 (e.g., for transmitting / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low energy consumption), components and other communication components to transmit / receive data); and a power management interface 920 (for example, an interface for transmitting / receiving power or control signals to / from PMC 812).

[0092] Embodiments herein may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with a memory (e.g., a processor, etc.), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described specific implementations and embodiments.

[0093] Embodiment 1 is a device of a user equipment (UE), wherein the UE includes one or more processors, and the one or more processors are configured to: send a quality of experience (QoE) reconfiguration or notification to a base station (BS) based on a UE report evaluation; and suspend, resume, terminate or change the QoE report to the BS based on the UE report evaluation.

[0094] Embodiment 2 includes the subject matter of any variation of any one of Embodiment 1, wherein the UE report evaluation is based on UE state parameters, the UE state parameters comprising at least one or more of battery level, mobility level, memory usage, buffer status of at least one radio bearer, channel quality, or application user settings.

[0095] Embodiment 3 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification further includes a QoE measurement report.

[0096] Embodiment 4 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request is sent by a UE Assistance Information (UAI) message.

[0097] Embodiment 5 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request is sent by a MAC control element (MAC-CE).

[0098] Embodiment 6 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification further includes a QoE measurement configuration for an idle or inactive state.

[0099] Embodiment 7 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

[0100] Embodiment 8 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification further includes reasoning information for the quality of experience (QoE) reconfiguration request or notification.

[0101] Embodiment 9 includes the subject matter of any variation of any one of Embodiment 1, wherein before sending the QoE reconfiguration request or notification, the one or more processors are further configured to: receive a network configuration for configuring a QoE report for the UE; and perform QoE measurement based on the configured QoE report and report the QoE measurement result to the BS. The UE report evaluation is based on the QoE measurement result.

[0102] Embodiment 10 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification is a QoE reconfiguration request indicating the UE's preference as to whether the QoE reporting should be paused, resumed, suspended, or changed.

[0103] Embodiment 11 includes the subject matter of any variation of any one of Embodiment 10, wherein after sending the QoE reconfiguration request or notification, the one or more processors are further configured to receive a reconfiguration request response from the BS indicating a rejection or approval of the QoE reconfiguration request, and suspend, resume, terminate, or change the QoE report to the BS based on the reconfiguration request response.

[0104] Embodiment 12 includes the subject matter of any variation of any one of Embodiment 11, wherein the one or more processors are further configured to start a timer when sending the QoE reconfiguration request. If the UE does not receive a response to the reconfiguration request before the timer expires, suspend, resume, terminate, or change the QoE report to the BS.

[0105] Embodiment 13 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification indicates parameters of a QoE measurement reconfiguration, the parameters including reconfiguration of a reporting periodicity, a reporting duration, or a number of QoE reports within a time period.

[0106] Embodiment 14 includes the subject matter of any variation of any one of Embodiment 1, wherein the QoE reconfiguration request or notification is a UE notification to the BS indicating that the QoE reporting is to be suspended, resumed, terminated, or changed.

[0107] Embodiment 15 is a device for a baseband processor of a base station (BS), the device comprising one or more processors configured to: receive a quality of experience (QoE) reconfiguration request or notification from a user equipment (UE) based on a UE report evaluation; and send a request response or notification confirmation to the UE in response to the QoE reconfiguration request or notification.

[0108] Embodiment 16 includes the subject matter of any variation of any one of Embodiment 15, wherein the QoE reconfiguration request or notification indicates UE preferences or capabilities to be reconfigured for QoE measurement reporting.

[0109] Embodiment 17 includes the subject matter of any variation of any one of Embodiment 15, wherein the QoE reconfiguration request or notification is sent by a UE Assistance Information (UAI) message.

[0110] Embodiment 18 includes the subject matter of any variation of any one of Embodiment 15, wherein the QoE reconfiguration request or notification further includes a QoE measurement configuration for an idle or inactive state.

[0111] Embodiment 19 includes the subject matter of any variation of any one of Embodiment 15, wherein the QoE reconfiguration request or notification is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

[0112] Embodiment 20 is a method for a user equipment (UE) to trigger a reconfiguration of a quality of experience (QoE) measurement report. The method includes: performing a UE report evaluation for QoE measurement reconfiguration; sending a QoE reconfiguration request or notification to a base station (BS) based on the UE report evaluation; receiving a request response or notification confirmation from the BS; and suspending, resuming, suspending or changing the QoE report to the BS based on the request response or the notification confirmation.

[0113] Embodiment 21 is a device of a user equipment (UE), the UE comprising one or more processors configured to: receive a quality of experience (QoE) configuration query from a base station (BS) to inquire whether to perform a QoE measurement configuration; and send a configuration query response indicating a rejection or approval of the QoE measurement configuration.

[0114] Embodiment 22 includes the subject matter of any variation of any one of Embodiment 21, wherein the one or more processors are further configured to, after receiving the QoE configuration query, perform a UE report evaluation for the QoE measurement configuration. The UE report evaluation is based on UE state parameters, the UE state parameters comprising at least one or more of a battery level, a mobility level, a memory usage, a buffer status of at least one radio bearer, a channel quality, or an application user setting.

[0115] Embodiment 23 includes the subject matter of any variation of any one of Embodiment 21, wherein the one or more processors are further configured to receive the QoE measurement configuration if the configuration query response indicates the approval of the QoE measurement configuration.

[0116] Embodiment 24 includes the subject matter of any variation of any one of Embodiment 21, wherein the QoE configuration query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of the QoE measurement configuration.

[0117] Embodiment 25 includes the subject matter of any variation of any one of Embodiment 21, wherein the QoE configuration query is specific to one or more service types.

[0118] Embodiment 26 includes the subject matter of any variation of any one of Embodiment 21, wherein in a case where the QoE configuration query is rejected by the UE, the configuration query response includes reasoning information indicating a reason for the rejection of the QoE configuration query.

[0119] Embodiment 27 includes the subject matter of any variation of any one of Embodiment 21, wherein in the event that the configuration query response indicates the rejection of the QoE measurement configuration, the configuration query response includes timing information indicating a duration that the UE will be able to use the QoE measurement configuration.

[0120] Embodiment 28 is a device for a base station (BS), the device comprising one or more processors, the one or more processors being configured to: send a QoE report query to a user equipment (UE) to inquire whether to restore or change a quality of experience (QoE) report; receive a report query response from the UE indicating a rejection or approval of the QoE report query; and configure the UE to restore or change the QoE report based on the report query response.

[0121] Embodiment 29 includes the subject matter of any variation of any one of Embodiment 28, wherein the QoE report query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of the QoE measurement configuration.

[0122] Embodiment 30 includes the subject matter of any variation of any one of Embodiment 28, wherein the QoE report query is specific to one or more service types.

[0123] Embodiment 31 includes the subject matter of any variation of any one of Embodiment 28, wherein in a case where the QoE report query is rejected by the UE, the report query response includes reasoning information indicating a reason for the rejection of the QoE report query.

[0124] Embodiment 32 includes the subject matter of any variation of any one of Embodiment 28, wherein in the event that the QoE report query is rejected by the UE, the report query response includes timing information indicating the duration of the restoration or change that the UE will be able to use for the QoE reporting.

[0125] Embodiment 33 is a device for a user equipment (UE), the device comprising one or more processors configured to: receive a quality of experience (QoE) report query from a base station (BS) to inquire whether to restore or change a QoE report; send a report query response indicating a rejection or approval of the QoE report query; and restore or change the QoE report based on the report query response.

[0126] Embodiment 34 includes the subject matter of any variation of any one of Embodiment 33, wherein the report query response is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

[0127] Embodiment 35 includes the subject matter of any variation of any of Embodiment 33, wherein the report query response is specific to one or more service types.

[0128] Embodiment 36 includes the subject matter of any variation of any one of Embodiment 33, wherein in a case where the QoE report query is rejected by the UE, the report query response includes reasoning information indicating a reason for the rejection of the QoE report query.

[0129] Embodiment 37 includes the subject matter of any variation of any one of Embodiment 33, wherein in the event that the QoE report query is rejected by the UE, the report query response includes timing information indicating the duration of the restoration or change that the UE will be able to use for the QoE reporting.

[0130] Embodiment 38 includes the subject matter of any variation according to any one of Embodiment 33, wherein after sending the report query response, the one or more processors are further configured to receive a QoE measurement reconfiguration from the BS based on the report query response to configure the restoration or change of the QoE report.

[0131] Embodiment 39 includes the subject matter of any variation of any one of Embodiment 33, wherein the QoE report query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

[0132] Embodiment 40 includes the subject matter of any variation of any one of Embodiment 33, wherein the QoE report query is specific to one or more service types.

[0133] Embodiment 41 is a method comprising any action or combination of actions as substantially described herein in the detailed description.

[0134] Example 42 is a method that is substantially described herein with reference to each or any combination of the figures included herein or with reference to each or any combination of the paragraphs in the detailed description.

[0135] Embodiment 43 is a user equipment configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the user equipment.

[0136] Embodiment 44 is a network node configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the network node.

[0137] Embodiment 45 is a non-transitory computer-readable medium storing instructions that, when executed, cause performance of any action or combination of actions as substantially described herein in the detailed description.

[0138] Embodiment 46 is a baseband processor of a user equipment, the baseband processor configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the user equipment.

[0139] Embodiment 47 is a baseband processor of a network node, the baseband processor configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the user equipment.

[0140] Embodiment 48 includes a product comprising one or more tangible computer-readable non-transitory storage media, the one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions, which are operable to enable at least one computer processor to perform a method according to any one of the above embodiments when executed by the at least one processor.

[0141] The above description of illustrative examples, implementations, aspects, etc. of the disclosed subject matter, including what is described in the abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific examples, implementations, aspects, etc. are described herein for illustrative purposes, various modifications can be considered within the scope of such examples, implementations, aspects, etc., as can be appreciated by those skilled in the relevant art.

[0142] In this regard, while the subject matter of the present disclosure has been described in conjunction with various examples, implementations, aspects, etc. and corresponding figures, it should be understood that other similar aspects may be used or modifications and additions may be made to the disclosed subject matter, where applicable, for performing the same, similar, alternative or alternative functions of the subject matter without departing from the disclosed subject matter. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but should be interpreted in accordance with the breadth and scope of the following claims.

[0143] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "components") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations illustrated herein. In addition, while particular features have been disclosed with respect to only one of a plurality of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

[0144] As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement of natural inclusive arrangements. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "one" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more" unless otherwise specified or clear from the context to point to a singular form. In addition, to the extent that the terms "including", "comprising", "having", "having", "with", or variations thereof are used in the specific embodiments and claims, such terms are intended to be included in a manner similar to the term "comprising". Additionally, where one or more numbered items (e.g., "first X", "second X", etc.) are discussed, generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0145] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A device for a user equipment (UE), the device comprising One or more processors configured to: Sending a quality of experience (QoE) reconfiguration request or notification to a base station (BS) based on the UE report evaluation; and The QoE reporting to the BS is suspended, resumed, stopped or changed based on the UE report evaluation.

2. The apparatus of claim 1 , wherein the UE report evaluation is based on UE state parameters, the UE state parameters comprising at least one or more of a battery level, a mobility level, a memory usage, a buffer status of at least one radio bearer, a channel quality, or an application user setting.

3. The apparatus of claim 1, wherein the QoE reconfiguration request or notification further comprises a QoE measurement report.

4. The apparatus of claim 1, wherein the QoE reconfiguration request is sent by a UE Assistance Information (UAI) message.

5. The apparatus of claim 1, wherein the QoE reconfiguration request is sent by a MAC control element (MAC-CE). 6 . The apparatus of claim 1 , wherein the QoE reconfiguration request or notification further comprises a QoE measurement configuration for an idle or inactive state.

7. The apparatus of claim 1, wherein the QoE reconfiguration request or notification is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

8. The apparatus of claim 1, wherein the QoE reconfiguration request or notification further comprises reasoning information for the quality of experience (QoE) reconfiguration request or notification.

9. The apparatus according to claim 1, before sending the QoE reconfiguration request or notification, the one or more processors are further configured to: Receiving a network configuration for configuring QoE reporting for the UE; and performing QoE measurement based on the configured QoE report and reporting the QoE measurement result to the BS, The UE report evaluation is based on the QoE measurement result.

10. The apparatus of claim 1, wherein the QoE reconfiguration request or notification is a QoE reconfiguration request indicating a preference of the UE as to whether the QoE reporting should be suspended, resumed, suspended, or changed.

11. The apparatus according to claim 10, after sending the QoE reconfiguration request or notification, the one or more processors are further configured to: receiving a reconfiguration request response from the BS indicating a rejection or approval of the QoE reconfiguration request, Wherein based on the reconfiguration request response, the QoE report to the BS is suspended, resumed, stopped or changed.

12. The apparatus of claim 11, wherein the one or more processors are further configured to: When sending the QoE reconfiguration request, a timer is started, Wherein, if the UE does not receive the reconfiguration request response before the timer expires, suspending, resuming, stopping or changing the QoE report to the BS.

13. The apparatus of claim 1, wherein the QoE reconfiguration request or notification indicates parameters of a QoE measurement reconfiguration including a reconfiguration of a reporting periodicity, a reporting duration, or a number of QoE reports within a time period.

14. The apparatus of claim 1, wherein the QoE reconfiguration request or notification is a UE notification indicating to the BS that the QoE reporting is to be suspended, resumed, terminated, or changed.

15. A baseband processor for a base station (BS), the baseband processor comprising One or more processors configured to: receiving a quality of experience (QoE) reconfiguration request or notification from a user equipment (UE) based on UE report evaluation; and A request response or notification confirmation is sent to the UE in response to the QoE reconfiguration request or notification.

16. The baseband processor of claim 15, wherein the QoE reconfiguration request or notification indicates UE preferences or capabilities to be reconfigured for QoE measurement reporting.

17. The baseband processor of claim 15, wherein the QoE reconfiguration request or notification is sent by a UE Assistance Information (UAI) message.

18. The baseband processor of claim 15, wherein the QoE reconfiguration request or notification further comprises a QoE measurement configuration for an idle or inactive state.

19. The baseband processor of claim 15, wherein the QoE reconfiguration request or notification is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

20. A method for a user equipment (UE) to trigger reconfiguration for a quality of experience (QoE) measurement report, the method comprising: Perform UE reporting evaluation for QoE measurement reconfiguration; Sending a QoE reconfiguration request or notification to a base station (BS) based on the UE report evaluation; receiving a request response or a notification confirmation from the BS; as well as The QoE reporting to the BS is suspended, resumed, stopped or changed based on the request response or the notification confirmation.

21. An apparatus for a user equipment (UE), the apparatus comprising One or more processors configured to: receiving a quality of experience (QoE) configuration query from a base station (BS) to inquire whether to perform a QoE measurement configuration; and A configuration query response is sent indicating a rejection or approval of the QoE measurement configuration.

22. The apparatus of claim 21, wherein the one or more processors are further configured to: After receiving the QoE configuration query, performing UE report evaluation for the QoE measurement configuration, Wherein the UE reporting evaluation is based on UE status parameters, the UE status parameters comprising at least one or more of a battery level, a mobility level, a memory usage, a buffer status of at least one radio bearer, a channel quality, or an application user setting.

23. The apparatus of claim 21, wherein the one or more processors are further configured to: In case the configuration query response indicates the approval of the QoE measurement configuration, the QoE measurement configuration is received.

24. The apparatus of claim 21, wherein the QoE configuration query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of the QoE measurement configuration.

25. The apparatus of claim 21, wherein the QoE configuration query is specific to one or more service types.

26. The apparatus of claim 21, wherein in a case where the QoE configuration query is rejected by the UE, the configuration query response includes reasoning information indicating a reason for the rejection of the QoE configuration query.

27. The apparatus of claim 21, wherein, in a case where the configuration query response indicates the rejection of the QoE measurement configuration, the configuration query response includes timing information indicating a duration for which the UE will be available for the QoE measurement configuration.

28. An apparatus for a base station (BS), the apparatus comprising One or more processors configured to: sending a user equipment (UE) a QoE report query to inquire whether to restore or change a quality of experience (QoE) report; receiving, from the UE, a report query response indicating a rejection or approval of the QoE report query; as well as The UE is configured to resume or change QoE reporting based on the report query response.

29. The apparatus of claim 28, wherein the QoE report query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

30. The apparatus of claim 28, wherein the QoE reporting query is specific to one or more service types.

31. The apparatus of claim 28, wherein in a case where the QoE report query is rejected by the UE, the report query response includes reasoning information indicating a reason for the rejection of the QoE report query.

32. The apparatus of claim 28, wherein in a case where the QoE report query is rejected by the UE, the report query response includes timing information indicating a duration for which the UE will be able to use the resumption or change of the QoE reporting.

33. An apparatus for a user equipment (UE), the apparatus comprising One or more processors configured to: receiving a quality of experience (QoE) report query from a base station (BS) to inquire whether to restore or change a QoE report; sending a report query response indicating a rejection or approval of the QoE report query; as well as The QoE report is restored or changed based on the report query response.

34. The apparatus of claim 33, wherein the report query response is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

35. The apparatus of claim 33, wherein the report query response is specific to one or more service types.

36. The apparatus of claim 33, wherein in a case where the QoE report query is rejected by the UE, the report query response includes reasoning information indicating a reason for the rejection of the QoE report query.

37. The apparatus of claim 33, wherein in a case where the QoE report query is rejected by the UE, the report query response includes timing information indicating a duration for which the UE will be able to use the resumption or change of the QoE reporting.

38. The apparatus of claim 33, after sending the report query response, the one or more processors are further configured to receive a QoE measurement reconfiguration from the BS based on the report query response to configure the restoration or change of the QoE report.

39. The apparatus of claim 33, wherein the QoE report query is specific to one or more QoE configuration identifiers from a set of QoE configuration identifiers, wherein each QoE configuration identifier in the set of QoE configuration identifiers represents a parameter of a QoE measurement configuration.

40. The apparatus of claim 33, wherein the QoE reporting query is specific to one or more service types.

Images