WO2024002461A1 - Nœud de réseau et procédé dans un réseau de communication - Google Patents

Nœud de réseau et procédé dans un réseau de communication Download PDF

Info

Publication number
WO2024002461A1
WO2024002461A1 PCT/EP2022/067592 EP2022067592W WO2024002461A1 WO 2024002461 A1 WO2024002461 A1 WO 2024002461A1 EP 2022067592 W EP2022067592 W EP 2022067592W WO 2024002461 A1 WO2024002461 A1 WO 2024002461A1
Authority
WO
WIPO (PCT)
Prior art keywords
power
rbs
network node
limited
schedule
Prior art date
Application number
PCT/EP2022/067592
Other languages
English (en)
Inventor
Ali YAVER
Ying Sun
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/067592 priority Critical patent/WO2024002461A1/fr
Publication of WO2024002461A1 publication Critical patent/WO2024002461A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0066Requirements on out-of-channel emissions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0076Allocation utility-based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04TPC
    • H04W52/18TPC being performed according to specific parameters
    • H04W52/28TPC being performed according to specific parameters using user profile, e.g. mobile speed, priority or network state, e.g. standby, idle or non transmission
    • H04W52/283Power depending on the position of the mobile
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04TPC
    • H04W52/30TPC using constraints in the total amount of available transmission power
    • H04W52/36TPC using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H04W52/365Power headroom reporting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04TPC
    • H04W52/06TPC algorithms
    • H04W52/14Separate analysis of uplink or downlink
    • H04W52/146Uplink power control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04TPC
    • H04W52/30TPC using constraints in the total amount of available transmission power
    • H04W52/36TPC using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H04W52/367Power values between minimum and maximum limits, e.g. dynamic range

