WO2023151773A1 - Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur - Google Patents

Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur Download PDF

Info

Publication number
WO2023151773A1
WO2023151773A1 PCT/EP2022/052938 EP2022052938W WO2023151773A1 WO 2023151773 A1 WO2023151773 A1 WO 2023151773A1 EP 2022052938 W EP2022052938 W EP 2022052938W WO 2023151773 A1 WO2023151773 A1 WO 2023151773A1
Authority
WO
WIPO (PCT)
Prior art keywords
energy usage
data
operations
usage data
energy
Prior art date
Application number
PCT/EP2022/052938
Other languages
English (en)
Inventor
Philipp BRUHN
German BASSI
Henrik RYDÉN
Ali Nader
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2022/052938 priority Critical patent/WO2023151773A1/fr
Publication of WO2023151773A1 publication Critical patent/WO2023151773A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • UE user equipment
  • a UE may use Discontinuous Reception (DRX) for receiving DL data.
  • DRX is a technique used in mobile communications to reduce UE energy consumption.
  • a base station e.g., gNB
  • a base station can configure a UE with a set of DRX parameters that allow the UE to decode a physical downlink control channel (PDCCH) to check for incoming DL traffic only at certain times, and to enter a sleep state at other times during which the UE does not monitor PDCCH and thus consumes less energy.
  • PDCCH physical downlink control channel
  • the base station must wait until the UE wakes up again. This means that DRX creates a trade-off between energy consumption and added delay.
  • a UE may use Scheduling Request (SR) procedure as a mechanism to request resources for a new UL transmission.
  • SR Scheduling Request
  • the UE may transmit the SR on a preconfigured, periodically occurring physical uplink control channel (PUCCH) resource.
  • PUSCH physical uplink shared channel
  • the periodicity of transmitting the SR which is configured for the UE by a network (NW) can range from once every 2 symbols up to once every 80ms.
  • the NW may want to limit the SR periodicity for the UEs (or a subset of the UEs) to 80ms to conserve PUCCH resources.
  • the NW may also configure the SR periodicity such that it is aligned with the UE's DRX cycle on-periods for the sake of UE energy saving. Otherwise, each time the UE exits the DRX to transmit the SR on PUCCH, the overall power savings achieved by the DRX may be reduced due to excessive wakeups.
  • the configured SR periodicity also has a direct impact on UL transmission delay. Upon receiving new data and/or packets from upper layers, the UE may have to wait up to 80ms for transmitting the SR before finally gaining access to UL resources for UL transmission.
  • RL is a type of Machine Learning (ML) scheme.
  • An RL algorithm continuously interacts with its environment and is given implicit and sometimes delayed feedback in the form of rewards.
  • the RL algorithm generally performs short-term reward maximization but can also make short-time irrational decisions in exchange for long-term gains.
  • Such RL algorithm attempts to maximize the expected future reward by exploiting already existing knowledge and exploring the space of actions in different network scenarios.
  • the optimization of the DRX configuration can be carried out by an RL agent that receives periodic feedback from UEs with respect to several different key performance indicators (KPIs) such as, for example, energy consumption and network throughput.
  • KPIs key performance indicators
  • This UE feedback includes information regarding UEs' energy usage data associated with UE configurations, which excludes UEs' energy usage data that is independent of the UE configurations (e.g., energy contribution associated with UE's user interface).
  • a network e.g., a base station
  • a network may need to adjust a particular UE configuration, and in order to determine how to adjust the particular UE configuration, the network may need the UE to provide to the network feedback information about UE's energy usage (a.k.a., "energy usage data”).
  • the energy usage data UE 102 provides to the network is generally about UE's energy usage that depends on multiple UE configurations. In other words, the energy usage data UE 102 provides to the network is not directed to the particular UE configuration the network wants to adjust.
  • the network may configure the UE with DRX parameters for UE energy saving while UE is in the connected mode.
  • the DRX parameters only affect the energy UE spends for monitoring PDCCH.
  • the feedback the UE provided to the network node is not only about monitoring PDCCH but also about receiving on PDSCH and transmitting on PUCCH/PUSCH which depend on other UE configurations such as carrier aggregation or dual connectivity.
  • the feedback information the UE provides to the network may be less meaningful in terms of finding an optimal UE configuration associated with DRX parameters. This introduces further uncertainty in the UE feedback, slows down the learning progress, and creates the need for much more training data.
  • Another challenge is that the energy usage data is generally collected and reported as a single metric or a single value for a given UE state even though the UE state may depend on multiple settings/configurations some of which may not be the subject of the network's energy efficiency optimization. This prevents the network from obtaining the energy usage data needed for training/updating multiple ML models that are used for optimizing different configurations with respect to UE's energy usage as such single metric or value of the energy usage data does not allow for an assessment of causality.
  • a method performed by a user equipment, UE comprises receiving a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected, the control message being transmitted by a network node.
  • the method further comprises based on the configuration information, collecting the first energy usage data, wherein the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • the method further comprises generating an energy report data based at least in part on the first energy usage data and transmitting towards the network node a feedback message comprising the generated energy report data.
  • a method performed by a network node comprises transmitting towards a user equipment, UE, a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected.
  • the method further comprises receiving a feedback message comprising energy report data, the feedback message being transmitted from the UE.
  • the energy report data is generated based at least in part on the first energy usage data, and the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • the UE may be configured to initiate performing the non-ongoing UE operations and collect energy usage data for performing the nonongoing UE operations.
  • control message may include a flag expressly indicating that the non-ongoing UE operations is to be initiated in response to receiving the control message and that energy usage data is to be collected for the non-going UE operations once being initiated. In some embodiments, if the control message does not include such indication, the UE may simply return zero energy consumption for the requested energy usage data associated with performing the non-ongoing UE operations. [0019] In another aspect, there is provided a computer program comprising instructions which when executed by processing circuitry cause the processing circuitry to perform the method described above.
  • a user equipment UE.
  • the UE is configured to receive a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected, the control message being transmitted by a network node.
  • the UE is further configured to, based on the configuration information, collect the first energy usage data, wherein the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • the UE is further configured to generate an energy report data based at least in part on the first energy usage data and transmit towards the network node a feedback message comprising the generated energy report data.
  • a network node configured to transmit towards a user equipment, UE, a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected.
  • the network node is further configured to receive a feedback message comprising energy report data, the feedback message being transmitted from the UE.
  • the energy report data is generated based at least in part on the first energy usage data, and the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • an apparatus comprising a memory and processing circuitry coupled to the memory, wherein the apparatus is configured to perform the method described above.
  • Embodiments of this disclosure enable a network node (e.g., a base station) to control UEs as to how collect (e.g., measures, calculates, stores, etc.) and/or report UE energy usage data (e.g., information about UE's energy consumption or UE's energy efficiency).
  • a network node e.g., a base station
  • collect e.g., measures, calculates, stores, etc.
  • UE energy usage data e.g., information about UE's energy consumption or UE's energy efficiency
  • Different configurations of a UE may contribute to the UE's overall energy consumption or efficiency differently.
  • the UE's energy consumption or efficiency associated with each of the UE configurations may contribute the UE's overall energy consumption or efficiency differently.
  • the embodiments of this disclosure allow the network node to control how a UE collects and/or reports one or more of such UE energy contributions in the form of UE feedback such that the network node can receive UE energy usage data associated with particular contribution(s) the network node is interested in (e.g., the UE energy contribution(s) that is subject to the network node's UE energy efficiency optimization process).
  • Improving the performance of the ML model results in better UE optimization (e.g., by configuring UEs in a better way), thereby achieving higher UE energy savings with the same or better quality of service (QoS) or performance or better QoS or performance with the same or less UE energy consumption. This leads to enabling more control over the trade-off between QoS or performance of UE(s) and UE energy savings.
  • QoS quality of service
  • Another advantage of the embodiments of this disclosure is that a UE only needs to monitor its energy consumption for specific features or functions and only when needed, instead of always monitoring the energy consumption for all features or functions. This reduces the number of parallel monitoring operations and the need for associated data storage for user devices, thereby allowing for less complex user devices.
  • the network node can adapt each feature or function separately and get more fine-granular information about each operation.
  • This allows faster adaptation of the ML algorithm, e.g., the RL agent, for a certain feature or function, since the UE feedback is significantly less distorted by "noise” from other sources, e.g., from other features or functions.
  • the RL agent needs to handle such distortion or "noise” by performing (significantly) more exploration and, as a consequence thereof, having a (significantly) longer exploration duration.
  • Reducing the training time of the RL agent reduces the need for UE feedback, which leads to a reduction in need for radio resources and energy consumption to report UE feedback.
  • reducing the training time of the RL agent also enables faster exploitation of the trained RL agent, which therefore leads to faster improvement the UE's energy efficiency.
  • the network node can receive individual UE energy consumption/efficiency feedback for the individual UE energy contributions that it is interested in, instead of a combined metric/value (aggregate) for all energy contributions that are associated with the UE configuration.
  • This allows making faster and better decisions on how to configure a UE for the optimal trade-off between QoS/performance and energy saving, with or without the use of ML methods, because it allows the immediate assessment of how individual parts of the UE configuration affect the QoS/performance as well as energy efficiency.
  • this also allows training or updating and therefore using multiple ML models to simultaneously optimize different parts of the UE configuration with respect to energy efficiency. This also enables faster and more fine-grained control over the inherent trade-off between QoS/performance and UE energy saving, which in turn enables the network node to reach the optimization goal faster and more accurately.
  • the NW can understand which parts of the receiver operation constitute a bottleneck, hence it can learn to optimize various features or functions for different user devices. For example, a UE with high amount of energy spent for monitoring PDCCH can be selected for optimizing said metric, while a UE whose main energy contributions are associated to PUSCH/PUCCH transmissions or PDSCH reception is selected for such optimization.
  • the network node can receive feedback on UL latency as a result of configured SR periodicity. For example, the UE can report the amount of time its UL data has been waiting in the UE buffer before an SR occasion or before an UL grant for data transmission. Based on such report the NW can reconfigure the PUCCH resources and or DRX scheme (e.g., offset or cycle) for the UE considering both energy consumption and latency.
  • SR periodicity For example, the UE can report the amount of time its UL data has been waiting in the UE buffer before an SR occasion or before an UL grant for data transmission.
  • the NW can reconfigure the PUCCH resources and or DRX scheme (e.g., offset or cycle) for the UE considering both energy consumption and latency.
  • Figure 1 shows a system according to some embodiments.
  • Figure 2 illustrates a process according to some embodiments.
  • Figure 3 shows an example of the content of configuration information.
  • Figure 4 shows a process according to some embodiments.
  • Figure 5 shows a process according to some embodiments.
  • Figure 6 shows a block diagram of a user equipment according to some embodiments.
  • Figure 7 shows a block diagram of a network node according to some embodiments.
  • FIG. 1 shows a system 100 according to some embodiments.
  • System 100 comprises a UE 102 and a network node 104 (e.g., a base station such as gNB).
  • Network node 104 is configured to provide a wireless network 110 through which UE 102 receives and/or sends data.
  • UE 102 is connected to and is served by network node 104.
  • UE 102 In order to receive data from network node 104 properly, UE 102 needs to monitor physical downlink control channel (PDCCH). More specifically, UE 102 needs to monitor the PDCCH included in each subframe to determine whether the subframe carries any data for UE 102 to receive. However, because UE 102 does not receive data in every single subframe, monitoring the PDCCH in every subframe may result in significant power consumption of UE 102. Thus, as discussed above, UE 102 may perform a discontinuous reception (DRX) (including idle mode DRX and connected mode DRX (“C-DRX”)).
  • DRX discontinuous reception
  • C-DRX connected mode DRX
  • UE 102 in the idle state i.e., the state where a radio connection between UE 102 and network node 104 is not established
  • UE 102 in the connected state i.e., the state where a radio connection between UE 102 and network node 104 is established
  • the connected mode DRX UE 102 in the connected state (i.e., the state where a radio connection between UE 102 and network node 104 is established) does not monitor PDCCH all the time. Rather, UE 102 discontinuously monitor PDCCH, thereby reducing the power consumption of UE 102.
  • network node 104 needs to configure UE 102 with proper DRX configuration.
  • UE 102 in order to transmit data from UE 102 towards network node 104 properly, UE 102 needs to transmit a scheduling request (SR) for requesting resources UE 102 to use for data transmission, and in order for UE 102 to transmit the SR properly, network node 104 needs to configure UE 102 with proper SR configuration.
  • SR scheduling request
  • FIG. 2 shows a process 200 for determining configuration(s) of UE 102 ("UE configuration”) according to some embodiments.
  • the UE configuration may include configuration(s) of UE 102 related to performing DRX (a.k.a., "DRX configuration”) and/or SR procedure (a.k.a., "SR configuration”).
  • Process 200 may be performed by a network node (e.g., network node 104).
  • Process 200 may begin with network node 104 transmitting towards UE 102 a first control message 204.
  • First control message 204 may comprise configuration information identifying one or more groups of one or more UE operations (performed by UE 102) for which information related to the energy usage (a.k.a., "energy usage data”) of UE 102 is to be collected and/or reported.
  • the energy usage data may include the total amount of power UE 102 consumes for performing each group of operations and/or statistic(s) (e.g., an average, a maximum, etc.) related to the amounts of power UE 102 consumes for performing each group of operations.
  • UE 102 may be configured to initiate performing the non-ongoing UE operations and collect energy usage data for performing the nonongoing UE operations.
  • the control message may include a flag expressly indicating that the non-ongoing UE operations is to be initiated in response to receiving the control message and that energy usage data is to be collected for the non-going UE operations once being initiated. In some embodiments, if the control message does not include such indication, the UE may simply return zero energy consumption for the requested energy usage data associated with performing the non-ongoing UE operations.
  • Figure 3 shows an example of the configuration information included in first control message 204 according to some embodiments. As shown in figure 3, the configuration information included in first control message 204 may identify a first group 302 of two operations 312 and 314 and a second group 304 of two operations 322 and 324. In some embodiments, some operation(s) included in first group 302 may also be included in second group 304. For example, in some embodiments, operation 312 and operation 322 are the same.
  • the configuration information may also identify a third group of one or more UE operations of which the effect on traffic latency is to be determined. For example, as shown in figure 3, the configuration information included in first control message 204 may identify a third group 306 of three operations 332, 334, and 336. In response to receiving the configuration information, UE 102 may determine information regarding a network latency (e.g., the amount of latency caused by performing the operations) caused by performing third group 306 of operations 332-336, and report such information (a.k.a., "latency data”) to network node 104.
  • a network latency e.g., the amount of latency caused by performing the operations
  • third group 306 may also be included in first group 302 and/or second group 304.
  • operation 312 and operation 332 may be the same and operation 314 and operation 334 may be the same.
  • the number of the groups of operations shown in figure 3 is provided for illustration purpose only and does not limit the embodiments of this disclosure in any way. More specifically, in the embodiments of this disclosure, the number of the groups can be any one number greater than or equal to 1.
  • the number of operations included in each group shown in figure 3 is provided for illustration purpose only and does not limit the embodiments of this disclosure in any way. More specifically, in the embodiments of this disclosure, the number of operations included in each group can be any one number greater than or equal to 1 .
  • Each operation included in first, second, and third groups 302-306 of operations may be selected from the list of operations included in Table 1 below.
  • the monitoring a PDCCH may include or exclude any one or more of the followings: receiving any information on the PDCCH, receiving information associated with user traffic on the PDCCH (e.g., including or excluding user-plane related information), or receiving information associated with control traffic on the PDCCH (e.g., including or excluding control-plane related information).
  • the receiving data on a PDSCH includes or excludes receiving downlink control information, DCI, on the PDCCH.
  • the transmitting data on a PUSCH includes or excludes any one or more of the followings: transmitting user traffic data on the PUSCH (i.e., transmitting user-plane related data), transmitting control traffic data on the PUSCH (transmitting control-plane related data), or transmitting uplink control information, UCI, on the PUSCH and/or the PUCCH.
  • the performing one or more processes related to PDCCH monitoring comprises any one or more of the followings: performing DRX while the UE is operating in a connected state, performing DRX while the UE is operating in a non-connected state, or receiving a wake-up signal, WUS, while the UE is operating in a non-connected state, and/or any other techniques or procedures for PDCCH monitoring.
  • the one or more synchronization signals are synchronization signal block, SSB, transmitted by the network node serving the UE and/or one or more neighboring network nodes neighboring the network node serving the UE.
  • SSB synchronization signal block
  • the one or more reference signals are channel state information reference signal, CSI-RS, transmitted by the network node and/or one or more neighboring network nodes neighboring the network node serving the UE.
  • CSI-RS channel state information reference signal
  • performing one or more processes related to multi-connectivity comprises any one or more of the followings: receiving and/or transmitting information using carrier aggregation; and receiving and/or transmitting information using dual connectivity.
  • the energy usage data and/or the latency data may be determined for frequency range 1 (FR1) and frequency range 2 (FR2) of 5G together. But in other embodiments, the energy usage data and/or the latency data is determined for each of the FR1 and FR2. Also, in some embodiments, the energy usage data and/or the latency data may be determined per carrier and/or frequency band.
  • the configuration information included in first control message 204 may indicate how to collect (e.g., measure, calculate, and/or store) and/or report the UE energy usage data related to performing the first and second groups 302 and 304 of operations and/or the latency data related to performing the third group 306 of operations.
  • the configuration information may indicate a period and/or a frequency of collecting the UE energy usage data and/or UE latency data.
  • the configuration may indicate whether UE 102 should collect the UE energy usage data and/or UE latency data continuously or whether UE 102 should start to collect the UE energy usage data and/or UE latency data upon detecting a start triggering event and/or should stop the collecting upon detecting a stop triggering event.
  • Each of the start triggering event and the stop triggering event may be any one or more of: starting and/or stopping of a service of a particular type (e.g., a video streaming) and/or detecting a particular triggering condition related to UE's energy (e.g., detecting that a remaining level of a battery included in UE 102 is below or above a threshold value, or detecting that UE 102 enters into or leaves from an energy saving mode).
  • a particular type e.g., a video streaming
  • detecting a particular triggering condition related to UE's energy e.g., detecting that a remaining level of a battery included in UE 102 is below or above a threshold value, or detecting that UE 102 enters into or leaves from an energy saving mode.
  • the configuration information may indicate a particular type of statistics (e.g., peak, average, etc.) to be used for generating the UE energy usage data or the UE latency data.
  • a particular type of statistics e.g., peak, average, etc.
  • UE 102 may generate separate energy usage report data and/or separate latency data for a different type of network traffic, a different network channel characteristic, a different quality of service, QoS, requirement, and/or a different UE mobility status.
  • the period/frequency of collecting UE energy usage data and/or UE latency data, whether UE 102 should collect the data continuously or start/stop collecting the data upon detecting triggering events, and/or whether UE 102 should use a particular type of statistics in generating the data may be defined globally for all operations or separately for each of different groups of operations.
  • the configuration information included in first control message 204 may indicate that different UE energy usage data (i.e., UE energy usage data associated with performing a different group of one or more UE operations) and different UE latency data should be collected and/or reported independently per a different traffic service type, a different logical channel, a different radio bearer, and/or a different quality of service (QoS) flow.
  • different UE energy usage data i.e., UE energy usage data associated with performing a different group of one or more UE operations
  • QoS quality of service
  • the configuration information may indicate that UE 102 should collect and/or report a separate UE energy usage data (or a separate UE latency data) for a different type of network traffic (e.g., voice over long-term evolution (VoLTE) or voice over new radio (VoNR) call, a video call, web surfing), a different network channel characteristic (RSRP or RSRQ), a different quality of service, QoS, requirement, and/or a different UE mobility status (stationary or moving).
  • the configuration information may indicate that UE energy usage data associated with monitoring PDCCH should be collected and/or reported while UE 102 is used for web browsing or a video call.
  • the configuration information may also indicate how to report the collected energy usage data.
  • network node 104 may instruct UE 102 to collect first energy usage data related to performing a first operation (e.g., the amount of energy consumed for performing the first operation) and second energy usage data related to performing a second operation (e.g., the amount of energy consumed for performing the second operation) and to send a single energy usage data report that is determined based on a combination of the first energy usage data and the second energy usage data (e.g., a single energy efficiency value).
  • network node 104 may instruct UE 102 to report two energy usage data reports (e.g., two energy efficiency values) one of which is associated with the first operation and another of which is associated with the second operation.
  • the configuration information included in first control message 204 may indicate how to report the collected UE energy usage data I UE latency data or how to use the collected UE energy data I UE latency data to calculate and report UE energy consumption/efficiency information.
  • the configuration information may indicate whether the reporting should be done once or multiple times and/or that the reporting should be done based on defined triggering condition(s) (e.g., when the calculated energy consumption or UL data buffer wait-time is above a certain threshold).
  • defined triggering condition(s) e.g., when the calculated energy consumption or UL data buffer wait-time is above a certain threshold.
  • the configuration may indicate that the frequency of the reporting is same as the frequency of the measuring or in case there are multiple measurements in a reporting period, if UE 102 should report all measurements per contribution or should report only statistics (e.g., mean, max/min values).
  • the configuration may indicate that whether UE 102 should report N highest energy consumption sources or report energy consumption/efficiency information derived based on the N highest energy consumption sources. This allows network node 104 to optimize the UE configuration with respect to highest energy contributors of UE 102.
  • the configuration information included in first control message 204 identifies the first and second groups 302 and 304 of UE operations for which the UE energy usage data is to be collected and the UE energy usage report is generated.
  • UE 102 may not be capable of collecting UE energy usage data associated with performing one or more of the UE operations included in the first and second groups 302 and 304. In such scenario, UE 102 cannot provide to network node 104 the requested energy usage report.
  • UE 102 may transmit towards network node 104 a UE capability message 202 prior to network node 104 transmitting towards UE 102 first control message 204.
  • UE 102 may transmit UE capability message 202 upon an occurrence of a triggering event.
  • the triggering event may be any one or more of the followings: receiving a request to send the UE capability message from network node 104, detecting that a predefined amount of time has elapsed (i.e., UE 102 is configured to periodically transmit the UE capability message), or detecting that a certain event related to UE operation (e.g., detecting that UE 102 is connected to network node 104) has occurred.
  • UE capability message 202 may comprise information related to UE 102's capability of collecting UE energy usage data associated with performing a candidate group of one or more UE operations.
  • network node 104 may determine the configuration information to be included in first control message 204 using the information included in UE capability message 202. For example, network node 104 may determine the configuration information based on the information included in UE capability message 202 such that the operations included in the first and second groups 302 and 304 are selected from the candidate group.
  • UE 102 may use the configuration information included in first control message 204 in order to collect the energy usage data and/or report the energy usage report.
  • first control message 204 identifies the first group 302 of operations 312 and 314 (e.g., transmitting data on PUSCH and receiving data on PDSCH) and the second group 304 of operations 322 and 324 (e.g., performing DRX while UE 102 is operating in a connected state and performing DRX while UE 102 is operating in a non-connected state). More specifically, first control message 204 shown in figure 3 may indicate that UE 102 should measure the amount of power consumption for performing first operation 312 and the amount of power consumption for performing second operation 314 every hour, and report an average amount of the power consumption every two hours.
  • first control message 204 shown in figure 3 may indicate that UE 102 should measure the amount of power consumption for performing third operation 322 (e.g., for performing DRX while UE 102 is operating in a connected state) and the amount of power consumption for performing fourth operation 324 (e.g., for performing DRX while UE 102 is operating in a non-connected state) every two hours, and report an average amount of the power consumption every four hours.
  • third operation 322 e.g., for performing DRX while UE 102 is operating in a connected state
  • fourth operation 324 e.g., for performing DRX while UE 102 is operating in a non-connected state
  • UE 102 upon receiving first control message 204, UE 102 measures the amount of power consumption UE 102 spent for transmitting data on PUSCH and receiving data on PDSCH every one hour, calculates an average amount of the power consumption, and reports to network node 104 the calculated average amount every two hours.
  • UE 102 upon receiving first control message 204, UE 102 measures the amount of power consumption UE 102 spent for performing DRX while UE 102 is operating in a connected state every two hours and performing DRX while UE 102 is operating in a non-connected state every two hours, calculates an average amount of the power consumption, and reports to network node 104 the calculated average every four hours.
  • UE 102 may determine whether UE 102 can successfully configure itself based on the configuration information included in first control message 204. In case UE 102 can successfully configure itself according to the configuration information, UE 102 may optionally transmit towards network node 104 a positive acknowledgement (ACK) message 206 indicating UE 102' s successful configuration (e.g., initialization) for reporting the requested usage report.
  • ACK positive acknowledgement
  • UE 102 may not be able to configure itself in accordance with the configuration information included in first control message 204. For example, because UE 102 is not capable of performing third operation 322 (e.g., performing DRX while UE 102 is operating in a connected state), UE 102 may not be able to measure the amount of power consumption UE 102 spent for performing DRX while UE 102 is operating in a connected state.
  • third operation 322 e.g., performing DRX while UE 102 is operating in a connected state
  • UE 102 may not be able to measure the amount of power consumption UE 102 spent for performing DRX while UE 102 is operating in a connected state.
  • UE 102 may transmit towards network node 104 a negative ACK (NACK) message 208 indicating UE 102's unsuccessful configuration (e.g., initialization).
  • NACK message 208 may also identify the operation(s) UE 102 cannot perform for collecting the requested energy usage data (e.g., performing DRX when UE 102 is in a connected state).
  • network node 104 may change the configuration information included in first control message 204 and resend first control message 204 that includes the changed configuration information.
  • the changed configuration information may identify a different group of one or more UE operations for which energy usage data is to be collected.
  • network node 104 may change the configuration information such that the configuration information no longer identifies the third operation 322 - performing DRX when UE 102 is in a connected state.
  • UE 102 may transmit towards network node 104 a UE feedback message 210 including the requested UE energy report.
  • UE feedback message 210 may include an average of power consumption of UE 102 for transmitting data on PUSCH and receiving data on PDSCH for one hour and an average of power consumption UE 102 spent for performing DRX while UE 102 was operating in a connected state and performing DRX while UE 102 as operating in a non-connected state for two hours.
  • network node 104 may determine UE configuration(s) using the information included in UE feedback message 210. As discussed above, in some embodiments, network node 104 may use a ML model (e.g., an RL model) to determine the optimal UE configuration(s).
  • a ML model e.g., an RL model
  • This ML model may be provided separately for each UE or may be provided separately for any one or more of the followings: the manufacturer of UEs (Samsung/Apple/Qualcomm%), an OEM vendor, a device model, a chipset vendor, a chipset model, software (SW) version, UE category (e.g., depending on NR performance capability), UE class (eMBB/smartphone, loT, RedCap, URLLC, XR, FWA ...), or UE subscription type (e.g., subscription that is used in a factory, premium subscription).
  • the ML model may be selected depending on UE's battery status (e.g., whether the UE is connected to a power source, whether UE's battery level is above or below a certain threshold value, etc.).
  • the UE's battery status may also be used at the network node to decide whether the ML model should perform exploration/exploitation.
  • network node 104 is configured to optimize two UE configurations with respect to UE energy efficiency - the C-DRX configuration and the multi-connectivity configuration.
  • network node 104 uses two ML models in parallel - one ML model for determining the best DRX parameters for UE 102 and another ML model for determining the best multi-connectivity setup for UE 102.
  • the C-DRX configuration impacts the UE energy consumption associated with monitoring PDCCH or receiving information on PDCCH while the multi-connectivity configuration impacts the UE energy consumption associated with reception of data on PDSCH and transmission of data on PUSCH.
  • network node 104 needs energy usage data associated with the C-DRX configuration and energy usage data associated with the multi-connectivity configuration separately. Otherwise, reported UE energy usage data may be dominated by UE energy consumption associated with reception of data on PDSCH and transmission of data on PUSCH. [0099] Therefore, according to the embodiments of this disclosure, network node 104 configures UE 102 to collect and/or report energy usage data (and the latency data) separately for each of the two UE configurations. Using the energy usage data for each of the two UE configurations, network node 104 may be able to optimize the C-DRX configuration and the multi-connectivity configuration independently.
  • Step s402 comprises receiving a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected, the control message being transmitted by a network node.
  • Step s404 comprises, based on the configuration information, collecting the first energy usage data, wherein the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • Step s406 comprises generating an energy report data based at least in part on the first energy usage data.
  • Step s408 comprises transmitting towards the network node a feedback message comprising the generated energy report data.
  • the configuration information further identifies one or more additional groups of one or more UE operations for which additional energy usage data is to be collected
  • the method further comprises, based on the configuration information, collecting the additional energy usage data, wherein the additional energy usage data indicates energy usage of the UE for performing said one or more additional groups of one or more UE operations, and the energy report data is generated based at least in part on the additional energy usage data.
  • the energy report data is either: the first energy usage data and/or one or more statistics calculated based on the first energy usage data, or any combination of the first energy usage data, additional energy usage data, and one or more statistics calculated based on the first energy usage data and/or the additional energy usage data.
  • the additional energy usage data indicates energy usage of the UE for performing one or more additional groups of one or more UE operations.
  • the method further comprises calculating a traffic latency resulting from performing an additional group of one or more UE operations, wherein the first group of one or more UE operations is included in said additional group of one or more UE operations, wherein the energy report data is generated based at least in part on the calculated traffic latency.
  • the configuration information contains a latency report command, and as a result of receiving the latency report command, the UE is configured to perform the calculation of the traffic latency.
  • each operation included in the first group of one or more UE operations is any one of the followings: monitoring a physical downlink control channel, PDCCH, receiving data on a physical downlink shared channel, PDSCH, transmitting data on a physical uplink shared channel, PUSCH, transmitting a scheduling request, SR, on a physical uplink control channel, PUCCH, performing one or more processes related to PDCCH monitoring, measuring and/or reporting of one or more synchronization signals, measuring and/or reporting of one or more reference signals, performing one or more processes related to multi-connectivity, receiving data and/or transmitting data on configured bandwidth parts, or receiving data and/or transmitting data using one or more antenna elements.
  • the monitoring a PDCCH excludes any one or more of the followings: receiving any information on the PDCCH, receiving information associated with user traffic on the PDCCH, or receiving information associated with control traffic on the PDCCH.
  • the receiving data on a PDSCH includes receiving downlink control information, DCI, on the PDCCH.
  • the transmitting data on a PUSCH includes or excludes any one or more of the followings: transmitting user traffic data on the PUSCH; transmitting control traffic data on the PUSCH; or transmitting uplink control information, UCI, on the PUSCH and/or the PUCCH.
  • the performing one or more processes related to PDCCH monitoring comprises any one or more of the followings: performing discontinuous reception, DRX, while the UE is operating in a connected state; performing DRX while the UE is operating in a non-connected state; or receiving a wake-up signal, WUS, while the UE is operating in a non-connected state.
  • said one or more synchronization signals are synchronization signal block, SSB, transmitted by the network node serving the UE and/or one or more neighboring network nodes neighboring the network node serving the UE
  • said one or more reference signals are channel state information reference signal, CSI-RS, transmitted by the network node and/or one or more neighboring network nodes neighboring the network node serving the UE.
  • the performing one or more processes related to multi-connectivity comprises any one or more of the followings: receiving and/or transmitting information using carrier aggregation; and receiving and/or transmitting information using dual connectivity.
  • the configuration information indicates how often the UE should collect energy usage data indicating energy usage of the UE for performing one or more UE operations.
  • the configuration information indicates one or more of: whether the UE should collect energy usage data indicating energy usage of the UE for performing one or more UE operations continuously, whether the UE should start to collect energy usage data indicating energy usage of the UE for performing one or more UE operations upon detecting a start triggering event, or whether the UE should stop collecting energy usage data indicating energy usage of the UE for performing one or more UE operations upon detecting a stop triggering event.
  • each of the start triggering event and the stop triggering event is any one or more of: starting of a video streaming, detecting that a remaining level of a battery included in the UE is below or above a threshold value, and detecting that the UE enters into or leaves from an energy saving mode.
  • the configuration information indicates a particular type of statistics of the first energy usage data the UE should use for generating the energy report data.
  • the configuration information indicates that the UE should generate a separate energy usage report data for: a different type of network traffic, a different network channel characteristic, a different quality of service, QoS, requirement, or a different UE mobility status.
  • the configuration indicates any one or more of: how often the UE should transmit the feedback message towards the network node, and a reporting condition for triggering the UE to transmit the feedback message.
  • the method further comprises: transmitting towards the network node a capability message, wherein the capability message indicates the UE's capability of collecting energy usage data associated with a set of operations, and each operation included in the first group of one or more UE operations is selected from the set of operations.
  • the method further comprises transmitting towards the network node a response message indicating whether the UE is capable of collecting the first energy usage data.
  • FIG. 5 shows a process 500 performed by network node 104 according to some embodiments.
  • Process 500 may begin with step s502.
  • Step s502 comprises transmitting towards a user equipment, UE, a control message including configuration information identifying a first group of one or more UE operations for which first energy usage data is to be collected.
  • Step s504 comprises receiving a feedback message comprising energy report data, the feedback message being transmitted from the UE.
  • the energy report data is generated based at least in part on the first energy usage data, and the first energy usage data indicates energy usage of the UE for performing the first group of one or more UE operations.
  • the configuration information further identifies one or more additional groups of one or more UE operations the UE is configured to perform for collecting additional energy usage data, the energy report data is generated based at least in part on the additional energy usage data, and the additional energy usage data indicates energy usage of the UE for performing said one or more additional groups of one or more UE operations.
  • the energy report data is either: the first energy usage data and/or one or more statistics calculated based on the first energy usage data, or any combination of the first energy usage data, additional energy usage data, and one or more statistics calculated based on the first energy usage data and/or the additional energy usage data, wherein the additional energy usage data indicates energy usage of the UE for performing one or more additional groups of one or more UE operations.
  • the energy report data is generated based at least in part on a traffic latency calculated by the UE, which is resulted from the UE performing an additional group of one or more UE operations, and the first group of one or more UE operations is included in said additional group of one or more UE operations.
  • the configuration information contains a latency report command, and as a result of receiving the latency report command, the UE is configured to perform the calculation of the traffic latency.
  • each operation included in the first group of one or more UE operations is any one of the followings: monitoring a physical downlink control channel, PDCCH, receiving data on a physical downlink shared channel, PDSCH, transmitting data on a physical uplink shared channel, PUSCH, transmitting a scheduling request, SR, on a physical uplink control channel, PUCCH, performing one or more processes related to PDCCH monitoring, measuring and/or reporting of one or more synchronization signals, measuring and/or reporting of one or more reference signals, performing one or more processes related to multi-connectivity, receiving data and/or transmitting data on configured bandwidth parts, or receiving data and/or transmitting data using one or more antenna elements.
  • the monitoring a PDCCH excludes any one or more of the followings: receiving any information on the PDCCH, receiving information associated with user traffic on the PDCCH, or receiving information associated with control traffic on the PDCCH.
  • the receiving data on a PDSCH includes receiving downlink control information, DCI, on the PDCCH.
  • the transmitting data on a PUSCH includes or excludes any one or more of the followings: transmitting user traffic data on the PUSCH; transmitting control traffic data on the PUSCH; or transmitting uplink control information, UCI, on the PUSCH and/or the PUCCH.
  • the performing one or more processes related to PDCCH monitoring comprises any one or more of the followings: performing discontinuous reception, DRX, while the UE is operating in a connected state; performing DRX while the UE is operating in a non-connected state; or receiving a wake-up signal, WUS, while the UE is operating in a non-connected state.
  • said one or more synchronization signals are synchronization signal block, SSB, transmitted by the network node serving the UE and/or one or more neighboring network nodes neighboring the network node serving the UE
  • said one or more reference signals are channel state information reference signal, CSI-RS, transmitted by the network node and/or one or more neighboring network nodes neighboring the network node serving the UE.
  • the performing one or more processes related to multi-connectivity comprises any one or more of the followings: receiving and/or transmitting information using carrier aggregation; and receiving and/or transmitting information using dual connectivity.
  • the configuration information indicates how often the UE should collect energy usage data indicating energy usage of the UE for performing one or more UE operations.
  • the configuration information indicates one or more of: whether the UE should collect energy usage data indicating energy usage of the UE for performing one or more UE operations continuously, whether the UE should start to collect energy usage data indicating energy usage of the UE for performing one or more UE operations upon detecting a start triggering event, or whether the UE should stop collecting energy usage data indicating energy usage of the UE for performing one or more UE operations upon detecting a stop triggering event.
  • each of the start triggering event and the stop triggering event is any one or more of: starting of a video streaming, detecting that a remaining level of a battery included in the UE is below or above a threshold value, or detecting that the UE enters into or leaves from an energy saving mode.
  • the configuration information indicates a particular type of statistics of the first energy usage data the UE should use for generating the energy report data.
  • the configuration information indicates that the UE should generate a separate energy usage report data for: a different type of network traffic, a different network channel characteristic, a different quality of service, QoS, requirement, or a different UE mobility status.
  • the configuration indicates any one or more of: how often the UE should transmit the feedback message towards the network node, and a reporting condition for triggering the UE to transmit the feedback message.
  • the method further comprises receiving a capability message, the capability message being transmitted from the UE, wherein the capability message indicates the UE's capability of collecting energy usage data associated with a set of operations, and each operation included in the first group of one or more UE operations is selected from the set of operations.
  • the method further comprises receiving a response message indicating whether the UE is capable of collecting the first energy usage data, the response message being transmitted from the UE.
  • FIG. 6 is a block diagram of UE 102, according to some embodiments.
  • UE 102 may comprise: processing circuitry (PC) 602, which may include one or more processors (P) 655 (e.g., one or more general purpose microprocessors and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); communication circuitry 648, which is coupled to an antenna arrangement 649 comprising one or more antennas and which comprises a transmitter (Tx) 645 and a receiver (Rx) 647 for enabling UE 102 to transmit data and receive data (e.g., wirelessly transmit/receive data); and a local storage unit (a.k.a., "data storage system”) 608, which may include one or more non-volatile storage devices and/or one or more volatile storage devices.
  • PC processing circuitry
  • P processors
  • ASIC application specific integrated circuit
  • FPGAs field-programmable gate arrays
  • CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644.
  • CRM 642 may be a non- transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like.
  • the CRI 644 of computer program 643 is configured such that when executed by PC 602, the CRI causes UE 102 to perform steps described herein (e.g., steps described herein with reference to the flow charts).
  • UE 102 may be configured to perform steps described herein without the need for code. That is, for example, PC 602 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.
  • FIG. 7 is a block diagram of network node 104, according to some embodiments.
  • the network node may comprise: processing circuitry (PC) 702, which may include one or more processors (P) 755 (e.g., one or more general purpose microprocessors and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be colocated in a single housing or in a single data center or may be geographically distributed (i.e., apparatus 700 may be a distributed computing apparatus); a network interface 768 comprising a transmitter (Tx) 765 and a receiver (Rx) 767 for enabling apparatus 700 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 748 is connected; communication circuitry 748, which is coupled to an antenna arrangement 749 comprising one or more antennas and which comprises a transmitter (Tx)
  • IP Internet Protocol
  • CPP 741 includes a computer readable medium (CRM) 742 storing a computer program (CP) 743 comprising computer readable instructions (CRI) 744.
  • CRM 742 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like.
  • the CRI 744 of computer program 743 is configured such that when executed by PC 702, the CRI causes the network node to perform steps described herein (e.g., steps described herein with reference to the flow charts).
  • the network node may be configured to perform steps described herein without the need for code. That is, for example, PC 702 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

Landscapes

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

Abstract

L'invention concerne un procédé mis en œuvre par un équipement utilisateur (UE). Le procédé comprend la réception d'un message de commande comprenant des informations de configuration identifiant un premier groupe d'une ou plusieurs opérations d'UE pour lesquelles des premières données d'utilisation d'énergie doivent être collectées. Le message de commande est transmis par un nœud de réseau. Le procédé comprend en outre, sur la base des informations de configuration, la collecte des premières données d'utilisation d'énergie, les premières données d'utilisation d'énergie indiquant l'utilisation d'énergie de l'UE pour effectuer le premier groupe d'une ou plusieurs opérations d'UE. Le procédé comprend en outre la génération de données de rapport d'énergie sur la base, au moins en partie, des premières données d'utilisation d'énergie et la transmission vers le nœud de réseau d'un message de rétroaction comprenant les données de rapport d'énergie générées.
PCT/EP2022/052938 2022-02-08 2022-02-08 Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur WO2023151773A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/052938 WO2023151773A1 (fr) 2022-02-08 2022-02-08 Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/052938 WO2023151773A1 (fr) 2022-02-08 2022-02-08 Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur

Publications (1)

Publication Number Publication Date
WO2023151773A1 true WO2023151773A1 (fr) 2023-08-17

Family

ID=80786225

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/052938 WO2023151773A1 (fr) 2022-02-08 2022-02-08 Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2023151773A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200229085A1 (en) * 2019-01-11 2020-07-16 Mediatek Inc. Electronic devices and methods for determining energy efficiency
WO2020145865A1 (fr) * 2019-01-10 2020-07-16 Telefonaktiebolaget Lm Ericsson (Publ) Rapport et configuration d'économies d'énergie d'équipement d'utilisateur (ue) de nr
WO2020193840A1 (fr) * 2019-03-27 2020-10-01 Nokia Technologies Oy Signalement de consommation d'énergie de dispositif sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020145865A1 (fr) * 2019-01-10 2020-07-16 Telefonaktiebolaget Lm Ericsson (Publ) Rapport et configuration d'économies d'énergie d'équipement d'utilisateur (ue) de nr
US20200229085A1 (en) * 2019-01-11 2020-07-16 Mediatek Inc. Electronic devices and methods for determining energy efficiency
WO2020193840A1 (fr) * 2019-03-27 2020-10-01 Nokia Technologies Oy Signalement de consommation d'énergie de dispositif sans fil

Similar Documents

Publication Publication Date Title
CN109845130B (zh) 与为在无线通信网络中工作的通信设备提供波束覆盖有关的方法和装置
JP6034885B2 (ja) データブロック伝送の処理時間依存制御
US10051504B2 (en) Methods and apparatuses for supporting MDT during eDRX
CN103069907A (zh) 通信网络中的用户终端的调度
US20230284136A1 (en) Sidelink control information based sensing
CN111989959B (zh) 一种信息发送、接收方法及装置
US20230180123A1 (en) Adjusting power consumption in a telecommunications network based on traffic prediction
US9955525B2 (en) Radio base station and method therein
US20220232476A1 (en) Adaptive wus transmission
KR20230078660A (ko) 사용자 장비에서의 적응적 추적 루프 업데이트
US20190297584A1 (en) User Device-Initiated Downlink Power Request
EP4014457B1 (fr) Procédé et appareil pour configuration de transmission
JP2022536656A (ja) Ｕｅ、無線局、及び方法
WO2018207102A1 (fr) Procédés et appareils pour réception discontinue courte (sdrx) dans un réseau de communication sans fil
WO2021077372A1 (fr) Procédé et nœud de réseau d'accès pour gestion de faisceaux
WO2020227913A1 (fr) Procédé et appareil de gestion de faisceau
CN112968755A (zh) 资源配置方法、网络设备及计算机存储介质
CN109756935B (zh) 一种调整工作带宽的方法和装置
US20230397115A1 (en) Employing paging early indicator for idle mode wireless communication device power savings
WO2023151773A1 (fr) Collecte et rapport de données d'utilisation d'énergie d'équipement utilisateur
WO2021213136A1 (fr) Procédé de communication et dispositif terminal
US20160057804A1 (en) Optimizing Channel State Switch based on the Traffic Volume Indicator (TVI) Values Associated with Throughputs on the Communication Links
US11963103B2 (en) Methods and apparatuses for paging
US20230422168A1 (en) Strategies for Power Efficient Configuration of a Wireless Access Network
WO2015169384A1 (fr) Transmission conditionnelle de mesure de bénéfice pour hypothèse de transmission multipoint coordonnée (comp) pour réseaux sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22708054

Country of ref document: EP

Kind code of ref document: A1