Method, apparatus and computer program

Abstract

The invention relates to a method, a device and computer equipment. The present disclosure provides a user device comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the user device to perform: receiving a second to change at least one metric related to Quality of Experience (QoE) from an application function, wherein the second request is directed to a session established between the user equipment and the application function; sending, based on the request, a third to modify the session to the application function, where the third request indicates a change in at least one metric related to QoE; and receiving data for the session from the application function based on a change in the at least one metric related to QoE, where the received data is associated with the degraded QoE metric as compared to previously received data for the session prior to the change.

Description

Technical Field

[0001] The various examples disclosed relate to methods, apparatuses, and computer programs. In particular, they relate to methods, apparatuses, and computer programs for communication networks. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices can be provided with services through application servers.

[0003] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of such a standard is the so-called 5G (fifth generation) standard provided by 3GPP. Summary of the Invention

[0004] Some embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to be used to limit its scope. In view of this disclosure, other features, aspects, and elements will be apparent to those skilled in the art. For example, it should be understood that additional aspects may be provided by any combination of two or more of the following aspects.

[0005] According to a first aspect, a user equipment is provided, the user equipment comprising: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to: receive from an application function a second request for changing at least one metric related to Quality of Experience (QoE), wherein the second request is for a session established between the user equipment and the application function; based on the request, send to the application function a third request for modifying the session, wherein the third request indicates a change in at least one metric related to QoE; and based on the change in at least one metric related to QoE, receive from the application function data for the session, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0006] According to a second aspect, a user equipment is provided, the user equipment comprising: components for receiving from an application function a second request for changing at least one metric related to quality of experience (QoE), wherein the second request is for a session established between the user equipment and the application function; components for sending to the application function a third request based on the request for modifying the session, wherein the third request indicates a change in at least one metric related to QoE; and components for receiving from the application function data for the session based on the change in at least one metric related to QoE, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0007] According to a third aspect, a method performed by a user device is provided, the method comprising: receiving from an application function a second request for changing at least one metric related to quality of experience (QoE), wherein the second request is for a session established between the user device and the application function; based on the request, sending to the application function a third request for modifying the session, wherein the third request indicates a change in at least one metric related to QoE; and based on the change in at least one metric related to QoE, receiving from the application function data for the session, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0008] According to a fourth aspect, a user equipment is provided, including a circuit system configured to perform: receiving from an application function a second request to change at least one metric related to quality of experience (QoE), wherein the second request is for a session established between the user equipment and the application function; based on the request, sending to the application function a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; and based on the change in at least one metric related to QoE, receiving from the application function data for the session, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0009] According to a fifth aspect, a computer program is provided, the computer program including instructions that, when executed by a user device, cause the user device to perform at least the following: receiving from an application function a second request to change at least one metric related to Quality of Experience (QoE), wherein the second request is for a session established between the user device and the application function; based on the request, sending to the application function a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; and based on the change in at least one metric related to QoE, receiving from the application function data for the session, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0010] The following applies to each of the first through fifth aspects above (e.g., one or more, including all).

[0011] In some examples, changes in at least one metric related to QoE include changes in at least one value associated with at least one metric related to QoE.

[0012] In some examples, a second request to change at least one metric related to QoE is associated with a request to downgrade the QoE metric used for that session.

[0013] In some examples, at least one metric associated with QoE includes at least one of the following: a metric for QoE, or a metric for QoS.

[0014] In some examples, receiving data for the session includes: buffering data for the session based on a change in at least one metric related to QoE; and providing the buffered data for the session to the user device's application based on that change in at least one metric related to QoE.

[0015] In some examples, the user equipment is also made to: receive a fourth request from the application function for information related to the QoE of the session established at the user equipment; and send information associated with at least one metric related to the QoE of the session to the application function.

[0016] In some examples, the user equipment is also made to perform: based on a fourth request for information related to the QoE used in the session, to perform a measurement related to the QoE used in the session, in order to determine information associated with at least one metric also used in the QoE used in the session.

[0017] In some examples, the user equipment is also instructed to: determine whether to accept a second request based on the buffer capacity level associated with the session.

[0018] The sending of this additional request is based on this determination.

[0019] In some examples, the user equipment is also made to: output an indication to the user of the user equipment for an input based on a second request, wherein the input is an indication to accept a request to change at least one metric related to QoE, or to reject a request to change at least one metric related to QoE; wherein the sending of the additional request is based on the input.

[0020] In some examples, the user equipment is also made to perform: receive an indication of an incentive provided to the user equipment by the network from the application function, wherein the incentive is associated with a third request indicating a change in at least one metric related to the QoE for the session.

[0021] In some examples, the session includes one of the following: a session for extended reality, a session for augmented reality, or an Internet Protocol Multimedia Subsystem session.

[0022] According to a sixth aspect, an apparatus for an application function is provided, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the application function to perform: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to Quality of Experience (QoE), wherein the first request is for a session established between a user device and the application function; sending a second request to the user device to change the at least one metric related to QoE, wherein the second request is for a session established between the user device and the application function; receiving a third request from the user device to modify the session, wherein the third request indicates a change in the at least one metric related to QoE; modifying the session based on the change in the at least one metric related to QoE according to the third request; and sending data for the session to the user device based on the change in the at least one metric related to QoE, wherein the sent data is associated with a degraded QoE metric compared to previously sent data for the session before the change.

[0023] According to a seventh aspect, an apparatus for an application function is provided, the apparatus including components for the application function to perform the following: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to Quality of Experience (QoE), wherein the first request is for a session established between a user equipment and the application function; sending a second request to the user equipment to change at least one metric related to QoE, wherein the second request is for a session established between the user equipment and the application function; receiving from the user equipment a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; modifying the session based on the change in at least one metric related to QoE according to the third request; and sending data for the session to the user equipment based on the change in at least one metric related to QoE, wherein the sent data is associated with a degraded QoE metric compared to previously sent data for the session before the change.

[0024] According to an eighth aspect, a method performed by an application function is provided, the method comprising: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to Quality of Experience (QoE), wherein the first request is for a session established between a user device and the application function; sending a second request to the user device to change at least one metric related to QoE, wherein the second request is for a session established between the user device and the application function; receiving from the user device a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; modifying the session based on the change in at least one metric related to QoE according to the third request; and sending data for the session to the user device based on the change in at least one metric related to QoE, wherein the sent data is associated with a degraded QoE metric compared to previously sent data for the session prior to the change.

[0025] According to a ninth aspect, an apparatus for an application function is provided, wherein the apparatus includes a circuit system configured to perform: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to Quality of Experience (QoE), wherein the first request is for a session established between a user equipment and the application function; sending a second request to the user equipment to change at least one metric related to QoE, wherein the second request is for a session established between the user equipment and the application function; receiving from the user equipment a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; modifying the session based on the change in at least one metric related to QoE according to the third request; and sending data for the session to the user equipment based on the change in at least one metric related to QoE, wherein the sent data is associated with a degraded QoE metric compared to previously sent data for the session before the change.

[0026] According to a tenth aspect, a computer program is provided, the computer program including instructions that, when executed by a user equipment, cause an application function to perform at least the following: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to Quality of Experience (QoE), wherein the first request is for a session established between the user equipment and the application function; sending a second request to the user equipment to change at least one metric related to QoE, wherein the second request is for a session established between the user equipment and the application function; receiving from the user equipment a third request to modify the session, wherein the third request indicates a change in at least one metric related to QoE; modifying the session based on the change in at least one metric related to QoE according to the third request; and sending data for the session to the user equipment based on the change in at least one metric related to QoE, wherein the sent data is associated with a degraded QoE metric compared to previously sent data for the session before the change.

[0027] The following applies to each of the above-mentioned aspects 6 through 10 (e.g., one or more, including all).

[0028] In some examples, the first request includes at least one of the following: triggering a power-saving mode for an application function, a range of values ​​for at least one metric related to QoE, information related to service experience, information about user devices, information about multiple user devices, a timer related to the first request, or an expiration timer for the first request.

[0029] In some examples, the first request is received from a core network entity or application provider.

[0030] In some examples, the changes in at least one metric related to QoE indicated in the third request include: changes in at least one value associated with at least one metric related to QoE.

[0031] In some examples, a second request to change at least one metric related to QoE is associated with a request to downgrade the QoE metric used for that session.

[0032] In some examples, at least one metric associated with QoE includes at least one of the following: a metric for QoE, or a metric for QoS.

[0033] In some examples, sending data for the session includes: buffering data for the session based on changes in at least one metric related to QoE; and sending data for the already buffered session to the user equipment based on changes in at least one metric related to QoE.

[0034] In some examples, the device is also made to: send a fourth request to the user equipment for information related to the quality of experience of a session established at the user equipment; and receive from the user equipment information associated with at least one metric related to the QoE also used for the session.

[0035] In some examples, the apparatus is also made to perform: receiving an indication of an incentive provided by the network to the user equipment, wherein the incentive is associated with a third request indicating a change in at least one metric related to QoE for the session; and sending an indication of an incentive to the user equipment.

[0036] In some examples, the session includes one of the following: a session for extended reality, a session for augmented reality, or an Internet Protocol Multimedia Subsystem session.

[0037] According to the eleventh aspect, an apparatus for a core network is provided, wherein the apparatus includes: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the core network to perform: providing an energy-saving related first request to an application function, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between a user equipment and the application function.

[0038] According to the twelfth aspect, an apparatus for a core network is provided, the apparatus including components for the core network to perform the following: providing an energy-saving related first request to an application function, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between a user equipment and the application function.

[0039] According to the thirteenth aspect, a method performed by a core network is provided, the method comprising: providing an application function with a first request related to energy saving, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between a user equipment and the application function.