Definitions

  • Embodiments herein relate to a network node and a method. In some aspects, they relate to deciding to schedule a User Equipment (UE) in a wireless communications network.
  • UE User Equipment
  • wireless devices also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part.
  • RAN Radio Access Network
  • CN Core Network
  • the RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in Fifth Generation (5G) telecommunications.
  • a service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.
  • 3GPP is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions.
  • EPS Evolved Packet System
  • 4G Fourth Generation
  • 3GPP 3rd Generation Partnership Project
  • 5G New Radio 5G New Radio
  • Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2).
  • FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz.
  • FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.
  • Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system.
  • a wireless connection between a single user, such as UE, and a base station the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel.
  • MIMO Multiple-Input Multiple-Output
  • SU Single-User
  • MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity.
  • MU-MIMO Multi-User
  • MU-MIMO may benefit when each UE only has one antenna.
  • Such systems and/or related techniques are commonly referred to as MIMO.
  • One aspect of these regulatory requirements it to prevent any outbound interference towards other networks outside RAN.
  • Such interference is most pronounced at the band edge.
  • UEs in this environment need to back-off (reduce) their maximum transmission power based on look-up tables.
  • MPR Maximum Power Reduction
  • AMPR Additional MPR
  • a support for AMPR functionality only defines a mechanism which allows a g/NR node B (gNB) to inform a UE about specific power back-off values to use.
  • the Identifiers for specific tables are signaled to the UE over a System Information Block 1 (SIB1).
  • SIB1 System Information Block 1
  • (A)MPR feature in itself does not mitigate any effects of using it, both in terms of throughput and coverage.
  • a separate functionality in the scheduler is required that takes potential power reduction at the UE side into account.
  • UEs are scheduled randomly over the entire available band for Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • An object of embodiments herein is to improve the performance when scheduling a UE in a wireless communications network that uses maximum output power backoff in uplink.
  • the object is achieved by a method performed by a network node.
  • the method is for scheduling a first UE in a wireless communications network.
  • Power backoff is activated for data traffic from the first UE to the network node.
  • the network node obtains a table comprising different power backoff values. For each power backoff value in the table a power backoff limit value providing a limit between causing a UE to be power limited and causing a UE to be non-power limited is calculated based on the power backoff value, and a required number of Radio Bearers (RBs), to empty a data buffer of the UE is estimated based on the related power backoff value.
  • RBs Radio Bearers
  • the network node determines a power state of the first UE based on the obtained table and a power headroom report received from the first UE.
  • the power state comprises whether the first UE is non-power-limited for all power backoff values in the table, power limited for all power backoff values in the table, or non-power limited for one or more power backoff value in the table and power limited for one or more other power backoff value in the table.
  • the network node decides whether to schedule the first UE in outer or edge region RBs of an available spectrum bandwidth, inner region RBs of the available spectrum bandwidth, or any region RBs of the available spectrum bandwidth.
  • the object is achieved by a network node configured to schedule a first UE in a wireless communications network.
  • Power backoff is arranged to be activated for data traffic from the first UE to the network node.
  • the network node is further configured to: obtain a table comprising different power backoff values, wherein for each power backoff value in the table:
  • a power backoff limit value providing a limit between causing a UE to be power limited and causing a UE to be non-power limited is adapted to be calculated based on the power backoff value
  • a required number of RBs to empty a data buffer of the UE is adapted to be estimated based on the related power backoff value, determine a power state of the first UE based on the obtained table and a power headroom report received from the first UE, which power state is adapted to comprise whether the first UE is,
  • Figure 1 is a schematic block diagram illustrating embodiments of a wireless communications network.
  • Figure 2 is a flowchart depicting an embodiment of a method in a network node.
  • Figure 3 is a schematic block diagram illustrating embodiments herein.
  • Figure 4 is a schematic block diagram illustrating embodiments herein.
  • Figure 5 is a schematic block diagram illustrating embodiments herein.
  • Figures 6 a-b are schematic block diagrams illustrating embodiments of a network node.
  • Figure 7 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.
  • Figure 8 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection
  • Figures 9-12 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Cell edge UEs require the highest transmit power and therefore they are subject to highest power back-off if they are scheduled at the edge PRBs. Therefore, a simple implementation would be to differentiate UEs based on their location such that cell edge UEs always end up in the middle PRBs. By moving UEs with worst channel to less or unaffected RB region, access to higher transmit power will be guaranteed. Not all cell- edge/low Signal to Interference Noise Ratio (SINR) UEs are power limited. If such UEs have small buffer, they do not need to transmit at full power and can meet their LA target even with MPR/AMPR back-off. Any scheduling constraints in terms of RB allocation therefore shall focus on power limited state of the UEs regardless of their proximity to the base station. In other words, any measure of channel quality alone is not sufficient to determine if the said UE requires any special treatment in the scheduling. Therefore, in embodiments herein for example:
  • SINR Signal to Interference Noise Ratio
  • a non-power limited UE and/or a UE with small buffer is assumed to have low power back-off impact.
  • Non-Power limited UEs e.g. buffer limited and/or good coverage
  • the UE location e.g. cell edge or cell center, is not an important criterion for scheduling decision making.
  • PUSCH repetitions may be provided if the power limited UEs cannot meet their LA target after backoff is applied.
  • the number of repetitions may counter the backoff in terms of combining gain.
  • Example of embodiments herein relate to deciding how to schedule for power limited UEs and non-power limited UEs when power backoff is activated for data traffic in Uplink (UL).
  • UL Uplink
  • scheduling decisions are based on the current power state, such as power limited state or non-power limited state, of the UEs.
  • a UE’s power state is a better metric to determine the extent to which a power backoff would impact the uplink performance rather than geographic location of the UE i.e. cell edge or cell center UE.
  • the UEs which are determined to be in power limited state due to e.g. a large UE buffer and/or a poor radio channel are e.g. decided to be scheduled in the center PRBs where the backoff is minimal. Any UEs which are non-power limited may then be prioritized for scheduling at the band edges, i.e. at the edge region RBs, of the available spectrum bandwidth.
  • Embodiments herein thus improve scheduling of UEs when power-limited UEs are present.
  • FIG. 1 is a schematic overview depicting a wireless communications network 100 wherein embodiments herein may be implemented.
  • the wireless communications network 100 comprises one or more RANs and one or more CNs.
  • the wireless communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • 6G Wi-Fi
  • LTE Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • GSM/EDGE Global System for Mobile communications/enhanced Data rate for GSM Evolution
  • UMB Ultra Mobile Broadband
  • Network nodes such as a network node 110, operate in the wireless communications network 100.
  • the network node 110 e.g. provides a number of cells and may use these cells for communicating with e.g. a UE 120 and/or a second UE 122.
  • the network node 110 may be a transmission and reception point e.g. a radio access network node such as a base station, e.g.
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR/g Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE served by the network node 110 depending e.g. on the radio access technology and terminology used.
  • eNB evolved Node B
  • eNodeB evolved Node B
  • gNB NR/g Node B
  • a base transceiver station such as a NodeB, eNodeB, eNode B), an NR/g Node B (gNB),
  • the UEs operate in the wireless communications network 100, such as e.g. a first UE 120 and in some examples, one or more second UEs 122.
  • the UE 120 and the one or more second UEs 122 may respectively be e.g. an NR device, a mobile station, a wireless terminal, an NB-loT device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to-everything (V2X) device, Vehicle-to- Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to-lnfrastructure (V2I) device, and a Vehicle-to-Network (V2N) device, a Wi-Fi device, an LTE device and a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g.
  • a base station such as e.g
  • the network node 110 one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN).
  • AN Access Networks
  • CN core networks
  • the UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.
  • D2D user equipment
  • Methods herein may in one aspect be performed by the UE 120, in another aspect by the network node 110.
  • a Distributed Node (DN) and functionality e.g. comprised in a cloud 135 as shown in Figure 1 , may be used for performing or partly performing the methods of embodiments herein.
  • Embodiments herein may relate to special handling for UEs such as e.g. the first UE 120 and/or the one or more second UEs 122, which are subjected to power backoff e.g. due to 3GPP MPR and AMPR feature.
  • UEs such as e.g. the first UE 120 and/or the one or more second UEs 122, which are subjected to power backoff e.g. due to 3GPP MPR and AMPR feature.
  • Embodiments herein enable maximum possible uplink transmission power for UEs such as e.g. the first UE 120 and/or the one or more second UEs 122, in the presence of power backoff, such as e.g. AMPR or MPR power backoff.
  • the power backoff affects the RBs such as PRBs towards the edge of the spectrum the most since the goal of the backoff is to reduce out of band emissions.
  • Band emissions when used herein e.g. means unwanted emissions outside the assigned radio channel bandwidth resulting from nonlinearity of the transmitters.
  • the power limited state of the UEs such as e.g. the first UE 120 and/or the one or more second UEs 122 is considered to make the power backoff based scheduling decision, and not only base the power backoff based scheduling decision on the radio channel as in prior art.
  • Figure 2 shows example embodiments of a method performed by the network node 110.
  • the method is for scheduling the first UE 120 in the wireless communications network 100.
  • Power backoff is activated for data traffic from the first UE 120 to the network node 110.
  • the first UE 120 may be placed in a scheduling queue together with one or more second UEs 122.
  • the power backoff is related to any one out of: MPR, or AM PR.
  • the method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 2.
  • the network node 110 establishes whether an average PRB utilization is above or below a threshold in a radio access network served by the network node 110 and any neighbouring network node in the wireless communications network 100. In some embodiments, this may be used later on for determining a power state of the one or more second UEs 122 in Action 203 below, only when the established average PRB utilization is above a threshold.
  • the network node 110 obtains a table comprising different power backoff values.
  • the table may be obtained by e.g., being received from a network node in the wireless communications network or being created by the network node 110 itself.
  • a power backoff limit value providing a limit between causing a UE to be power limited and causing a UE to be non-power limited is calculated based on the power backoff value.
  • a required number of RBs to empty a data buffer of the UE is estimated based on the related power backoff value.
  • This is a general table that may be applied for any UE, such as the first UE 120, to be scheduled, and having power backoff activated for UL data traffic.
  • non-power limited also means buffer limited in embodiments herein.
  • the first UE 120 is to be scheduled for some data packets in a buffer of the UE 120.
  • the network node 110 determines the power state of the first UE 120 based on the obtained table and a power headroom report received from the first UE 120. This may be to check the power state of the first UE 120 as a basis for deciding in which region of the available spectrum bandwidth to schedule RBs for the first UE 120. This determining of the power state based on table and the power headroom report may be performed by comparing the headroom report against the new maximum allowed transmission power.
  • the reported power headroom report gives an indication to the network such as the network node 110, that how close is the first UE 120 is to the maximum allowed transmission power while transmitting on PUSCH.
  • a UE is limited in terms of how much transmission power it can use in the uplink based on its power class standardized by 3GPP and regulatory requirements.
  • a power backoff value lowers this maximum transmission power further.
  • a positive value of power headroom report indicates that the UE, such as the first UE 120, is transmitting below the maximum allowed transmission power.
  • a negative value indicates that if there were no maximum power limit, the UE, such as the first UE 120, would exceed its maximum transmission power.
  • the network node 110 shall use a new maximum transmission power, which is maximum allowed power minus the table value, to determine if the first UE 120 is power limited.
  • the power state comprises whether the first UE 120 is:
  • non-power limited or buffer limited for one or more power backoff values in the table, and power limited for one or more other power backoff values in the table.
  • Power limited when used herein means that if allowed, the first UE 120 would use higher than maximum allowed power to transmit in the uplink in order to empty its buffer.
  • Non-power limited or equivalently buffer limited when used herein means that the first UE 120 does not require to use maximum transmission power in order to empty its buffer
  • this determining of the power state of the first UE 120 based on the obtained table and the power headroom report received from the first UE 120 is performed by determining in an order according to the scheduling queue, the respective power state of the first UE 120 and the one or more second UEs 122 based on the obtained table and a respective power headroom report received from the first UE 120 and the one or more second UEs 122.
  • the network node 110 determines the power state of the first UE 120 only when the established average PRB utilization is above the threshold. In some of these embodiments, the network node 110 determines the power state of the one or more second UEs 122 only when the established average PRB utilization is above the threshold.
  • the network node 110 decides whether to schedule the first UE 120 in:
  • the network node 110 decides whether to schedule the first UE 120, such that:
  • the network node 110 decides to schedule the UE 120 in the outer RB region or in any RB region,
  • the network node 110 decides to schedule the UE 120 in the inner RB region.
  • the first UE 120 is placed in the scheduling queue together with the one or more second UEs 122. This means that there is more than one UE to schedule for the network node 110.
  • the deciding of whether to schedule the first UE 120 in the outer or edge region RBs, inner region RBs, or any region RBs based on the determined power state of the first UE 120 further comprises deciding whether to schedule the respective one or more second UEs 122 in the outer or edge region RBs, inner region RBs, or any region RBs based on the respective determined power state of the one or more second UEs 120.
  • the network node 110 decides whether to schedule the first UE 120 in the outer or edge region RBs, inner region RBs, or any region RBs, only when the established average PRB utilization is above the threshold. In some of these embodiments, the network node 110 decides whether to schedule the respective one or more second UEs 122 in the outer or edge region RBs, inner region RBs, or any region RBs, only when the established average PRB utilization is above the threshold.
  • the MPR is a 3GPP feature defined in 3GPP TS 38.101 , which allows a UE, such as e.g. the first UE 121 and the one or more second UEs 122, to reduce its maximum transmit power for higher order modulation schemes and for transmit bandwidth configurations. It is designed to address out of band emissions due to non-linearity of UE amplifiers. Out of band emissions when used herein may mean emission caused by the first UE 120 immediately outside the assigned channel bandwidth due to transmitter nonlinearity or imperfects. A UE, such as the first UE 120, transmitter is more prone to out of band emissions compared to a base station, e.g. network node 110, transmitter due to implementational constraints and computational power.
  • a base station e.g. network node 110
  • An amount of relative Bandwidth determines if MPR is used or not.
  • the functionality may be executed based on look up tables grouped according to UE power class, modulation scheme to be used and the frequency band in use of the UE, such as e.g. the first UE 121 and the one or more second UEs 122.
  • Individual value of MPR for each power class varies according to the modulation scheme in use by the UE, such as e.g. the first UE 121 and the one or more second UEs 122.
  • MPR is applicable for all bands in Frequency Division Duplex (FDD) and Time Division Duplex (TDD) with special cases for frequency bands n40, n41 , n77, n78, n79 when a higher power UE, e.g. PC326dBm, is used.
  • PC326dBm when used herein e.g., means a UE, e.g. an example of the first UE 120, with power class 3 as defined by 3GPP which is allowed a maximum transmit power of 26dBm.
  • BPSK Binary Phase-shift keying
  • DFT Direct Fourier Transform
  • s Orthogonal Frequency Division Multiplexing
  • OFDM Orthogonal Frequency Division Multiplexing
  • AMPR is similar to MPR but at the gNB level, such as the network node 110 level.
  • a specific value of power backoff to be used may be signaled by the network node 110 in the form of a Network Signalling Value (NS) value.
  • An NS value refers to a corresponding indication of an NR frequency band number of an applicable operating band.
  • Each NS value corresponds to a table of power back off values for a given spectrum.
  • the network node 110 e.g. a base station, informs the UE such as e.g. the first UE 121 and the one or more second UEs 122, which backoff values they are mandated to use.
  • NS_x values signaled by the network node 110 to the UE 121 , 122.
  • the Information Element (IE) field frequency Band Indicator NR referred to as freqBandlndicatorNR
  • additionalSpectrumEmission in relevant Radio Resource Control (RRC) lEs.
  • Each NS value corresponds to a AMPR value in a table of AMPR values. Different frequency bands support different NS values detailed described in 3GPP Table 6.2.3.1-1A of 38.101. Each NS value in turn references the same table. This means that the table of power reduction values to be used may be determined by the NS values.
  • RB regions for both MPR and AMPR are defined based on inner, outer and edge PRBs.
  • RBs Resource Blocks
  • Figure 3 depicts that the Total Number of RBs NRB comprises:
  • NRB Total Number of RBs
  • LCRB Length of contiguous resource block allocation
  • RBStart.Low max(1 , floor(LCRB/2)). This determines the start region of outer RBs. For example for an LCRB of 15, RB 0 to RB 6 represent a total of 7 RBs in the beginning of spectrum.
  • RBStart.High NRB - RBStart.Low - LCRB. This determines the outer RBs at the end of the spectrum. RBStart, Low ⁇ RBStart ⁇ RBStart, High, This determines the RBs in the inner RB region. And
  • Embodiments herein may be implemented in an Estimate Required Number of RBs function, e.g. inside a Radio Resource Management (RRM) Algorithm specification.
  • RRM Radio Resource Management
  • (A)MPR is a term used herein in order to cover both MPR and AM PR since for the purpose embodiments herein they do the same thing. Therefore the wordings (A)MPR, MPR and AMPR may be used interchangeably herein.
  • an input in the form of the table comprising different power backoff values such as e.g. an MPR or AMPR table is provided to the function, e.g. an- Carrier Frequency and UE power class specific AMPR Table 400 as illustrated in Figure 4.
  • Figure 4 illustrates an example of the method according to embodiments herein, e.g. how to calculate the table that in a later state (output) shall be used when scheduling UEs, such as e.g. any of the UEs 121 , 122.
  • the table itself may be chosen based on the NS value that network node 110 has signaled.
  • a UE metric according to embodiments herein is provided with the table comprising the following features: These are the values, also referred to as metrics, metrics, that are comprised in the table.
  • UE Power State 403 Power Limited, also referred to as non-Buffer limited, OR non-power limited (buffer limited) per (A)MPR value. • Required Number of RBs per (A)MPR value 404
  • a UE metric when used herein is a combination of the above two bullets.
  • the UE metric 403 comprises the information to be used by the scheduler for a particular UE such as the first UE 120 and possible the oner more UEs 122.
  • a UE becomes power limited or non-power limited.
  • a UE may or may not be power limited with following example possibilities:
  • a UE is non-power limited (or buffer limited) for ALL back-off values. (This UE is a good candidate for scheduling in the outer RB region)
  • a UE is power limited (or non-buffer limited) for ALL back-off values (This UE is a good candidate for scheduling in the inner RB region).
  • a UE is non-power limited (or buffer limited) for one or more back-off value(s) i.e. one or more of the lowest back-off values.
  • the UE is power limited (or non-buffer limited) for one or more back-off value(s) i.e. one or more of the highest back-off values.
  • This relates to and may be combined with Actions 203 and 204 described above.
  • the Network node 110 e.g. a PUSCH allocator in the network node 110, will use the obtained table and a power headroom report received from the first UE 120 to determine a power state of the first UE 120 and possible the one or more second UEs 122, and based on that decide how to schedule the first UE 120 and possible the one or more second UEs 122.
  • Figure 5 illustrates the procedure.
  • the network node 110 such as its PUSCH allocator evaluates the first UE 120 according to the UE metric. This may be performed for a UE such as the first UE 120 at the top of a scheduling queue of e.g. one or more second UEs 122. Based on the power limited state of the first UE 120 and possibly the one or more second UEs 122, they are scheduled at different regions of the PRB map.
  • the priority 504 may be to schedule that UE in the first available PRB preferring the outer or edge region RBs to avoid fragmentation.
  • UEs metrics which indicate that the UE such as the first UE 120 and possibly the one or more second UEs 122, is power limited 505 for all or some backoff values, or 506 if it is power limited 506 for outer RB region but buffer limited for inner RB region, it may be prioritized 507 for scheduling in the inner region RBs among the available PRBs. If no inner PRBs are available for the given UE metric, choose the second best UE metric, e.g. second smallest backoff value.
  • the network node 110 is configured to schedule the first UE 120 in the wireless communications network 100.
  • Power backoff is arranged to be activated for data traffic from the first UE 120 to the network node 110.
  • the power backoff is adapted to be related to any one out of: MPR, or AMPR.
  • the first UE 120 is arranged to be placed in a scheduling queue together with the one or more second UEs 122, and wherein the network node 110.
  • the network node 110 may comprise an arrangement depicted in Figures 6a and 6b.
  • the network node 110 may comprise an input and output interface 600 configured to communicate in the wireless communications network 100, e.g. with the first UE 120 and/or to the one or more second UEs 122.
  • the input and output interface 600 may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).
  • the network node 110 may further be configured to, e.g. by means of an establishing unit 601 in the network node 110, establish whether an average PRB utilization is above or below a threshold in a radio access network served by the network node 110 and any neighbouring network node in the wireless communications network 100.
  • the network node 110 may further be configured to, e.g. by means of an obtaining unit 602 in the network node 110, obtain a table comprising different power backoff values, wherein for each power backoff value in the table:
  • a power backoff limit value providing a limit between causing a UE to be power limited and causing a UE to be non-power limited is adapted to be calculated based on the power backoff value
  • a required number of RBs to empty a data buffer of the UE is adapted to be estimated based on the related power backoff value.
  • the network node 110 may further be configured to, e.g. by means of a determining unit 603 in the network node 110, determine a power state of the first UE 120 based on the obtained table and a power headroom report received from the first UE 120, which power state is adapted to comprise whether the first UE 120 is,
  • the network node 110 may further be configured to, e.g. by means of a deciding unit 604 in the network node 110, based on the determined power state of the first UE 120, decide whether to schedule the first UE 120 in:
  • the network node 110 may further be configured to, e.g. by means of the deciding unit 604 in the network node 110, decide whether to schedule the first UE 120, such that:
  • the network node 110 may further be configured to, e.g. by means of the determining unit 603 in the network node 110, determine the power state of the first UE 120 based on the obtained table and the power headroom report received from the first UE 120, by determining in an order according to scheduling queue, the respective power state of the first UE 120 and the one or more second UEs 122 based on the obtained table and a respective power headroom report received from the first UE 120 and the one or more second UEs 122.
  • the network node 110 may further be configured to, e.g. by means of the deciding unit 604 in the network node 110, decide whether to schedule the first UE 120 in the outer or edge region RBs, inner region RBs, or any region RBs based on the determined power state of the first UE 120, and further decide whether to schedule the respective one or more second UEs 122 in the outer or edge region RBs, inner region RBs, or any region RBs based on the determined power state of the respective second UE 122.
  • the network node 110 may further be configured to, e.g. by means of the determining unit 603 and/or the deciding unit 604 in the network node 110, in an order according to the scheduling queue, any one or more out of:
  • the embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 660 of a processing circuitry in the network node 110 depicted in Figure 6a, together with respective computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 110.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 110.
  • the network node 110 may further comprise a memory 670 comprising one or more memory units.
  • the memory 670 comprises instructions executable by the processor in network node 110.
  • the memory 670 is arranged to be used to store e.g. information, indications, data, configurations, device types, device information, feature tags, communication data, and applications to perform the methods herein when being executed in the network node 110.
  • a computer program 680 comprises instructions, which when executed by the respective at least one processor 660, cause the at least one processor of the network node 110 to perform the actions above.
  • a respective carrier 690 comprises the respective computer program 680, wherein the carrier 690 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the units in the network node 110 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the network node 110, that when executed by the respective one or more processors such as the processors described above.
  • processors as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a- chip SoC.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, e.g. wireless communications network 100, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, e.g., the network node 110, such as AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c e.g.
  • radio network nodes 141 ,142 is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE), e.g. first UE 120, such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c, e.g., the network node 110.
  • a second UE 3292, e.g., any of the one or more second UEs 122, such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a, e.g., the network node 110. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 7 as a whole enables connectivity between one of the connected UEs 3291 , 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211 , the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 8) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Figure 8) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 12 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Figure 7, respectively.
  • the inner workings of these entities may be as shown in Figure 8 and independently, the surrounding network topology may be that of Figure 7.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the RAN effect: data rate, latency, power consumption and thereby provide benefits such as e.g. the applicable corresponding effect on the OTT service: reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • FIG. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8.
  • a host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIG 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8.
  • a host computer receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third sub step 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Landscapes

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