[0040] According to the fourteenth aspect, an apparatus for a core network is provided, wherein the apparatus includes a circuit system configured to perform: providing an energy-saving related first request to an application function, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between a user equipment and the application function.

[0041] According to the fifteenth aspect, a computer program is provided, the computer program including instructions that, when executed by a user equipment, cause the core network to at least: provide an energy-saving related first request to an application function, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between the user equipment and the application function.

[0042] The following applies to each of the above aspects eleven through fifteen (e.g., one or more, including all).

[0043] In some examples, the first request includes at least one of the following: triggering a power-saving mode for an application function, a range of values ​​for at least one metric related to QoE, information related to service experience, information about user devices, information about multiple user devices, a timer related to the first request, or an expiration timer for the first request.

[0044] In some examples, this first request is provided to the application functionality through the application layer.

[0045] In some examples, the device is also made to perform: provide the application function with an indication of an incentive provided by the network to the user equipment, wherein the incentive is associated with a change in at least one metric related to the QoE used for the session.

[0046] In some examples, the device is also made to perform: storing authorizations related to the degradation of QoE metrics for user devices at a unified data management office, wherein the authorizations are stored in subscription data associated with the user devices.

[0047] In some examples, the application is also enabled to perform: selecting user devices from multiple user devices for application degradation against QoE metrics via session management features.

[0048] In some examples, the device is also configured to perform: through the session management function, to provide a request for information regarding the service experience at the user equipment to the network analytics data function.

[0049] In some examples, the device is also made to perform: respond to a request for information about the service experience at the user equipment by providing a network analytics data function to a session management function, wherein the request includes: at least one metric for the user equipment that is predicted to be related to QoE.

[0050] In some examples, the device is also made to perform: communicate with unified data management via session management functions to determine whether subscription data associated with a user device has an indication of authorization for a degradation of QoE metrics, wherein the first request is sent to the application function based on the communication.

[0051] A computer product stored on a medium can enable the device to perform the methods described herein.

[0052] A non-transitory computer-readable medium includes program instructions that, when executed by a device, cause the device to perform the methods described herein.

[0053] An electronic device may include the apparatus described herein.

[0054] Various other aspects and additional embodiments are described in the following detailed description and the appended claims.

[0055] The subject matter of the independent claims is provided for certain aspects. Other aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims should be interpreted as examples that aid in understanding this disclosure.

[0056] List of abbreviations: AF: Application Functions AMF: Access and Mobility Management Function AN: Access Network AP: Application Provider AR: Augmented Reality AS: Application Server BS: Base Station CN: Core Network DL: Downlink eNB: eNodeB gNB: gNodeB HMD: Head-mounted display IIoT: Industrial Internet of Things LTE: Long Term Evolution MAF: Media Access Function MS: Mobile Site MSH: Media Session Handler NEF: Network Exposure Function NG-RAN: Next Generation Radio Access Network NF: Network Functions NR: New Radio NRF: Network Repository Functionality NW: Network NWDAF: Network Data Analysis Function PCF: Policy Control Function PLMN: Public Land Mobile Network QoE: Quality of Experience QoS: Quality of Service RAN: Radio Access Network RF: Radio Frequency SMF: Session Management Function UE: User Equipment UDR: Unified Data Repository UDM: Unified Data Management UL: Uplink UPF: User-Face Functionality XR: Extended Reality 3GPP: Third Generation Partnership Project 5G: Fifth Generation 5GC: 5G Core Network 5G-AN: 5G Radio Access Network 5GS: 5G system 5QI: 5G QoS Identifier Attached Figure Description

[0057] Some embodiments will now be described by way of illustrative and limiting example only with reference to the accompanying drawings, in which:

[0058] Figure 1 This diagram illustrates a 5G communication system.

[0059] Figure 2 It shows the use of Figure 1 A schematic representation of a 5G communication system device;

[0060] Figure 3 A schematic representation of the communication equipment is shown;

[0061] Figure 4A schematic representation of the architecture for an extended reality (XR) baseline client capable of supporting experience quality degradation is shown;

[0062] Figure 5 An example block diagram representation of a management system for buffer control is shown;

[0063] Figure 6 A schematic representation of a system with media access capabilities for augmented reality to support session control and buffer control is shown.

[0064] Figure 7 Example signaling and operation diagrams for experience quality degradation between user equipment and network entities in XR sessions are shown;

[0065] Figure 8 Example signaling and operations between network entities related to the triggering of the energy-saving process are shown;

[0066] Figure 9 Another example signaling and operation diagram between user equipment and network entities is shown for experience quality degradation in XR sessions;

[0067] Figure 10 A flowchart of an example method executed by the device is shown;

[0068] Figure 11 A flowchart of another example method performed by the device is shown;

[0069] Figure 12 A flowchart of another example method executed by the device is shown; and

[0070] Figure 13 A schematic representation of the device is shown. Detailed Implementation

[0071] Quality of Service (QoS) is generally a measure of the overall performance of a service experienced by users of a network. Some examples of QoS metrics or parameters include packet loss rate, bit rate, throughput, transmission delay, availability, and jitter. QoS requirements are related to technical constraints that must be met, such as performance-related issues, reliability issues, and availability issues. A characteristic of 5G communication systems is the ability to differentiate and manage traffic flows or sessions with different QoS requirements.

[0072] Quality of Experience (QoE) is a measure of how satisfied users are with digital services, such as communication sessions. For example, the QoE of a 5G communication session can provide a measure of user satisfaction with the session and the overall level of the experience.

[0073] QoE can be seen as a “high level” indicator of the performance and quality of the service provided from the user’s perspective, while QoS provides a more detailed understanding of the parameters related to the performance of the service.

[0074] Mobile network operators seek to minimize energy consumption, for example, for cost and / or environmental reasons. Network energy-saving techniques attempt to optimize energy consumption with or without QoS degradation. Sometimes, the network may identify additional energy-saving opportunities, but at the cost of QoS degradation. The actions taken by the network to save energy may target one or more UEs. In some cases, when a UE generates high energy consumption at the base station due to its location / radio conditions and / or high traffic, that UE may be identified by the network as a potential candidate to provide incentives for service performance adjustments, which can reduce such energy consumption from the network's perspective. An associated issue is that it is unclear what trade-offs between energy saving and service adjustments (such as QoS degradation) are acceptable (e.g., tolerable by applications / users). Different types of behavior are envisioned, including: completely intolerant of any QoS degradation, or tolerating some QoS degradation based on QoS policies.

[0075] Tolerance for QoS degradation can vary depending on current UE / user activity, especially based on a specific application / service. QoS degradation can take the form of variations in the 5G QoS Identifier (5QI) to accommodate more lenient Key Performance Indicators (KPIs), for example, especially when using Guaranteed Bit Rate (GBR) for conversational or streaming video services. However, there may be limitations on tolerable QoS degradation, even under degraded conditions, that still satisfy existing policy rules or operator policies for the service. This use case may not be suitable for "best-effort" services because the network will not be able to evaluate alternative configurations of QoS attributes.

[0076] In examples related to 5G networks, the network may perform actions that degrade service performance to conserve energy, considering the following: service performance characteristics resulting from the energy-saving action (e.g., reduced / increased bit rate, latency, 5QI), QoS policies associated with the affected service, incentives (e.g., reduced energy credit consumption rate, reward credits), or future dynamic adjustments to the provided communication services (e.g., temporary improvement of QoS or service performance), and applicable conditions (which may be (semi-)permanent or restricted, e.g., applicable network slices, time or region, application / service aspects). Such conditions can also refer to explicit actions from the UE and / or user (e.g., moving to another location, minimum duration of stay at a given location). Before applying energy-saving actions, the network may examine its tolerance for associated service performance degradation for services with QoS standards. However, it is unclear how user tolerance for reduced QoS and QoE can be determined, and how the UE / network can determine an appropriate strategy for reduced QoS that minimizes the overall reduction in QoE at the UE.

[0077] Furthermore, in many current systems, regardless of the network subscription fees paid by the user (e.g., for 4G Wi-Fi, 5G Wi-Fi, etc.), the network can reduce a user's QoE (e.g., to save energy, bandwidth, or restrict user activity) without the user's consent. Typically, the user is completely unaware of this. If the user or UE wants to adjust (modify / change / alter / improve) the QoE, they must do so manually. Therefore, the user's user experience and / or service experience can be degraded due to the network without the user's knowledge.

[0078] One or more of the following examples are designed to address one or more of the issues identified above.

[0079] For example, there exists a user equipment (UE) configured to receive from an application function (AF) a request to change at least one metric related to Quality of Experience (QoE), wherein the request for change is used for a session established between the UE and the application function. Based on the request, the UE sends a request to the AF to modify the session, wherein the request for modification indicates a change in at least one metric related to QoE. Then, based on the change in at least one metric related to QoE, the UE receives data from the AF for the session, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0080] This example will be combined below. Figures 4 to 13 It was described in more detail.

[0081] Before explaining the above examples in more detail, here are some example communication devices that can establish communication sessions with a network (such as...). Figure 3 (As shown in the image) is described. Communication equipment is a part of a communication system (such as...). Figure 1 (As shown in the image). Communication equipment can be transmitted via devices (such as...) Figure 2 (as shown) and one or more entities in the communication system (such as) Figure 1 (As shown in the diagram) communication device, which may be part of or included in a base station. As described above, the base station and the communication device can communicate with each other, enabling the communication device to receive data from the network for a communication session.

[0082] Certain general aspects of communication systems and equipment will be referenced Figures 1 to 3 The explanation is brief to aid in understanding the technology upon which the examples are based.

[0083] Figure 1 A schematic representation of a 5G communication system 100 is shown. The wireless communication system 100 includes one or more communication devices 102, such as user equipment (UE) or terminals. The wireless communication system 100 includes a 5G system (5GS). The 5GS includes a 5G radio access network (5G-RAN) 106, a 5G core network (5GC) 104 including one or more network functions (NFs), one or more application functions (AFs) 108, and one or more data networks (DNs) 110. The one or more DNs 110 may include one or more application servers (ASs) (not shown).

[0084] The 5G-RAN 106 may include one or more gNodeB (gNB) distributed unit (DU) functions connected to one or more gNodeB (gNB) centralized unit (CU) functions.

[0085] 5GC 104 includes Access and Mobility Management Functions (AMF) 112, Session Management Functions (SMF) 114, Authentication Server Functions (AUSF) 116, User Data Management Functions (UDM) 118, User Plane Functions (UPF) 120, Network Exposure Functions (NEF) 122, and / or other NFs. Some examples as shown below may apply to the 3GPP 5G standard. However, some examples may also apply to Advanced 5G, 4G, 3G, and other 3GPP standards.

[0086] In wireless communication system 100 (such as Figure 1In the diagram, communication device 102 (such as, for example, a terminal, user equipment, user equipment (UE), and / or machine-type communication device) is provided with wireless access via at least one base station or similar wireless transmitting and / or receiving node or point. Communication device 102 is provided with suitable signal receiving and transmitting means for enabling communication, for example, enabling access to a communication network or direct communication with other devices. Communication device 102 can access a carrier provided by the base station or access point and transmit and / or receive communication on that carrier.

[0087] Figure 2 An example of device 200 is shown. Device 200 can be used for Figure 1 The 5G communication system. Device 200 can be used to control one or more network entities and / or network functions, such as... Figure 1 The above describes the entity of 5G-RAN or 5GC. Device 200 includes at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 is coupled to RAM 211a and ROM 211b. At least one processor 212, 213 can be configured to execute appropriate software code 215. For example, the software code 215 can allow the execution of one or more steps to perform one or more of the aspects or examples herein. The software code 215 can be stored in ROM 211b. Device 200 can interconnect with another device 200 that controls another entity / function of 5G-AN or 5GC. In some examples, device 200 can be configured to provide one or more functions of 5G-AN or 5GC. For example, device 200 can be configured to perform at least some of the specific functions of 5G-AN or 5GC. For example, device 200 can be configured to operate as a specific function of 5G-AN or 5GC. In alternative examples, device 200 may be configured to perform at least some of the functions of two or more of 5G-AN and / or 5GC. For example, device 200 may be configured to operate as two or more functions of 5G-AN and / or 5GC. Device 200 may include one or more circuits, or a circuit system (not shown) that may be configured to perform one or more of the functions in this aspect or example.

[0088] Figure 3 An example of a communication device 300 is shown. The communication device 300 can be similar to... Figure 1The communication device 102 shown is illustrated. Communication device 300 can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples of communication device 300 include user equipment, terminals, mobile stations (MS) or mobile devices (such as mobile phones or so-called "smartphones"), HMDs (head-mounted displays), smart glasses (augmented reality (AR), virtual reality (VR), or extended reality (XR) devices), computers provided with wireless interface cards or other wireless interface facilities (e.g., USB dongles), personal data assistants (PDAs) or tablets provided with wireless communication capabilities, machine-type communication (MTC) devices, cellular Internet of Things (CIoT) devices, or land / sea / air vehicles (such as cars, trucks, ships, airplanes, or drones), or any combination thereof. Communication device 300 can provide, for example, data communication for carrying communication. Communication can be one or more of voice, email, text messaging, multimedia, data, machine data, etc.

[0089] The communication device 300 can receive signals via air or radio interface 307 via suitable means for receiving, and can transmit signals via suitable means for transmitting radio signals. Figure 3 In the diagram, the transceiver device is schematically represented by box 306. The transceiver device 306 may be provided, for example, by a radio component and an associated antenna arrangement. The antenna arrangement may be located inside or outside the mobile device.

[0090] The communication device 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for use in performing tasks designed to be performed with software and hardware assistance, including access to access systems and other communication devices, and control of communication with access systems and other communication devices. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute appropriate software code 308. For example, software code 308 may allow execution of one or more of the aspects described herein. Software code 308 may be stored in ROM 302a. The communication device 300 may include one or more circuits, or a circuit system (not shown) that may be configured to execute one or more of the aspects described herein or in the examples.

[0091] Processors, memory, and other related control devices may be provided on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The communication device may optionally have a user interface, such as a keyboard 305, a touchscreen or touchpad, a combination thereof, etc. Optionally, one or more displays, one or more speakers, and one or more microphones in the display may be provided, depending on the type of device.

[0092] It should be understood that although many examples are described about 5G, they are equally applicable to 6G and other future standards.

[0093] Mobile networks can prioritize energy efficiency within the network or at the UE. Energy-saving technologies aim to optimize energy consumption while minimizing trade-offs. To identify potential energy-saving opportunities, the network can target specific UEs that consume excessive energy and offer incentives to reduce energy consumption in exchange for service adjustments. The network should assess whether the target UE will accept the proposed service adjustments that may cause QoS degradation. Not all users are willing to tolerate such changes, especially when current services or content received at a particular time or location are sensitive to performance degradation. If the user / UE agrees to the service adjustments, the UE and network can explore potential mitigation strategies to minimize the impact on service experience and QoE.

[0094] If users are incentivized, such as by billing-related or service-related incentives, they may be more tolerant of QoS / QoE degradation. Generally, networks should track evidence of energy efficiency at the cost of QoS degradation to avoid minimizing QoS performance without any compensation at the UE / user level.

[0095] In this context, a degradation of a QoS or QoE metric is considered a deterioration of QoS or QoE. For example, video resolution can be an example of a QoE metric. A degradation of video resolution is a reduction in video resolution (e.g., from 1080p to 720p). Similarly, jitter can be an example of a QoS metric. A degradation of jitter is an increase in jitter. QoS and QoE can be correlated with each other.

[0096] In some examples, a QoS metric can be converted to a (associated) QoE metric, as will be described in detail below. In this way, in some examples, a "QoE-related metric" can be a "QoE metric." In other examples, a "QoE-related metric" can be a "QoS metric."

[0097] In some examples, a (communication) session exists between the UE and the network. Depending on the type of session or the data sent / received for that session, the session can be considered a "high-energy" session. For example, the session could be an XR session (e.g., an AR session) or a VR session. Due to the characteristics of the media data sent to the UE for an XR session, the XR session can result in high power consumption at the base station. It should be understood that an XR session is merely an example of session types. The following examples apply to any type of communication session that can be established at the UE. Example architectures for XR-related examples are provided in... Figure 4 It is depicted in the middle.

[0098] Figure 4 A schematic representation of an architecture for an extended reality (XR) baseline client capable of supporting experience quality degradation is shown.

[0099] The XR baseline client 400 includes: a runtime for XR (referred to herein as "XR runtime" 401), an application for XR (referred to herein as "XR application" 403), source management for XR (referred to herein as "XR source management" 405), a rendering engine 407, a scene manager 409, a media session handler 411, media access functionality 413, and an interface 415 to a 5G system. The XR runtime 401 includes: runtime functions (such as tracking and real-time localization and mapping (SLAM)), compositing functions, and an audio subsystem. The XR runtime 401 receives input from devices (such as sensors, microphones, and cameras). The XR runtime 401 provides output to devices (such as actuators, displays, and speakers).

[0100] The XR runtime 401 interfaces with the XR application 403, the XR source management 405, and the rendering engine 407. The rendering engine 407 includes a visual renderer and an audio renderer. The rendering engine 407 also interfaces with the scene manager 409. The scene manager 409 also interfaces with the XR application 403 and the media access function 413.

[0101] Media access function 413 includes: content delivery protocol, metadata format, video codec, audio codec, and buffer control 417. Buffer control 417 will be described in more detail below. Media access function 413 also has interfaces with XR source management 405, XR application 403, media session handler 411, and 5G system 415.

[0102] The media session handler 411 includes session control 419. Session control 419 will be described in more detail below.

[0103] In some examples, a method is provided whereby the Application Function (AF) assesses QoS degradation and notifies the UE of QoS or QoE degradation due to network or UE power saving. This enables the UE to proactively adjust QoS or QoE metrics to minimize the impact on user experience.

[0104] Energy-saving triggers may occur where a request or notification is provided to the AF. Authorized entities (such as the 5G core network (5GC) or application provider (AP)) may request (or notify) the AF to request the UE to change a metric related to QoE for establishing a session (referred to herein as a "QoE metric"). A change to the QoE metric can be considered a reduction in QoE (in order to save energy). This may be triggered by energy-saving incentives from the network or the UE. For example, the 5GS may determine a reduction in QoS and trigger energy saving through the AF and the proposed QoS or QoE metric (or a range of the metric). An AP that has a contract with a cloud provider or 5GS may initiate energy saving to the AF. Another example is that an AP with a green media streaming contract with the UE may trigger energy saving due to the energy status of cloud and 5GS resources. For example, energy saving may be triggered if / when the 5GS and / or RAN nodes consume more non-renewable energy (e.g., energy generated through the use of coal, natural gas, and / or oil). In some embodiments, an energy-saving mode may be triggered if / when the percentage of non-renewable energy in the total energy exceeds a threshold, and / or if / when the percentage of renewable / green energy in the total energy is below / not above another threshold.

[0105] There may be an assessment of UE tolerance for QoE degradation. When the AF receives a request (or notification) for energy saving, the AF assesses its potential impact on the UE's (or the UE's users') QoE. By comparing the QoS metric or QoE metric to be included in the request with at least one threshold, the AF can determine the acceptable level of QoE degradation. For example, to save energy, the AP determines to limit the video resolution (an example of a QoE metric) of individual users to 720p. If there are users watching 4K or 8K resolution video, the QoE metric for those users' resolutions will be compared with the 720p threshold. After the comparison, users (e.g., those watching 4K or 8K) will be requested to reduce their resolution to 720p. When a request from the 5GC or AP includes a QoS metric (or a range of QoS metrics) rather than a QoE metric, the AF can request a core network function (e.g., Network Data Analysis Function (NWDAF)) to convert the QoS metric into a QoE metric. In this way, the core network function estimates the QoE impact at the UE. The AF can examine subscription information regarding the UE used for an agreed-upon QoE level or QoE metric. If the information regarding the UE's subscription indicates that the estimated / requested QoE degradation is aligned with the agreed-upon QoE level or QoE metric, then approval from the UE / user for that degradation may not be required. Even without approval, UE / user feedback can still be collected by the AF. In examples where the information regarding the UE's subscription does not indicate that the estimated / requested QoE degradation is aligned with the agreed-upon QoE level or QoE metric, the AF may request UE / user approval, explaining the potential QoE impact or indicating the QoE metric.

[0106] At the UE, there can be control over QoE. Based on a request for QoE degradation received from the AF, the UE assesses the current state of the QoE and determines how to respond to the AF. The UE's goal is to minimize the impact on its service experience. To achieve this, two new submodules are provided. These two submodules can be provided within the UE's client architecture, such as, for example, within an XR baseline client architecture (e.g., within the XR baseline client architecture of 3GPP TS 26.119). The function of these two submodules is to allow the UE to determine whether its applications can tolerate degradation in its current QoE. When degradation is tolerated, the UE determines how the application can manage the current QoE without unacceptable degradation. These two submodules can be referred to as "session control" and "buffer control," which... Figure 4 It is shown in the middle. For example... Figure 4As depicted, the “Session Control” 419 submodule resides within the Media Session Handler (MSH) module 411. In this context, the Media Session Handler 411 is referred to as a “module,” and therefore, Session Control 419, as part of the Media Session Handler 411, is referred to as a “submodule.” Session Control 419 is a logical entity that includes specific functions related to and thus control (e.g., change or modify) the QoE of a particular UE. Session Control 419 may be a separate submodule (sub-logical entity) within the Media Session Handler 411. Alternatively, Session Control 419 may also be directly integrated into the Media Session Handler 411 module as another function. It should be understood that the Media Session Handler 411 module is responsible for receiving reported QoE from the user / UE, directly or via another logical entity within it (e.g., Session Control submodule 419).

[0107] Since XR application 403 is exposed to MSH 411 via the IF-6 interface, MSH 411 possesses knowledge about each application. This, in turn, allows session control 419 to understand each (XR) application. The session control 419 submodule allows the UE to control (or change, or modify) the QoE metrics of currently established applications. Session control 419 can be configured to measure the service experience at the UE and then determine, based on that service experience, which QoE metrics at the UE can be changed. In this way, the UE is able to estimate its service experience and adjust QoE metrics to minimize the impact of performance degradation. QoE metrics can be associated with QoS metrics.

[0108] Service experience can be defined as QoE related to a specific application or service. For example, QoE for a video stream might be related to pixels or resolution, while QoE for an audio stream would be different. An application might have relatively "good" audio quality (HQ resolution) provided by the AP (i.e., good QoE for audio), but might have relatively "poor" video quality (i.e., poor QoE for video resolution). Therefore, the service experience for video streams and audio streams might differ.

[0109] For example, in the context of a media session (e.g., an XR session), some examples of QoS metrics include: packet loss rate, bandwidth (throughput), jitter, latency, out-of-order delivery, and errors (noise, interference). One or more of these QoS metrics are associated with QoE metrics for video quality. Video quality as a QoE metric (i.e., the quality of the video) can be indicated by one or more of the following KPIs: frame rate fluctuation, spatial information loss (blurring), and latency.

[0110] For Dynamic Adaptive Streaming (DASH) over HTTP, some examples of QoE metrics include: a list representing switching events, average throughput, initial playback latency, buffer level, playlist, Media Rendering (MPD) information, playback latency for media startup, and device information. For Virtual Reality (VR), some examples of QoE metrics include: DASH-based QoE degradation metrics, comparable quality viewport switching latency, rendering viewport, and VR device information. For IP Multimedia Subsystem Multimedia Telephony Service (MTSI), some examples of QoE metrics include: corruption duration, continuous loss of Real-Time Transport Protocol (RTP) packets, frame rate, jitter duration, synchronization loss duration, round-trip time (RTT), average codec rate, codec information, and call setup time. For RAN-visible QoE (configurable for DASH and VR), some examples of QoE metrics include: application layer buffer level and playback latency for media startup. It should be understood that these are given only as examples.

[0111] The second of the two submodules in the XR baseline client is the "Buffer Control" submodule, such as... Figure 4 As described in [the text]. Figure 4 As shown, buffer control 417 is a logical function within the Media Access Function 413 module. Buffer control 417 is configured for buffer management. Based on requests from the Session Control 419 submodule, buffer control 417 controls the data streams (e.g., audio, video, haptic, etc.) entering and / or leaving the MSH 411. Buffer control 417 is a submodule within the Media Access Function 413. It can be directly integrated into the Media Access Function 413 module, or it can exist as a separate submodule with Media Access Function 413. It should be noted that the Media Access Function module is responsible for buffer management to allow for compensation of degradations in QoE, directly or via another logical entity existing within it, such as the "Buffer Control" submodule. Figure 5 A more detailed description Figure 4 An example representation of the buffer control 417 submodule, where buffer control 417 is implemented to buffer the video stream.

[0112] Figure 5 An example block diagram representation of a management system for buffer control is shown. Figure 5 In the example, buffer control is implemented for video streaming applications, causing the RTP payload to be input to the buffer control. It should be understood that this is just an example and can be extended to other types of applications, such as audio, haptic, etc.

[0113] The submodule 501, named "Buffer Control," is in Figure 5The buffer control 501 is described as receiving input 501 of the RTP payload and sending buffered output 503. Based on the input of the (video) stream's RTP payload and instructions received from an external entity 505 (e.g., a session control submodule), the buffer control 501 is able to adapt flexibly to different network conditions and utilizes QoE as an influencing factor in this adaptation process.

[0114] Input 501 of buffer control 501 is provided to network analyzer 507 and buffer 509. Buffer 509 is an area of ​​memory used to (temporarily) store data as it is moved from one location to another. Feedback loops may exist on the inputs and outputs of the buffer to compensate for jitter; this is referred to as jitter buffer delay 517. Network analyzer 507 is connected to adaptive control logic 511. Network analyzer 507 can provide receive status to adaptive control logic 511. Receive status outputs the unbuffered incoming RTP payload to adaptive control logic. Adaptive control logic 511 receives instructions from external entity 505 and also communicates with buffer 509. Buffer 509 can provide adaptive control logic 511 with its status. For example, this status may include the amount of data available for storage in buffer 509.

[0115] The adaptive control logic 511 outputs a scaling request and a scaling window to the video processing unit 513 of the buffer control 501. The scaling request and scaling window instruct the video processing unit to determine how the buffered video should be processed before being output. For example, this may include how long the video should be buffered.

[0116] A frame of video data is provided from buffer 509 to video buffer management unit 515 of buffer control 501. Video buffer management unit 515 processes the received frame and outputs the buffered video to video processing unit 513. Video processing unit 513 provides buffered video output 503 based on scaling request, scaling window, and buffered video.

[0117] like Figure 5 As described above, the Buffer Control 501 submodule is a logical entity that allows incoming / outgoing streams to be buffered to compensate for degradation in QoE. It should be understood that "Session Control" and "Buffer Control" are given only as examples. In other examples, any suitable name or label may be used for these submodules.

[0118] Figure 6 A schematic representation of a system with augmented reality media access capabilities to support session control and buffer control is shown.

[0119] For example Figure 6The example AR session depicted includes an AR runtime 601, an AR scene manager 603, a media access function 605, and a media session handler 607. The media session handler 607 includes session control 613. The functionality of session control 613 is similar to the previously described session control (e.g., ...). Figure 4 The session control is the same as that described previously. Media access function 605 includes buffer control 615. The function of buffer control 615 is the same as that of the previously described buffer control (e.g., ...). Figure 4 The buffer control is the same as in [the previous text].

[0120] Both the media access function 605 and the media session handler 607 have an interface (Uu) 617 with the 5G system.

[0121] exist Figure 6 In the example, the signaling flow is divided into uplink 609 and downlink 611 to aid understanding.

[0122] In AR runtime 601, input is received from external sources such as microphones, sensors, and cameras. This input is provided to the XR / AR spatial computing module. The output from the XR / AR spatial computing module is passed to the XR / AR spatial description contribution module in media access function 605. Furthermore, input data is also provided to media access function 605 for processing and encoding. The processing and encoding of input data is part of uplink 609. The processed and encoded data is then provided to the 5G system 617.

[0123] In downlink 611, data received at the content delivery protocol module in media access function 605 is provided to another module for decryption, decoding, and processing. After decryption, decoding, and processing, the data can be stored in the raw buffer before being output to AR scene manager 603. Data from AR scene manager 603 is provided to AR runtime 601 for output to a device such as a display and / or speaker.

[0124] Figure 7 Example signaling and operation diagrams for experience quality degradation between user equipment and network entities in an XR session are shown.

[0125] At S701, the UE initiates a communication session. For example, the communication session can be an XR session, an AR session, a media session, an IMS (IP Multimedia Subsystem) session, or another Protocol Data Unit (PDU) session. In this example, the session is an XR session. It should be understood that the following signaling and operations apply to any type of communication session.

[0126] exist Figure 7In the example, the UE's XR application initiates an XR session by providing an instruction to the UE's Media Access Function (MAF) to start an XR session.

[0127] At S702, the MAF communicates with the UE's Media Session Handler (MSH) to establish (or set up) an XR session at the UE.

[0128] exist Figure 7 In the example, the session control submodule (as described above) is associated with or located within the UE's MSH. The buffer control submodule (as described above) is associated with or located within the UE's MAF.

[0129] At S703, the UE sends a request to the Application Function (AF) to establish an XR session. The request to establish the session can be initiated by the MSH.

[0130] At S704, the AF sends an indication to the UE that an XR session has been established.

[0131] At S705, the application provider (AP) sends media data for the XR session to the UE. The media data can be provided via the application server (AS). The media data can be received by the XR application.

[0132] At S706, it is assumed that media download for the XR session has begun. Media is provided from the AP to the AS, then from the AS to the MAF, and finally to the XR application.

[0133] In this manner, the signaling and operations of S701 to S705 can be the initial connection establishment for establishing a session between the UE (e.g., smartphone, mobile device / 5G UE / XR device) and the AS. Then, media is transmitted from the AP to the UE, and media download begins at S706.

[0134] At S707a, entities in the 5G core (5GC entities) submit energy-saving related requests to the AF. These energy-saving requests can be viewed as requests for QoS or QoE degradation. QoS and / or QoE are degraded for this session to reduce energy usage at the network.

[0135] The request may include information about QoE-related metrics (referred to herein as "QoE metrics"). In some examples, the request includes at least one of the following: triggering of power-saving modes, a range of values ​​for QoE metrics, information related to service experience, information about candidate UEs(s), and an expiration time / timer associated with the request (e.g., an expiration timer).

[0136] In some examples, energy-saving related requests are sent through the application layer (e.g., using application layer signaling). Using the application layer reduces the amount of network resources used (compared to sending requests using network signaling).

[0137] As an alternative to S707a, there is S707b.

[0138] At S707b, the AP provides the AF with energy-saving related requests. These energy-saving requests can be viewed as requests for QoS or QoE degradation. QoS and / or QoE are downgraded for this session to reduce energy usage at the network.

[0139] The request may include information about QoE-related metrics (referred to herein as "QoE metrics"). In some examples, the request includes at least one of the following: triggering of power-saving modes, a range of values ​​for QoE metrics, information related to service experience, information about candidate UEs(s), and an expiration time / timer associated with the request (e.g., an expiration timer).

[0140] Requests for S707a and / or S707b can be provided to the AF at a specific time or within a specific time window. For example, a request for energy saving can be provided during peak data traffic periods. For example, during peak data traffic periods (e.g., between 12 noon and 2 pm), the 5GC or AP determines to reduce energy consumption, for example, at the AS or throughout the network.

[0141] For S707a, energy-saving related requests have shifted from 5GC to AF. 5GC can be based on... Figure 8 The signaling and operations described in the document determine the possible range of QoE metrics included in the request.

[0142] Figure 8 Example signaling and operations between network entities related to triggering the energy-saving process are shown.

[0143] At S801, in the UDM, the authorization for QoE downgrade for the UE is added to the subscription data associated with that UE (referred to as "UE subscription data" in this document). In other words, the UE subscription QoE downgrade authorization is added to the UDM.

[0144] At S802, the SMF selects one UE from multiple UEs as the target for QoS degradation for a specific application. In other words, the SMF will select a specific UE for a specific application to reduce its QoS or QoE.

[0145] In some examples, the SMF checks with the PCF whether the SMF is authorized to perform QoS or QoE degradation on the UE / user.

[0146] At S803, the SMF provides the NWDAF with a request for information regarding the service experience (or service experience level) at the UE. In some examples, the SMF will register with the NWDAF to obtain analysis related to the (observed) service experience for the UE, with one or more candidate QoS metric ranges from the NWDAF. The request used for registration may include the identifier (e.g., application ID) of the application targeted at the UE.

[0147] At S804, the NWDAF provides the SMF with a response including information related to the QoE metric for the UE. This information may be a predicted QoE metric for the UE.

[0148] At S805, the SMF communicates with the UDM to determine whether the subscription data associated with the UE includes information related to QoE degradation. In some examples, the subscription data for the UE will indicate authorization for QoE degradation.

[0149] At S806, the SMF provides an energy-saving-related request to the AF. This request from the SMF to the AF can be provided via the Network Exposure Function (NEF). This request can designate the UE as a candidate for energy reduction. The request may include a QoE metric or a range of metrics.

[0150] The request in S806 is similar to that in S707a.

[0151] It should be understood that in other examples, Figure 8 One or more steps or operations in a process or operation may not be performed, or may be performed in a different order.

[0152] refer to Figure 7 At S708, power saving is triggered at AF based on a request (from S707a or S707b). Triggering power saving may include activating a power saving mode at AF.

[0153] In some examples, when the request in S707a or S707b does not include candidate UE information (e.g., an indication of one or more UEs), the AF determines the list of candidate UEs based on the information received in the request (S707a or S707b).

[0154] In some examples, the SMF can also provide the AF with multiple power-saving options for the candidate UE, and the AF can choose from those options. In these examples, the 5GC has provided the candidate UE with the policies associated with those options, or the 5GC can notify the AF to select the preferred options so that the associated policies can be provided to the candidate UE.

[0155] At S709, the AF sends a request to the UE for information regarding QoE metrics at the UE. This request can be for the current QoE metrics at the UE. The request for information may include indications of the application or session to which the request applies.

[0156] In some examples, the AF requests multiple UEs (including the UE itself) to provide their current QoE metrics. For instance, the AF may request all UEs receiving media data for a specific application to provide their QoE metrics. In some examples, when a request from the 5GC / AP identifies one or more candidate UEs with declining QoE, the AF provides a request for information based on one or more identities from the requests from the 5GC / AP.

[0157] At S710, based on the request (of S709), the UE sends information related to its QoE metric to the AF. The information related to the QoE metric may include information related to multiple different QoE metrics.

[0158] The QoE metric sent can be the current QoE metric used for this session. In some examples, the UE performs a measurement over a period of time to measure the QoE metric. The UE can determine to limit this measurement to a duration of X ms. In other examples, the UE may have recently performed a QoE measurement. If the UE has recently performed a QoE measurement, it can provide the most recent measurement.

[0159] exist Figure 7 In the example, it is assumed that the information related to the UE's QoE metric includes the value associated with that QoE metric.

[0160] At S711, AF compares information related to QoE metrics (e.g., values ​​related to the QoE metrics of the UE) with a threshold.

[0161] This threshold can be a QoE metric (or a range of metric) included in a 5GC or AP request (for S707a / b). For example, the threshold can be a value of a QoE metric or a value of a QoS metric.

[0162] For example, the 5GC or AP can (in the S707a / b request) instruct that the video resolution quality of all (or some) users connected to the AF between 12:00 noon and 2:00 pm be limited to 720p. Video resolution is a QoE metric. In other examples, the QoS metric is instructed to the AF (instead of the QoE metric). Based on the received QoS metric, the AF can request a QoE metric for the UE from the NWDAF based on the requested QoS metric. In other words, when the threshold includes a QoS metric, the AF communicates with the NWDAF to convert the QoS metric into a QoE metric. After conversion to a QoE metric, the AF performs a comparison with the information associated with the QoE metric received from the UE.

[0163] In some examples, the AF communicates with the 5GC to determine whether a QoE downgrade authorization is stored in the UE subscription data. Based on a comparison with this threshold, when the UE subscription data indicates that a specific QoE downgrade has been authorized, the AF knows that the QoE can be downgraded / reduced without the UE's approval. In other examples, the 5GC or AP (before triggering the AF for power saving) checks the UE subscription data for authorization and includes information related to this check in its request (S707a / b).

[0164] At S712, based on a comparison with the threshold, the AF sends a request to the UE to change at least one metric related to QoE (or QoS). For example, changing a QoE metric. This request can be a request to change the value of at least one QoE metric. This request is used for a session established between the UE and the AF (or AP). This request can be considered a request to reduce the QoE used for the session in order to reduce energy consumption (i.e., save energy).

[0165] Depending on whether the UE subscription data indicates that QoE degradation is permitted for a given QoE metric (or metric range), the S712 request can be approved or rejected by the UE, or it may have been pre-approved. In other words, in some cases, the S712 request may not require UE approval. If the UE has already consented to such QoE degradation, the AF will request a change to the QoE metric without obtaining the UE's consent.

[0166] In some examples, there is a timer associated with the request sent by the AF to the UE. If the UE response has not been received by the AF before the timer expires (e.g., after Y minutes), it indicates that the UE does not agree to the QoE downgrade, and the process continues in S723.

[0167] In some examples, the UE determines whether it can accept a request based on the S712 request. For example, the UE may determine whether it can accept the request based on the capacity level of the buffer associated with the session. In such examples, accepting or rejecting the request can be considered automatic. For example, the UE may accept or reject the request based on application settings (without user input). In other examples, the user is provided with an on-screen prompt where the user inputs whether to accept or reject the request. It should be understood that any suitable method can be used by the UE to determine whether to accept or reject the request.

[0168] As the first alternative, S713 to S723 are provided. For the first alternative, the UE accepts the request for QoE downgrade, or the UE subscription data has indicated authorization for QoE downgrade.

[0169] At S713, MSH notifies MAF of the reduced QoE. This activates buffer control in MAF. This notifies the application (e.g., via IF-7) that the application's QoE is now about to be reduced / degraded.

[0170] At S714, the MAF activates the buffer control submodule. The buffer control submodule is associated with or included within the UE's MAF.

[0171] At S715, the MSH sends a request to the MAF to modify an existing ongoing session. For example, the UE can modify the QoE metric of the session based on the request in S712.

[0172] In some examples, modifications made by the UE to a session include the UE changing the QoE metric for the session. For example, the UE can change the value of the QoE metric (or the value of the QoS metric).

[0173] At S716, the UE sends a request to the AF to modify the session. The request to modify the session may include an indication of the changed QoE metric (or QoS metric) for the session.

[0174] The request to modify may include a value related to a QoE metric that has been changed.

[0175] At S717, the AF stores information received from the UE related to the changed QoE metric (or QoS metric). For example, by storing the changed QoE metric at the AF, the AF can know the extent to which the UE is willing to accept future QoE degradation, which is indicated in the changed QoE metric.

[0176] In some examples, the QoE metrics accepted for the UE will be stored, allowing the AP or 5GS to perform analysis using the QoE metrics.

[0177] Based on S716 requests, AF modifies the session based on changes in QoE metrics.

[0178] At S718, the AF sends an acknowledgment to the UE regarding the request to modify the session. In some examples, this acknowledgment may indicate that the session has been successfully modified.

[0179] At S719, the AF sends an indication to the AP that the UE's session has been modified. This indication may include a notification of the changed QoE metric. In some examples, the AP or AF will notify the 5GC of the session modification.

[0180] At S720, the 5GC or AP provides the AF with an indication of whether the UE is eligible for incentives. Since the UE agrees to QoE downgrade, the UE can be eligible for incentives. For example, the incentive may include one of the following: free data or free subscription.

[0181] At S721, the AF sends an indication to the UE that the UE is suitable for the stimulus.

[0182] At S722, the AP provides the UE with data for the session. The data in S722 has a degraded (e.g., reduced) QoE metric compared to the data in S705. This QoE degradation has the effect of reducing energy usage at the network (i.e., energy saving).

[0183] In some examples, data received in S722 is buffered by a buffer control module before being provided to the XR application. In this context, buffering may include storing at least a portion of the data (e.g., media data) in a buffer. Buffering enables smoother playback of video, audio, games, or other data. For example, always having a pre-fed supply of video frames, audio samples, or game content in memory prevents playback interruptions due to momentary delays in the streaming rate. Figure 7 In this example, the buffer allows (XR) application to adapt to the new (degraded) QoE.

[0184] At S723, the data received in S722 is provided to the XR application. The data received in S722 can be considered as so-called "buffered data".

[0185] In this way, the AP continues to provide data to the UE, but the data is provided to the UE with at least one degraded QoE / QoS metric (e.g., reduced video resolution). In some examples, there is degradation for multiple different QoE metrics.

[0186] In some examples, after S722 / S723, AF repeats S709 to S711 to check whether the changed QoE / QoS metric is a result of session modification. AF can trigger further iterative changes to the QoE / QoS metric to further optimize the QoE / QoS metric (e.g., improve or downgrade the QoE / QoS metric).

[0187] As a second alternative, S724 to S727 are provided (instead of S713 to S723). In the second alternative, it is assumed that the UE rejects the request (of S712) used to downgrade the QoE of the session.

[0188] At S724, the UE continues the session using the current QoE metric.

[0189] At S725, the UE sends an indication to the AF that the current session will continue. This indication may indicate that there have been no changes in the QoE metric. In some examples, the indication at S725 may include an explicit rejection of the request.

[0190] At S726, the AP sends data for the session to the UE.

[0191] At S727, data for the session is provided to the XR application.

[0192] It should be understood that in other examples, Figure 7 One or more steps in the process may not be performed, or may be performed in a different order.

[0193] Figure 7 The signaling and operations can be applied to any UE or mobile device. For example, the signaling and operations can be applied to device types 2, 3, and 4. An example of “device type 2” is AR glasses. An example of “device type 3” is an XR phone. An example of “device type 4” is a head-mounted display (HMD) (e.g., according to 3GPP TS 26.119).

[0194] Figure 9 Another example signaling and operational diagram is shown between the user equipment and network entities for the experience quality set in an XR session. Figure 7 Compared to related systems, Figure 9 The buffer control submodule is located in the AF, not in the UE.

[0195] At S901, the UE initiates a communication session. For example, the communication session can be an XR session, an AR session, a media session, an IMS (IP Multimedia Subsystem) session, or another Protocol Data Unit (PDU) session. In this example, the session is an XR session. It should be understood that the following signaling and operations apply to any type of communication session.

[0196] exist Figure 9 In the example, the UE's XR application initiates an XR session by providing an instruction to the UE's Media Access Function (MAF) to start an XR session.

[0197] At S902, the MAF communicates with the UE's Media Session Handler (MSH) to establish (or set up) an XR session at the UE.

[0198] exist Figure 9 In the example, the session control submodule (as described above) is associated with or located within the UE's MSH. The buffer control submodule (as described above) is associated with or located within the AF.

[0199] At S903, the UE sends a request to the AF to establish an XR session. The request to establish the session can be initiated by the MSH.

[0200] At S904, the AF sends an indication to the UE that an XR session has been established.

[0201] At S905, the application provider (AP) sends media data for the XR session to the UE. The media data can be provided via the application server (AS). The media data can be received by the XR application.

[0202] At S906, it is assumed that media download for the XR session has begun. Media is provided from the AP to the AS, then from the AS to the MAF, and finally reaches the XR application.

[0203] In this manner, the signaling and operations in S901 to S905 can be the initial connection establishment for the establishment of a session between the UE (e.g., smartphone, mobile device / 5G UE / XR device) and the AS. Then, media is transmitted from the AP to the UE, and media download begins in S906.

[0204] At S907a, entities in the 5G core (5GC entities) submit energy-saving related requests to the AF. These energy-saving requests can be viewed as requests for QoS or QoE degradation. QoS and / or QoE are degraded for the session to reduce energy usage at the network.

[0205] The request may include information about QoE-related metrics (referred to herein as "QoE metrics"). In some examples, the request includes at least one of the following: triggering of power-saving modes, a range of values ​​for QoE metrics, information related to service experience, information about candidate UEs(s), and a validity period / timer (e.g., an expiration timer) associated with the request.

[0206] In some examples, energy-saving related requests are sent through the application layer (e.g., using application layer signaling). Using the application layer reduces the amount of network resources used (compared to sending requests using network signaling).

[0207] As an alternative to S907a, there is S907b.

[0208] At S907b, the AP provides energy-saving related requests to the AF. These energy-saving requests can be viewed as requests for QoS or QoE degradation. QoS and / or QoE are degraded for the session to reduce energy usage at the network.

[0209] The request may include information about QoE-related metrics (referred to herein as "QoE metrics"). In some examples, the request includes at least one of the following: triggering of power-saving modes, a range of values ​​for QoE metrics, information related to service experience, information about candidate UEs(s), and a validity period / timer (e.g., an expiration timer) associated with the request.

[0210] Requests for S907a and / or S907b can be provided to the AF at a specific time or within a specific time window. For example, a request for energy saving can be provided during peak data traffic periods. For example, during peak data traffic periods (e.g., between 12 noon and 2 pm), the 5GC or AP determines to reduce energy consumption, for example, at the AS or throughout the network.

[0211] For S907a, energy-saving related requests have shifted from 5GC to AF. 5GC can be based on... Figure 8 The signaling and operations described in the document determine the possible range of QoE metrics included in the request.

[0212] In S908, power saving is triggered at AF based on a request (as in S907a / b). In some examples, power saving can be a power saving mode triggered at AF.

[0213] In some examples, when the request in S907a or S907b does not include candidate UE information (e.g., an indication of one or more UEs), the AF determines the list of candidate UEs based on the information received in the request (S907a or S907b).

[0214] In some examples, the SMF can also provide the AF with multiple power-saving options for the candidate UE, and the AF can choose from those options. In these examples, the 5GC has provided the candidate UE with the policies associated with those options, or the 5GC can notify the AF to select the preferred options so that the associated policies can be provided to the candidate UE.

[0215] At S909, the AF sends a request to the UE for information regarding QoE metrics at the UE. This request can be for the current QoE metrics at the UE. The request for information may include indications of the application or session to which the request applies.

[0216] In some examples, the AF requests multiple UEs (including the UE itself) to provide their current QoE metrics. For instance, the AF may request all UEs receiving media data for a specific application to provide their QoE metrics. In some examples, when a request from the 5GC / AP identifies one or more candidate UEs with declining QoE, the AF provides a request for that information based on one or more identities from the requests from the 5GC / AP.

[0217] At S910, based on the request (of S909), the UE sends information related to its QoE metric to the AF. The information related to the QoE metric may include information related to multiple different QoE metrics.

[0218] The QoE metric sent can be the current QoE metric used for this session. In some examples, the UE performs a measurement over a period of time to measure the QoE metric. The UE can determine to limit this measurement to a duration of X ms. In other examples, the UE may have recently performed a QoE measurement. If the UE has recently performed a QoE measurement, it can provide the most recent measurement.

[0219] exist Figure 9 In the example, it is assumed that the information related to the UE's QoE metric includes the value associated with that QoE metric.

[0220] At S911, AF compares information related to QoE metrics (e.g., values ​​related to the UE's QoE metrics) with a threshold.

[0221] This threshold can be a QoE metric (or a range of metric) included in a 5GC or AP request (S907a / b). For example, the threshold can be a value of a QoE metric or a value of a QoS metric.

[0222] For example, a 5GC or AP (in the S907a / b request) can instruct that the video resolution quality of all (or some) users connected to the AF between 12 PM and 2 PM be limited to 720p. Video resolution is a QoE metric. In other examples, a QoS metric is instructed to the AF (instead of a QoE metric). Based on the received QoS metric, the AF can request a QoE metric for the UE from the NWDAF based on the requested QoS metric. In other words, when the threshold includes a QoS metric, the AF communicates with the NWDAF to convert the QoS metric into a QoE metric. After conversion to a QoE metric, the AF performs a comparison with the information associated with the QoE metric received from the UE.

[0223] In some examples, the AF communicates with the 5GC to determine whether a QoE downgrade authorization is stored in the UE subscription data. Based on a comparison with a threshold, when the UE subscription data indicates that a specific QoE downgrade has been authorized, the AF knows that the QoE can be downgraded / reduced without the UE's approval. In other examples, the 5GC or AP (before triggering the AF for power saving) checks the UE subscription data for authorization and includes information related to this check in its request (S707a / b).

[0224] At S912, buffer control is activated. The buffer control submodule is associated with or included within the AF. Figure 9 In the example, buffer control is from MAF (according to) Figure 7 The buffer management system is moved to the AF (Active Frame). This causes the management of buffers to move to the network side (rather than the UE side). Having buffer control in the AF will save UE computing resources.

[0225] At S913, based on a comparison with a threshold, the AF sends a request to the UE to change at least one metric related to QoE (or QoS). For example, changing a QoE metric. This request can be a request to change the value of at least one QoE metric. This request is used for a session established between the UE and the AF (or AP). This request can be considered a request to reduce the QoE used for that session in order to reduce energy consumption (i.e., save energy).

[0226] Depending on whether the UE subscription data indicates that QoE degradation is permitted for a given QoE metric (or metric range), the S913 request can be approved or rejected by the UE, or pre-approved. In other words, in some cases, the S913 request may not require UE approval. If the UE has already consented to such QoE degradation, the AF will request a change to the QoE metric without obtaining the UE's consent.

[0227] In some examples, there is a timer associated with the request sent by the AF to the UE. If the UE response has not been received by the AF before the timer expires (e.g., after Y minutes), it indicates that the UE does not agree to the QoE downgrade, and the process will continue in S922.

[0228] In some examples, the UE determines whether it can accept a request based on the request in S913. For example, the UE may determine whether it can accept the request based on the capacity level of the buffer associated with the session. In such examples, accepting or rejecting the request can be considered automatic. For example, the UE may accept or reject the request based on application settings (without user input). In other examples, the user is provided with an on-screen prompt where the user inputs whether to accept or reject the request. It should be understood that any suitable method can be used by the UE to determine whether to accept or reject the request.

[0229] As the first alternative, S914 to S922 are provided. For the first alternative, the UE accepts a request for QoE downgrade, or the UE's subscription data has indicated authorization for QoE downgrade.

[0230] At S914, the UE modifies the session. For example, the UE's MSH and MAF communicate with each other to modify the session. The UE can also modify the session based on a request in S913. For example, the UE can modify at least one QoE-related metric (e.g., multiple QoE metrics) of the session based on a request in S913.

[0231] In some examples, modifications made by the UE to a session include the UE changing the QoE metric for the session. For example, the UE can change the value of a QoE metric (or QoS metric).

[0232] In S915, the UE sends a request to the AF to modify the session. This request to modify the session may include an indication of the modified QoE metric for the session.

[0233] The request for modification may include a value related to a QoE metric that has changed. For example, the UE may indicate that the frame rate has changed from 30 frames per second to 24 frames per second. Similarly, the UE may indicate that the frame resolution has changed from 1080p to 720p.

[0234] At S916, the AF stores information received from the UE related to the changed QoE metric. For example, by storing the changed QoE metric at the AF, the AF can know the extent to which the UE is willing to accept a future QoE degradation, which is indicated in the changed QoE metric.

[0235] In some examples, the QoE metrics accepted for the UE will be stored, allowing the AP or 5GS to perform analysis using the QoE metrics.

[0236] As requested by S915, AF modifies the session based on changes in QoE metrics.

[0237] At S917, the AF sends an acknowledgment to the UE regarding the request to modify the session. In some examples, this acknowledgment can indicate that the session has been successfully modified.

[0238] At S918, the AF sends an indication to the AP that the session for the UE has been modified. This indication may include a notification of the changed QoE metric.

[0239] At S919, the 5GC or AP provides the AF with an indication of whether the UE is eligible for incentives. Since the UE agrees to QoE downgrade, the UE can be eligible for incentives. For example, incentives may include one of the following: free data or free subscription.

[0240] At S920, the AF sends an indication to the UE that the UE is suitable for the stimulus.

[0241] At S921, the AP provides the UE with data for the session. The data in S921 is considered to have a degraded (e.g., reduced) QoE metric compared to the data in S905. This QoE degradation has the effect of reducing energy usage at the network (i.e., energy saving).

[0242] In some examples, data received by the AF in S921 is buffered by the buffer control submodule in the AF before being provided to the XR application of the UE.

[0243] At S922, the data received in S921 is provided to the XR application. The data received in S922 can be considered as so-called "buffered data".

[0244] In this manner, the AP continues to provide data to the UE, but the data is degraded in QoE as it arrives at the UE from the MAF. Alternatively, the AP continues to provide data to the UE, but the data has at least one degraded QoE / QoS metric (e.g., reduced video resolution) as it arrives at the UE from the MAF. In some examples, there is degradation for multiple different QoE metrics.

[0245] As a second alternative, S923 to S926 are provided (instead of S914 to S922). In the second alternative, it is assumed that the UE rejects the request (of S913) used to downgrade the QoE of the session.

[0246] At S923, the UE continues the session using the current QoE metric.

[0247] At S924, the UE sends an indication to the AF that the current session will continue. This indication may indicate that there have been no changes in the QoE metric.

[0248] At S925, the AP sends data for the session to the UE.

[0249] At S926, data for the session is provided to the XR application.

[0250] It should be understood that in other examples, Figure 9 One or more steps in the process may not be performed, or may be performed in a different order.

[0251] Figure 9 The signaling and operations can be applied to any UE or mobile device. For example, these signaling and operations can be applied to devices of device type 1. An example of “device type 1” is ultra-thin AR glasses with limited device capabilities (e.g., as defined in 3GPP TS26.119).

[0252] Figures 7 to 9 Examples have already been described for 5G. It should be understood that these examples also apply to 6G systems.

[0253] One or more of the examples above have the advantage of saving energy in the communication system by monitoring QoS and / or QoE for ongoing sessions and proposing new metrics with the user's consent. This can be particularly important during peak network times, as the network may be under extremely high traffic loads, leading to high energy consumption. In one or more of the examples, communication between the network and the UE is used to determine whether the UE can tolerate degradation in QoS or QoE. For UEs that cannot tolerate degradation, the session continues without degradation. In this way, the UE is involved in the decision regarding degradation, rather than an established session being automatically degraded by the network. In this way, signaling and operations between entities mean that there is minimal impact on the service experience / QoE at the UE, while ensuring energy savings as much as possible.

[0254] In one or more of the examples, the network requests a user / UE to downgrade their QoE. When the user / UE agrees to this request, the network downgrades / reduces the QoE for that particular user / UE (e.g., frame resolution, bit rate reduction, etc.). The users are aware beforehand that their QoE will be downgraded. This increased control by the user / UE means that there is no unexpected degradation in service experience or quality of experience. Furthermore, the user / UE does not need to perform unnecessary "clicks" or inputs to manually change back the QoE metric (e.g., if the network has already automatically downgraded the resolution, there is no need to manually change it back to the previous setting).

[0255] Figure 10 An example method flow executed by a device is shown. This device can be a user equipment (or other communication device). In some examples, the device may be included within or as part of the user equipment. The device may include components for performing... Figure 10 The method may include one or more components. In some examples, the apparatus may include components for performing... Figure 10 The method's circuit system. In some embodiments, the device includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 10 The method.

[0256] At S1001, the method includes: receiving from an application function a second request to change at least one metric related to quality of experience (QoE), wherein the second request is for a session established between the user device and the application function.

[0257] In S1003, the method includes: based on the request, sending a third request to the application function to modify the session, wherein the third request indicates a change in at least one metric related to QoE.

[0258] In S1005, the method includes: receiving data for the session from an application function based on a change in at least one metric related to QoE, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

[0259] It should be understood that, in some embodiments, one or more additional method steps are included. Figure 10 In the method flow, and these steps are performed by the apparatus. In some embodiments, Figure 10 One or more method steps described in detail in the document may not be executed, or may be executed in a different order.

[0260] Figure 11 An example method flow executed by a device is shown. This device can provide an AF (or is configured to provide an AF). The device may include components for performing... Figure 11 The method may include one or more components. In some examples, the apparatus may include components for performing... Figure 11 The method's circuit system. In some embodiments, the device includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 11 The method.

[0261] In S1101, the method includes: receiving a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between a user device and an application function.

[0262] In S1103, the method includes: sending a second request to a user equipment to change at least one metric related to QoE, wherein the second request is used for establishing a session between the user equipment and an application function.

[0263] In S1105, the method includes: receiving a third request from a user equipment to modify a session, wherein the third request indicates a change in at least one metric related to QoE.

[0264] In S1107, the method includes: modifying the session based on a change in at least one metric related to QoE, according to the third request.

[0265] In S1109, the method includes: sending data for a session to a user equipment based on a change in at least one metric related to QoE, wherein the data sent is associated with a degraded QoE metric compared to previously sent data for the session before the change.

[0266] It should be understood that in some examples, one or more additional method steps are included. Figure 11 The method flow is in which these steps are performed by the device. In some examples, Figure 11 One or more method steps described in detail in the document may not be executed, or may be executed in a different order.

[0267] Figure 12 An example method flow executed by a device is shown. This device can provide a core network or core network entity. The device may include components for performing... Figure 12 The method may include one or more components. In some examples, the apparatus may include components for performing... Figure 12 The method's circuit system. In some embodiments, the device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 12 The method.

[0268] In S1201, the method includes: providing an application function with a first request related to energy saving, wherein the request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between the user device and the application function.

[0269] It should be understood that in some examples, one or more additional method steps are included. Figure 12 The method flow is in which these steps are performed by the device. In some examples, Figure 12 One or more method steps described in detail in the document may not be executed, or may be executed in a different order.

[0270] Figure 13 A schematic representation of the device is shown. Figure 13 A block diagram of apparatus 10 is illustrated by way of example. Apparatus 10 includes, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause apparatus 10 to perform at least the methods disclosed herein and any embodiments thereof. In the example, at least one memory and instructions (e.g., computer program code, software), together with at least one processor, are configured to cause apparatus 10 to perform the methods disclosed herein and any embodiments thereof.

[0271] Processor 12 may include, or be constituted by, one or more circuit systems configured to perform various stages of the method according to the example embodiments described herein. As used herein, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry having software / firmware; and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a user equipment) to perform various functions; and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or ( A circuit system is a portion of a multi-processor that requires software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of a circuit system applies to the use of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or multiple processors) or portions of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0272] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 is at least partially located outside the device 10, but is accessible to the device 10.