Abstract

L'invention concerne un procédé mis en œuvre par un nœud de réseau permettant de programmer un premier équipement utilisateur (UE) dans un réseau de communication sans fil. Une réduction de puissance est activée pour un trafic de données du premier UE au nœud de réseau. Le nœud de réseau obtient (202) une table comprenant différentes valeurs de réduction de puissance. Pour chaque valeur de réduction de puissance dans la table, une valeur limite de réduction de puissance fournissant une limite entre amener un UE à être limité en puissance et amener un UE à ne pas être limité en puissance est calculée sur la base de la valeur de réduction de puissance, et un nombre requis de porteuses radio (RB) pour vider un tampon de données de l'UE est estimé sur la base de la valeur de réduction de puissance associée. Le nœud de réseau détermine (203) un état de puissance du premier UE sur la base de la table obtenue et un rapport de marge de puissance reçu du premier UE. L'état de puissance indique si le premier UE est non limité en puissance pour toutes les valeurs de réduction de puissance dans la table, limité en puissance pour toutes les valeurs de réduction de puissance dans la table, ou non limité en puissance pour une ou plusieurs valeurs de réduction de puissance dans la table et limité en puissance pour une ou plusieurs autres valeurs de réduction de puissance dans la table. Sur la base de l'état de puissance déterminé du premier UE, le nœud de réseau décide (204) s'il faut programmer le premier UE dans des RB de région de bord ou externe d'une largeur de bande de spectre disponible, des RB de région interne de la largeur de bande de spectre disponible, ou des RB de toute région de la largeur de bande de spectre disponible.
PCT/EP2022/067592 2022-06-27 2022-06-27 Nœud de réseau et procédé dans un réseau de communication WO2024002461A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/067592 WO2024002461A1 (fr) 2022-06-27 2022-06-27 Nœud de réseau et procédé dans un réseau de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/067592 WO2024002461A1 (fr) 2022-06-27 2022-06-27 Nœud de réseau et procédé dans un réseau de communication