[0273] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) and read-only memory (ROM)).

[0274] For example, device 10 is a terminal device or UE, such as Figure 7 or Figure 9 The device is included in the UE. As another example, the device is included in such a terminal device / UE, for example, as a chipset configured to control the terminal device. The device 10 can be made or configured to at least perform Figure 10 The methods and / or one or more of the embodiments described herein.

[0275] As another example, device 10 is a network node or base station. In another embodiment, the device is included in such a network node, for example, as a chipset configured to control the network node.

[0276] As another example, device 10 provides one or more network functions (NFs) or the core NF of the network, such as Figure 7 or Figure 9 AF in, or Figure 7 or Figure 9 One or more core NFs in the 5GC. Device 10 can be configured to perform at least Figure 11 or Figure 12 The method and / or any one or more embodiments described.

[0277] The device 10 may include one or more entities in any protocol layer, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity, or a PHY entity.

[0278] Device 10 includes a radio interface 16. Radio interface 16 provides communication capabilities to device 10. Radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. Radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. Receivers may include more than one receiver. Transmitters may include more than one transmitter. Radio interface 16 may include transceivers configured to receive and transmit information according to at least one cellular or non-cellular standard. Transceivers may include more than one transceiver.

[0279] Device 10 may include a user interface 18, which may include at least one of the following: a keyboard, microphone, touch screen, display screen, speaker, etc. User interface 18 can be used to control the device by a user. User interface 18 may be located external to device 10. For example, device 10 may be connected to another device (such as a computer) via a wireless or wired connection, and device 10 may be controlled by a user via the computer.

[0280] In embodiments, at least some of the processes described herein may be performed by means including at least some of the components for performing the processes. Components for performing the method steps disclosed herein may include software and / or hardware components of means 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods disclosed herein and any embodiments thereof. As used herein, the term “component” is to be interpreted as either singular (i.e., a single element) or plural (i.e., a combination of single elements). Thus, the term “component for [performing A, B, C]” is to be interpreted to encompass means in which only one component exists for performing A, B, and C, or in which separate components exist for performing A, B, and C, or in which components partially or completely overlap for performing A, B, and C. Furthermore, the terms "component for performing A, component for performing B, component for performing C" should be interpreted to cover means that include only one component for performing A, B, and C, or means that include separate components for performing A, B, and C, or means that include partially or completely overlapping components for performing A, B, and C. It should be noted that although exemplary embodiments have been described above, several variations and modifications can be made to the disclosed solutions without departing from the scope of the invention.

[0281] Therefore, these embodiments can vary within the scope of the appended claims. Generally, some embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, although the embodiments are not limited thereto. While various embodiments may be shown and described as block diagrams, flowcharts, or other graphical representations, it should be well understood that, by non-limiting example, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0282] These examples can be implemented by computer software stored in memory and executed by at least one data processor of the relevant entity, or by hardware, or by a combination of software and hardware. Furthermore, it should be noted in this regard that any process can represent program steps, or interconnected logic circuits, blocks, and functions, or combinations of program steps with logic circuits, blocks, and functions. Software can be stored on physical media, such as memory chips or memory blocks implemented within a processor, magnetic media (such as hard disks or floppy disks), and optical discs (such as, for example, DVDs and their data variants, CDs).