Publications (1)

Publication Number Publication Date
WO2024002461A1 true WO2024002461A1 (fr) 2024-01-04

Family

ID=82547043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/067592 WO2024002461A1 (fr) 2022-06-27 2022-06-27 Nœud de réseau et procédé dans un réseau de communication

Country Status (1)

Country Link
WO (1) WO2024002461A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130165132A1 (en) * 2006-07-25 2013-06-27 Motorola Mobility Llc Spectrum emission level variation in schedulable wireless communication terminal
CN113891447A (zh) * 2020-07-03 2022-01-04 大唐移动通信设备有限公司 一种上行资源的分配方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130165132A1 (en) * 2006-07-25 2013-06-27 Motorola Mobility Llc Spectrum emission level variation in schedulable wireless communication terminal
CN113891447A (zh) * 2020-07-03 2022-01-04 大唐移动通信设备有限公司 一种上行资源的分配方法及装置

Similar Documents

Publication Publication Date Title
US9961646B2 (en) Devices and method using transmit power control and scheduling for LTE unlicensed band operation
US10327282B2 (en) Network node, a wireless device and methods therein for selecting a communication mode in a wireless communications network
KR20190038555A (ko) 채널 리소스 이용에 따라 우선순위화된 트래픽을 위한 lte-v2v 에서의 혼잡 제어
EP2949166A1 (fr) Allocation de ressources dans un réseau de radiocommunication
US20190254043A1 (en) Apparatuses, methods and computer programs for implementing fairness and complexity-constrained a non-orthogonal multiple access (noma) scheme
US20220039150A1 (en) User Equipment for Obtaining a Band Width Part for a Random Access, a Network Node, and Corresponding Methods in a Wireless Communication Network
US20220104199A1 (en) Method and apparatus for sharing communication channel
CN113439475A (zh) 网络节点、ue和在其中执行的用于处理通信的方法
US11622358B2 (en) Network node and method in a wireless communications network
US20190312693A1 (en) A Wireless Device, a Network Node and Methods Therein for Transmission of Synchronization Signals
CN113711522A (zh) 速率匹配模式的有效信令
EP3753115A1 (fr) Attribution de saut de fréquence de canal physique partagé montant (pusch)
US11395330B2 (en) Method and apparatus for adaptive scheduling and transmission
WO2024002461A1 (fr) Nœud de réseau et procédé dans un réseau de communication
WO2020201106A2 (fr) Ue et premier nœud de réseau pour gérer des ajustements de puissance
US11902964B2 (en) Network node and method performed therein for scheduling user equipment in uplink
US20170118742A1 (en) Methods and apparatus for uplink clear channel assessment
RU2767780C1 (ru) Выбор ресурсов физического канала управления восходящей линии связи (pucch) до конфигурирования на уровне управления радиоресурсами (rrc)
WO2023134909A1 (fr) Nœud de réseau et procédé dans un réseau de communication sans fil
WO2023147873A1 (fr) Nœud de réseau et procédé de planification d'équipements utilisateurs dans un réseau de communication sans fil
WO2022231499A1 (fr) Équipement utilisateur, nœud de réseau et procédés dans un réseau de communications sans fil
EP4316031A1 (fr) Noeud de réseau radio et procédé mis en oeuvre dans un réseau de communication
WO2023282802A1 (fr) Nœud de réseau radio, équipement utilisateur et procédés associés

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

Country of ref document: EP

Kind code of ref document: A1