[0283] As used in this article, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0284] As used herein, “at least one of the following: ” and “at least one of the following: ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, indicating at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0285] The memory can be of any type suitable for the local technological environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technological environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0286] As used herein, the terms “component for…”, “component comprising for performing an operation”, “component configured to perform an operation”, or “component configured to perform the following” (or similar) can be any component suitable for performing (or performing) the features(s). A “component” can be configured to perform one or more of the previously described functional and / or method steps. For example, a “component” can include one or more of the following: at least one processor, at least one memory, a transceiver circuit system, an antenna circuit system, etc. It should be understood that these are provided as non-limiting examples.

[0287] Alternatively or additionally, certain examples may be implemented using a circuit system. This circuit system may be configured to perform one or more of the previously described functional and / or method steps. This circuit system may be provided in a base station and / or communication equipment.

[0288] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuits and software, such as: (i) a combination of (multiple) analog and / or digital hardware circuits having software / firmware; and (ii) any part of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable an apparatus (such as a communication device or base station) to perform the various functions previously described; and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0289] This definition of circuit system applies to the use of the term "component" in this application (including in any claim). As another example, as used herein, the term circuit system also covers only hardware circuitry or a processor (or multiple processors) or portions of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0290] The foregoing description has provided a complete and informative description of some embodiments through exemplary and non-limiting examples. However, various modifications and alterations may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such modifications and similar alterations will still fall within the scope defined in the appended claims.

Claims

1. A user equipment, comprising: At least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to perform: Receive a second request from the application function to change at least one metric related to Quality of Experience (QoE), wherein the second request is for a session established between the user device and the application function; Based on the second request, a third request is sent to the application function to modify the session, wherein the third request indicates a change in the at least one metric related to QoE; as well as Based on the change in the at least one metric related to QoE, data for the session is received from the application function, wherein the received data is associated with a degraded QoE metric compared to previously received data for the session prior to the change.

2. The user equipment of claim 1, wherein the change in the at least one metric related to QoE comprises: The change of at least one value associated with the at least one metric related to QoE.

3. The user equipment of claim 1, wherein the second request for changing at least one metric related to QoE is associated with a request for downgrading the QoE metric for the session.

4. The user equipment of claim 1, wherein the at least one metric related to QoE includes at least one of the following: a metric for QoE, or a metric for QoS.

5. The user equipment of claim 1, wherein receiving data for the session comprises: Based on the changes in the at least one metric related to QoE, the data used for the session is buffered; as well as Based on the changes in the at least one metric related to QoE, the data for the already buffered session is provided to the application of the user device.

6. The user equipment of claim 1, wherein the user equipment is further configured to perform: Receive a fourth request from the application function, the fourth request relating to information related to the QoE for the session established at the user equipment; and Send information associated with at least one metric related to QoE for the session to the application function.

7. The user equipment of claim 1, wherein the session includes one of the following: a session for extended reality, a session for augmented reality, or an Internet Protocol Multimedia Subsystem session.

8. An apparatus for application functions, wherein the apparatus comprises: At least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the application function to perform: Receive a first request related to energy saving, wherein the first request includes: information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between the user equipment and the application function; Send a second request to the user equipment to change at least one metric related to QoE, wherein the second request is for the session established between the user equipment and the application function; Receive a third request from the user equipment to modify the session, wherein the third request indicates a change in the at least one metric related to QoE; Based on the third request, the session is modified according to the changes in the at least one metric related to QoE; and Based on the change in the at least one metric related to QoE, data for the session is sent to the user equipment, wherein the data sent is associated with a degraded QoE metric compared to previously sent data for the session prior to the change.

9. The apparatus of claim 8, wherein the first request comprises at least one of the following: triggering an energy-saving mode for the application function, a range of values ​​for at least one metric related to QoE, information related to service experience, information about user devices, information about multiple user devices, a timer related to the first request, or an expiration timer for the first request.

10. The apparatus of claim 8, wherein the first request is received from a core network entity or an application provider.

11. The apparatus of claim 8, wherein the transmission of data for the session comprises: Based on the changes in the at least one metric related to QoE, the data used for the session is buffered; as well as Based on the change in the at least one metric related to QoE, the data for the already buffered session is sent to the user equipment.

12. An apparatus for a core network, wherein the apparatus comprises: At least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the core network to perform: A first request related to energy saving is provided to an application function, wherein the request includes information associated with at least one metric related to quality of experience (QoE), wherein the first request is for establishing a session between the user device and the application function.

13. The apparatus of claim 12, wherein the apparatus is further configured to: determine, in conjunction with the unified data management communication, whether subscription data associated with the user equipment contains an indication of authorization for a degradation of QoE metrics, through the session management function. The first request is sent to the application function based on the communication.

Images