CN111133802B - Network Node Power Control - Google Patents

Network Node Power Control Download PDF

Info

Publication number
CN111133802B
CN111133802B CN201780094932.9A CN201780094932A CN111133802B CN 111133802 B CN111133802 B CN 111133802B CN 201780094932 A CN201780094932 A CN 201780094932A CN 111133802 B CN111133802 B CN 111133802B
Authority
CN
China
Prior art keywords
mode
autonomous
normal
rus
power saving
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201780094932.9A
Other languages
Chinese (zh)
Other versions
CN111133802A (en
Inventor
M·桑德格伦
M·布雷谢尔
P·弗伦格
M·尼尔松
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to CN202311058464.3A priority Critical patent/CN117082601A/en
Publication of CN111133802A publication Critical patent/CN111133802A/en
Application granted granted Critical
Publication of CN111133802B publication Critical patent/CN111133802B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • 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/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0891—Non-scheduled access, e.g. ALOHA using a dedicated channel for access for synchronized access
    • 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

Landscapes

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

Abstract

A method is disclosed for a centralized unit, CU, of a wireless communication network, wherein the CU is associated with each of one or more remote units, RU, of the wireless communication network via a respective communication interface. The CU is adapted to operate in one of a plurality of modes including at least a normal operating mode and a power saving operating mode, the normal operating mode defining a plurality of functions to be performed by the CU. The method includes (when the CU is in the normal mode of operation): determining that a traffic load associated with the one or more RUs meets a power saving operation criterion; configuring each of the RUs for autonomous operation via the respective communication interfaces, whereby each of the RUs is configured to perform at least one of the plurality of functions; and transitioning from the normal operation mode to the power saving operation mode. Corresponding methods, computer program products, network nodes, and apparatuses for a CU and RU, respectively, for a remote unit are also disclosed.

Description

Network node power control
Technical Field
The present disclosure relates generally to the field of wireless communication networks. More particularly, the present disclosure relates to power control in a network node of a wireless communication network.
Background
Within the third generation partnership project (3 GPP) and other standardization organizations, attention is directed to reducing the energy consumption of network nodes (e.g., base stations). For example, some reasons for this concern include reduced cost and reduced environmental occupancy.
One typical approach for reducing power consumption is to define different power states (also referred to as modes) for a device (or modules, units, blocks, etc. included in a device), where the different power states include one or more low power states, such as a sleep mode. Typically, power is saved at the cost of increasing the delay of some or more functions to be performed by the device. Thus, deep sleep mode generally requires a long wake-up time compared to shallow sleep mode.
According to many radio access technologies for wireless communication, there is a necessary signaling between devices (typically control signaling between a wireless communication device such as a User Equipment (UE) and a network node such as a base station, and/or broadcast signaling of the base station) even when no traffic is served. These signaling prevent an efficient base station sleep mode and result in poor power consumption versus scaling of served traffic.
There are methods for power control of network nodes. For example, EP 2157824A1 discloses a network node adapted to enter a standby mode, wherein a sleep control device of the network node is adapted to switch on the network node upon occurrence of a trigger event during a monitoring period. However, this approach suffers at least in part from the same problems as described above, as the network node must leave standby mode for some necessary signalling (e.g. broadcast signalling).
Accordingly, there is a need for alternative and improved methods for using low power modes of network nodes.
Disclosure of Invention
It should be emphasized that the term "comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps, or components, but does not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be noted that when reference is made herein to power consumption (or energy saving), the corresponding statement is generally equally applicable to power consumption (or power saving), and vice versa.
It is an object of some embodiments to address or mitigate, alleviate or eliminate at least some of the above-identified deficiencies or others.
According to a first aspect, the object is achieved by a method for a centralized unit, CU, of a wireless communication network, wherein the CU is associated with each of one or more remote units, RU, of the wireless communication network via a respective communication interface. The CU is adapted to operate in one of a plurality of modes including at least a normal operating mode and a power saving operating mode, the normal operating mode defining a plurality of functions to be performed by the CU.
The method includes (when the CU is in the normal mode of operation): determining that a traffic load associated with the one or more RUs meets a power saving operation criterion; configuring each of the RUs for autonomous operation via the respective communication interfaces, whereby each of the RUs is configured to perform at least one of the plurality of functions; and transitioning from the normal operation mode to the power saving operation mode.
In certain embodiments, the at least one of the plurality of functions comprises one or more of:
-responding to a random access request by issuing a random access grant for transmission;
-responding to a need for system information by providing a system information block for transmission;
-providing a synchronization signal for transmission;
-providing a main information block for transmission; and
-providing a system information block for transmission.
In some embodiments, the power saving operation criteria includes that none of the one or more RUs are associated with a WCD in connected mode.
In some embodiments, configuring each of the RUs for autonomous operation includes at least one of:
-providing a pre-generated random access grant to the RU;
-providing a pre-generated system information block to the RU;
-providing a timing reference to the RU; and
-providing the RU with a pre-generated master information block.
According to some embodiments, the power saving mode of operation is a sleep mode. Then, in some embodiments, the method may further include (when the CU is in the power save mode of operation): detecting a normal operation mode trigger event; configuring each of the RUs for non-autonomous operation via the respective communication interfaces; and transitioning from the power saving mode of operation to the normal mode of operation.
In certain embodiments, detecting the normal operation mode trigger event comprises at least one of:
-receiving an interrupt signal from one of the one or more RUs;
-receiving a paging signal from the wireless communication network; and
-detecting that a predetermined time period for said power saving operation mode has elapsed.
According to some embodiments, the power saving mode of operation is a shutdown mode. Then, according to some embodiments, if the CU is a first CU, the method may further comprise configuring a second CU to: controlling respective communication interfaces of the one or more RUs; detecting a normal operation mode trigger event for the first CU; configuring each of the RUs for non-autonomous operation via the respective communication interfaces; and causing the first CU to transition from the shutdown mode to the normal operation mode.
A second aspect is a method for a remote unit, RU, of a wireless communication network, wherein the RU is associated with a centralized unit, CU, of the wireless communication network via a communication interface. The RU is adapted to operate in one of a plurality of modes including at least a non-autonomous mode of operation associated with a normal mode of operation of the CU and an autonomous mode of operation associated with a power saving mode of operation of the CU, and the normal mode of operation defines a plurality of functions to be performed by the CU.
The method includes (when the RU is in the non-autonomous mode of operation): receiving autonomous operation mode configuration signaling from the CU via the communication interface; configuring the RU to perform at least one of the plurality of functions; and transitioning from the non-autonomous mode of operation to the autonomous mode of operation.
In certain embodiments, the at least one of the plurality of functions comprises one or more of:
-responding to a random access request by issuing a random access grant for transmission;
-responding to a need for system information by providing a system information block for transmission;
-providing a synchronization signal for transmission;
-providing a main information block for transmission; and
-providing a system information block for transmission.
In some embodiments, the configuration signaling includes at least one of:
-a pre-generated random access authorization;
-a pre-generated system information block;
-a timing reference; and
-a pre-generated master information block.
According to some embodiments, the method may further comprise (when the RU is in the autonomous mode of operation): detecting a non-autonomous mode of operation trigger event; and transitioning from the autonomous mode of operation to the non-autonomous mode of operation, whereby the RU is not configured to perform any of the plurality of functions.
In certain embodiments, detecting the non-autonomous operation mode trigger event includes at least one of:
-receiving a random access request from a wireless communication device associated with the RU;
-detecting that more pre-generated random access grants are required;
-detecting that more pre-generated system information blocks are required;
-detecting that more pre-generated main information blocks are required; and
-detection requires a new timing reference.
The method may further comprise: and sending an interrupt signal for triggering a normal operation mode of the CU to the CU.
In certain embodiments, detecting the non-autonomous operation mode trigger event includes at least one of:
-receiving a paging signal from the CU;
-receiving non-autonomous operation mode configuration signaling from the CU via the communication interface; and
-detecting that a predetermined time period for said autonomous mode of operation has elapsed.
A third aspect is a computer program product comprising a non-transitory computer readable medium having a computer program comprising program instructions thereon. The computer program is loadable into a data-processing unit and configured to cause execution of the method according to any of the first and second aspects when the computer program is run by the data-processing unit.
A fourth aspect is an apparatus for a centralized unit, CU, of a wireless communication network, wherein the CU is associated with each of one or more remote units, RU, of the wireless communication network via a respective communication interface. The CU is adapted to operate in one of a plurality of modes including at least a normal operating mode and a power saving operating mode, and the normal operating mode defines a plurality of functions to be performed by the CU.
The apparatus comprises a controller configured such that (when the CU is in the normal operation mode): determining that a traffic load associated with the one or more RUs meets a power saving operation criterion; configuring each of the RUs for autonomous operation via the respective communication interfaces, whereby each of the RUs is configured to perform at least one of the plurality of functions; and transitioning from the normal operation mode to the power saving operation mode.
A fifth aspect is an apparatus for a remote unit, RU, of a wireless communication network, wherein the RU is associated with a centralized unit, CU, of the wireless communication network via a communication interface. The RU is adapted to operate in one of a plurality of modes including at least a non-autonomous mode of operation associated with a normal mode of operation of the CU and an autonomous mode of operation associated with a power saving mode of operation of the CU, and the normal mode of operation defines a plurality of functions to be performed by the CU.
The apparatus includes a controller configured such that (when the RU is in the non-autonomous mode of operation): receiving autonomous operation mode configuration signaling from the CU via the communication interface; configuring the RU to perform at least one of the plurality of functions; and transitioning from the non-autonomous mode of operation to the autonomous mode of operation.
A sixth aspect is a centralized unit CU comprising the apparatus according to the fourth aspect.
A seventh aspect is a remote unit RU comprising an apparatus according to the fifth aspect.
An eighth aspect is a network node comprising at least one of: a centralized unit according to the sixth aspect, and one or more remote units according to the seventh aspect.
In certain embodiments, any of the above aspects may additionally have the same or corresponding characteristics as any of the various characteristics as explained above for any other aspect.
An advantage of some embodiments is to provide a method for low power mode of a network node.
Another advantage of some embodiments is the ability to reduce power consumption in low traffic load scenarios.
Another advantage of some embodiments is the ability to dynamically use one or more low power modes of the network node.
Yet another advantage of some embodiments is that the necessary signaling can be managed even if the network node is in a low power mode.
Another advantage of some embodiments is that the disadvantage of delay in transitioning from a low power mode is mitigated.
Yet another advantage of some embodiments is that the mode change is completely transparent to the wireless communication device associated with the RU(s).
Drawings
Other objects, features and advantages will become apparent from the following detailed description of embodiments, which proceeds with reference to the accompanying drawings. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating exemplary embodiments.
FIG. 1 is a combined flow chart and signaling diagram showing example method steps and signaling in accordance with certain embodiments;
FIG. 2 is a schematic diagram illustrating an example functional partition, according to some embodiments;
FIG. 3 is a schematic block diagram illustrating an example apparatus in accordance with certain embodiments;
FIG. 4 is a schematic block diagram illustrating an example apparatus according to some embodiments;
FIG. 5 is a schematic block diagram illustrating an example apparatus in accordance with certain embodiments;
FIG. 6 is a schematic block diagram illustrating an example apparatus in accordance with certain embodiments; and
FIG. 7 is a schematic diagram illustrating an example computer-readable medium according to some embodiments.
Detailed Description
As already mentioned above, it should be emphasized that the term "comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Embodiments of the present disclosure will be described and illustrated more fully below with reference to the accompanying drawings. The solutions disclosed herein may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein.
Hereinafter, embodiments of the method in which alternatives and improvements for low power modes of network nodes are provided will be described. According to some embodiments, when a Centralized Unit (CU) is to enter a low power mode (e.g., sleep mode or shutdown mode), certain functions typically performed by the centralized unit are handed over to one or more Remote Units (RUs). Furthermore, according to some embodiments, when a first centralized unit is to enter a shutdown mode, certain functions typically performed by the first centralized unit are handed over to another centralized unit. Thus, existing functionality is divided between the centralized unit and the remote units in different ways depending on the current mode of the centralized unit. In other words, tasks are redistributed between CUs and RUs when conditions allow and do not require the introduction of special and/or parallel techniques.
The centralized unit(s) and remote unit(s) are physically separate units and the association between CUs and RUs is accomplished via a communication interface. The communication interface may be implemented using any suitable known or future physical and protocol methods (e.g., fiber, copper, ethernet, communication bus, radio interface, etc.).
The associated CUs/RUs may or may not be co-located at the same geographic site, the same logical site, and/or may not be included in the same network node. The names centralized unit and remote unit will be understood to describe functional features rather than physical features. Thus, a centralized unit is typically the unit of the network node responsible for performing non-distributed functions, while a remote unit is typically the unit of the network node responsible for performing distributed functions. Functionally, the remote unit is typically closer to the radio access interface than the centralized unit.
Fig. 1 is a combined flow chart and signaling diagram illustrating example method steps and signaling between a Centralized Unit (CU) 110 and associated Remote Units (RUs) 150, in accordance with some embodiments.
The CU is adapted to operate in one of a plurality of modes, including a normal operation mode 112 and one or more power saving operation modes (sleep mode 118 and optionally shutdown mode 132). The RU is also adapted to operate in one of a plurality of modes including at least a non-autonomous operating mode (152) and an autonomous operating mode (156), the non-autonomous operating mode (152) being associated with a normal operating mode of the CU, the autonomous operating mode (156) being associated with a power saving operating mode of the CU.
When a CU is in the normal operation mode 112, there are multiple functions to be performed by the CU. These functions may include, for example, one or more of the following: responding to the random access request by issuing a random access grant for transmission by the RU; responding to a demand for system information by providing a system information block for transmission by the RU; providing a synchronization signal for transmission by the RU; providing a master information block for transmission by an RU; and providing a system information block for transmission by the RU.
During the CU normal operation mode 112, the RU is in the non-autonomous operation mode 152, and the method includes: the CU determines whether the traffic load associated with one or more associated RUs meets a power save operation criteria, as shown by step 114. For example, a power saving operation criterion may be met when none of the associated RUs are in a connected mode WCD. If the power save operation criteria is not met ("no" path out of step 114), the CU remains in the normal operation mode 112.
The traffic load may be measured according to any suitable metric and may be obtained using any suitable known or future method. For example, the registration unit may be configured to track a wireless communication device currently registered with a particular RU and its corresponding modes of operation (e.g., idle mode, connected mode, etc.). Then, if the RU does not currently have a wireless communication device in an active (e.g., connected) mode, the registration unit may determine that a traffic load associated with the RU meets a power save operation criterion.
If the power save operation criteria is met ("yes" path out of step 114), the CU prepares for sleep mode 118 by configuring its associated RU(s) for autonomous operation, as shown by step 116 and signaling 190. Autonomous operation mode configuration signaling 190 occurs via the respective communication interface of each RU and autonomous operation mode configuration signaling 190 is received by the RU in step 154, where the RU is configured accordingly for autonomous operation. The configuration of an RU for autonomous operation includes: the RU is configured to perform at least one of a plurality of functions performed by the CU in a normal operating mode.
Configuration of an RU may include configuring the RU to perform the following functions: the random access request is responded to by issuing a random access grant for transmission by the RU. The configuration of steps 116 and 154 may then include: the CU provides the RU with a pre-generated random access grant.
In some embodiments, when the RU sends a random access grant, a Timing Advance (TA) indication will be included. Such a TA cannot generally be pre-generated because it depends on the physical distance between the RU and the wireless communication device. Thus, in autonomous mode, the RU is typically configured to calculate a TA for transmission with a random access grant.
Configuration of an RU may include configuring the RU to perform the following functions: the need for system information is responded to by providing a block of system information for transmission by the RU. The configuration of steps 116 and 154 may then include: the CU provides the RU with a pre-generated system information block.
Configuration of an RU may include configuring the RU to perform the following functions: a synchronization signal is provided for transmission by the RU. The configuration of steps 116 and 154 may then include: the CU provides timing references to the RU. Alternatively or in addition, the RU may obtain and/or maintain the timing reference without signaling from the CU.
Configuration of an RU may include configuring the RU to perform the following functions: a master information block is provided for transmission by the RU. The configuration of steps 116 and 154 may then include: the CU provides the RU with a pre-generated master information block.
Configuration of an RU may include configuring the RU to perform the following functions: a system information block is provided for transmission by an RU. The configuration of steps 116 and 154 may then include: the CU provides the RU with a pre-generated system information block.
After configuring the RU in steps 116 and 154, the RU transitions from the non-autonomous mode of operation to the autonomous mode of operation 156, and the CU transitions from the normal mode of operation to the sleep mode 118. In general, there may be some sort of handshake between the RU and the CU (or at least a configuration complete signal from the RU) before the CU transitions to sleep mode.
During the CU sleep mode 118, the RU is in the autonomous mode of operation 156. As long as the RU or CU does not detect a mode change trigger event, the CU remains in the low power mode of operation and the RU remains in the autonomous mode of operation, as indicated by the "no" path branching from steps 120 and 160, respectively.
If the CU detects a normal operation mode trigger event ("Yes" path out of step 120), the CU proceeds to step 122, where preparation for the CU's normal operation mode and for the RU(s) non-autonomous operation mode is performed at step 122.
The normal operation mode trigger event may include, for example: an interrupt signal is received from one of the one or more RUs, as indicated by signaling 192. Such an interrupt signal may generally be due to the RU detecting a non-autonomous operation mode trigger event in step 160, as will be described in detail below. Alternatively or in addition, the normal operation mode trigger event may include: a trigger signal 191 (e.g., a paging signal) is received from the wireless communication network 101 for a wireless communication device associated with the RU. Such a trigger signal may be received, for example, via a transport network interface. Alternatively or in addition, the normal operation mode trigger event may include detecting that a predetermined time period for the power saving operation mode has elapsed.
If the RU detects a non-autonomous mode of operation trigger event ("Yes" path out of step 160), the RU may send an interrupt signal 192 to the CU to cause the CU to proceed to step 122, at step 122, preparation for the normal mode of operation of the CU and for the non-autonomous mode of operation of the RU(s) is performed.
The non-autonomous operation mode trigger event may, for example, include receiving a random access request from a wireless communication device associated with the RU. Typically, the RU may then send a pre-generated random access grant in conjunction with sending an interrupt signal 192 to the CU. Because the RU is able to send random access grants before the CU leaves sleep mode, the delay requirement before the CU transitions to normal operation mode may be relaxed to some extent. In some embodiments, the delay requirement before the CU transitions to normal operation mode may be relaxed further to some extent if the pre-generated random access grant relates to radio resources as late as possible under applicable standardization.
Alternatively or in addition, the non-autonomous mode of operation triggering event may include: detecting that more pre-generated random access grants are needed, that more pre-generated system information blocks are needed, that more pre-generated master information blocks are needed, and/or that a new timing reference is needed. Then, in response thereto, an interrupt signal 192 may be sent to the CU.
In some embodiments, the non-autonomous operation mode trigger event detected by the RU (the "yes" path out of step 160) is due to the CU detecting a normal operation mode trigger event. The CU may then have continued to step 122 and the non-autonomous operation mode trigger event may be part of the signaling 193 of the CU in step 122. In these embodiments, interrupt signaling 192 may generally be omitted. Examples of such non-autonomous mode of operation triggering events include: paging signals relayed from the CUs are received and/or non-autonomous operation mode configuration signaling is received from the CUs.
Alternatively or in addition, the non-autonomous mode of operation triggering event may include: it is detected that a predetermined time period for the power saving operation mode of the CU has elapsed. In these embodiments, the corresponding time may or may not be maintained at the CU, where the normal operating mode trigger event includes detecting that a predetermined length of time for the power saving operating mode has elapsed, as described above. According to various embodiments, if this type of detection is only at the CU, the signaling 193 may be applicable, if this type of detection is only at the RU, the signaling 192 may be applicable, and if this type of detection is at both the CU and RU, neither signaling 192, 193 may be applicable.
In any case, when a normal operation mode trigger event and/or an autonomous operation mode trigger event has been detected ("yes" path out of steps 120 and 160), the CU proceeds to step 122, and the RU proceeds to step 162.
In step 122, the CU prepares for the normal operation mode 112 by configuring its associated RU(s) for non-autonomous operation, as shown by signaling 194. The non-autonomous operation mode configuration signaling 194 occurs via a respective communication interface of each RU and the non-autonomous operation mode configuration signaling 194 is received by the RU in step 162, wherein the RU is configured accordingly for non-autonomous operation. The configuration of an RU for non-autonomous operation includes: the RU is configured to no longer perform the functions performed by the CU in the normal operating mode as described above. Furthermore, the CU configures itself to perform these operations in preparation for the CU's normal operating mode. In some embodiments, signaling 194 may be omitted, for example, when the RU triggers the CU to switch to normal operation mode.
After configuring the RU in steps 122 and 162, the RU transitions from autonomous to non-autonomous operation mode 152 and the CU transitions from sleep mode to normal operation mode 112. In general, there may be some kind of handshake between the RU and the CU (or at least a mode transition complete signal from the CU) before the RU transitions to the non-autonomous mode of operation.
In some embodiments, the CU can enter a second power saving mode, namely a power off mode 132, from the sleep mode 118. This power saving mode may be used, for example, when the statistics indicate that the traffic conditions tested in step 114 are unlikely to change in the near future. In these embodiments, the (first) CU may configure the other (second) CU to take over the functionality of the (first) CU before entering the shutdown mode, as shown by step 130.
Thus, the first CU may configure the second CU to be able to wake up the first CU (if necessary) by configuring the second CU to control the respective communication interfaces of the one or more RUs, detect a normal operation mode trigger event for the first CU (as compared to step 120), configure each RU for non-autonomous operation in response thereto (as compared to step 122), and cause the first CU to transition from the off mode to the normal operation mode, as shown by step 133.
In some embodiments, the CU can enter the shutdown mode 132 directly from the normal operation mode 112. Then, the second CU may or may not configure RU(s) of the first CU for autonomous operation.
FIG. 2 is a schematic diagram illustrating an example functional partition, according to some embodiments. The example of fig. 2 can be applied to 5G, depending on current or future standardization.
The right side of fig. 2 shows different types of processing; packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) 250, medium Access Control (MAC) and Radio Link Control (RLC) 251, hybrid automatic repeat request (HARQ) 252, forward error correction coding and decoding (FEC) 253, modulation and demodulation (MOD) 254, precoding and equalization 255, resource mapping and demapping 256, antenna processing 257, radio Frequency (RF) processing 258, and antenna interface 259. Arrow 280 represents a downlink processing flow and arrow 290 represents an uplink processing flow.
The lowest functionality of fig. 2 is close to the antenna and typically requires or benefits from dedicated hardware (sometimes referred to as dedicated processor SPP) for efficient processing. Further up in the hierarchy of fig. 2, the need for dedicated hardware is gradually reduced, and at the highest functionality of fig. 2, general purpose hardware processing resources (sometimes referred to as general purpose processor GPP) may be used. Functions close to the antenna also typically require real-time processing with short delays, while higher layer functions have more moderate real-time processing requirements.
The left side indicates different functional divisions between CU and RU; common Public Radio Interface (CPRI) partition 206, partition A205, partition B204, partition C203, partition D202, and partition E201, and functional partitions between RUs and CUs are shown at 271-276. These different partitions are example partitions that may be used in connection with the method of FIG. 1. For example, partition E may be used for the power-off mode of the CU, while partition D may be used for the sleep mode of the CU. It should be noted that these divisions are merely examples, and other divisions, more divisions, or fewer divisions may be employed as appropriate.
Some functions, such as Carrier Aggregation (CA) and coordinated multipoint (CoMP), require centralized processing and coordination among multiple RUs connected to a common CU. This sets the minimum allocation function partition (partition C, B, A, or CPRI) for the CU for such methods.
Thus, when considering the division between CU and RU functions, it should be noted that some functions may be handled on general hardware, and that it may be advantageous to have as many of these functions in the CU as possible in terms of cost and/or sharing. It should also be noted that when a CU serves multiple RUs, certain coordination functions (e.g., CAs) typically need to be deployed in the CU. It should also be noted that sharing multiple functions among CUs (e.g., configuration 276) may place stringent requirements on the interface between the CU and RU(s) in terms of latency and/or aggregate data rate.
Fig. 3 schematically illustrates an example apparatus according to some embodiments, wherein a CU 301 is associated with RU 1 302 through RU N303 via connection 350. Each RU has a time keeping function 304, 305 and is associated with one or more radio front ends (RFICs) 311, 312, 313.
In fig. 3, the CU is in a normal operation mode, while the RU(s) are in an autonomous mode. Thus, uplink processing 320 and downlink processing 330 occur in both CUs and RUs, according to some suitable partitioning and signaling flow via communication interface 310.
Fig. 4 schematically illustrates an example apparatus according to some embodiments, wherein a CU 401 is associated with RU 1 402 to RU N403 via connection 450. Each RU has a time keeping function 404, 405 and is associated with one or more radio front ends (RFICs) 411, 412, 413.
In fig. 4, the CU is in sleep mode, while the RU(s) are in autonomous mode. Thus, uplink processing 420 and downlink processing 430 occur in the RU, and no (or very limited) signaling flows through communication interface 410. To this end, RU(s) are equipped with memory circuits (MEM) 406, 407 to store one or more of: a pre-generated random access grant, a system information block, and a master information block. The time keeping functions 404, 405 may run based on timing references provided or otherwise obtained by the CU in the normal operating mode.
For example, RU(s) may be configured to handle periodic broadcast, periodic random access, periodic rib (radio interface based synchronization) processing and timing adjustment, and/or processing of other external synchronization data (e.g., global navigation satellite system GNSS, precision time protocol PTP, etc.).
Fig. 5 schematically illustrates an example apparatus according to some embodiments, in which CU 1501 is associated with RU 1502 via connection 550 and CU 2508 is associated with RU 2503 via connection 551. Each RU has a time keeping function 504, 505 and a memory circuit (MEM) 506, 507 and is associated with one or more radio front ends (RFICs) 511, 512, 513.
In fig. 5, CU 1 is in sleep mode, while RU 1 is in autonomous mode. Thus, uplink processing 520 and downlink processing 530 occur in RU 1, and no (or very limited) signaling flows through communication interface 510.RU 2 is also in autonomous mode. However, CU 2 is in a shutdown mode and CU 1 has been configured to temporarily control communication with RU 2, the transfer of responsibility from CU 2 to CU 1 being schematically illustrated by switch 560.
Fig. 6 schematically illustrates an example apparatus for a network node according to some embodiments. The example apparatus may be configured, for example, to cause performance of the method steps as described above in connection with fig. 1.
The apparatus includes CU 610 and RU 650 associated via a communication Interface (IF) 690. CU is associated with the rest of the wireless communication network through a network interface (NW IF) 600, while RU is associated with a wireless transceiver (TX/RX) 670 to provide a radio access interface. In various embodiments, transceiver 670 may or may not be included in RU 650.
The CU is adapted to operate in one of a plurality of modes, including a normal operating mode and a power saving operating mode (e.g., a sleep mode and/or a shutdown mode), the normal operating mode defining a plurality of functions to be performed by the CU in the normal operating mode.
The CU includes a Controller (CNTR) 620 configured such that (when the CU is in a normal operation mode): determining that a traffic load associated with one or more RUs meets a power saving operation criterion; via the communication interface 690, the RUs are configured for autonomous operation (whereby each RU is configured to perform at least one of a plurality of functions); and transitioning from the normal operating mode to the power saving operating mode.
This determination may be performed, for example, by a determination circuit (e.g., determiner DET) 616, which may be included in or otherwise associated with the CU. This configuration may be performed, for example, by a configuration circuit (e.g., a configurator CONF) 614, which may be included in or otherwise associated with the CU. The MODE conversion may be performed, for example, by a MODE control circuit (e.g., MODE controller MODE) 612, which may be included in or otherwise associated with the CU.
The RU is adapted to operate in one of a plurality of modes, including a non-autonomous mode (corresponding to a normal operation mode of the CU) and an autonomous mode (corresponding to a power saving operation mode of the CU).
The RU includes a Controller (CNTR) 660 configured such that (when the RU is in non-autonomous mode): receiving autonomous operation mode configuration signaling from the CU via the respective communication interface 690; configuring the RU to perform at least one function of a plurality of functions performed by the CU in a normal operating mode; and transitioning from the non-autonomous mode of operation to the autonomous mode of operation.
This configuration may be performed, for example, by a configuration circuit (e.g., a configurator CONF) 654, which may be included in or otherwise associated with the RU. The MODE conversion may be performed, for example, by a MODE control circuit (e.g., MODE controller MODE) 652, which may be included in or otherwise associated with the RU.
The controllers 620, 660 may also be configured to cause the other steps explained above in connection with fig. 1 to be performed. For example, the controller 620 may be configured such that (when the CU is in a power saving mode of operation): detecting a normal operation mode trigger event; transitioning from the power saving mode of operation to a normal mode of operation; and configuring each RU for non-autonomous operation, and controller 660 may be configured such that (when the RU is in autonomous operation mode): detecting a non-autonomous mode of operation trigger event; and transitioning from the autonomous mode of operation to the non-autonomous mode of operation, whereby the RU is not configured to perform any of a plurality of functions.
Thus, in accordance with various embodiments, a method for a power efficient base station is provided while enabling continuous service. When there is no traffic, there is typically very limited transmission/reception (e.g., in a 5G reduced signaling architecture), and the remaining activity is typically periodic, with known (or at least predictable) content and time. The processing load in the system will therefore typically be small when not servicing any traffic. Locally addressing these transmissions/receptions using the available resources in the RU will allow the CUs typically involved in the processing for these functions to implement longer and deeper sleep modes. This is especially prominent if these functions serve many radio units (e.g. as in the C-RAN architecture). This approach also allows for an efficient sleep mode for the high speed interface between RU and CU, providing additional power savings, which is especially prominent when CU/RU(s) are distributed.
Taking 5G as an example, when not serving traffic, the remaining mandatory parts may include:
-transmitting a broadcast signal:
the o-Synchronization Signal (SS), in case the New Radio (NR) SS is divided into a primary (P) part and a secondary (S) part, may be denoted as NR-PSS and NR-SSs.
o a master information block (MIB, or NR-MIB) transmitted in a first physical broadcast channel (which may be denoted as new radio first physical broadcast channel NR-PBCH 1).
o system information block (SIB or NR-SIB). SIBs in NR may be transmitted in a second physical broadcast channel (NR-PBCH 2) or may be scheduled by an NR physical downlink control channel (NR-PDCCH) and carried by an NR physical downlink shared channel (NR-PDSCH).
The timing and content of these NR idle mode broadcast signals and channels are known (or predictable) by the base station.
-listening for UE random access requests and on-demand system information requests:
o timing and data are known and during low traffic scenarios the likelihood of any UE requesting access is relatively low.
-receiving and transmitting radio interface based synchronization (rib in 3GPP terminology):
o-timing and data are known. During low traffic scenarios, the temperature dynamics are small, which causes small drift of the internal oscillator, thereby reducing the RIBS frequency.
In order to reduce overall power consumption, some embodiments propose to have the RU also handle regular, periodic, known (or predictable) transmissions and receptions that are typically handled by the CU. Thus, longer (and deeper) sleep mode periods of the CUs and interfaces are achieved.
A key characteristic of NR is multi-user multiple input multiple output (MU-MIMO). A radio unit supporting user space separation requires an antenna system with a large number of individually controllable antenna units. Distribution of user data over different antenna units is preferably done in the RU, requiring a large amount of digital signal processing power to be provided in the RU. With low traffic load, a large amount of processing power can therefore typically be provided in the RU.
Embodiments include altering the broadcasted system information to limit the number of possible random access preambles, thereby reducing the processing required in the RU. These changes may include, but are not limited to:
stopping sending PRACH (physical random access channel) configuration in the broadcasted system information and instead indicating that this information is available on demand.
-increasing the time between PRACH occasion windows.
Embodiments include preparing PRACH response messages (or portions of these messages) in advance and storing them locally in the RU, so that the baseband has a longer time to reactivate before it needs to be fully operational. For example:
-for on-demand System Information (SI), requesting pre-calculation of the requested SI, and transmitting the requested SI from the RU upon request.
Embodiments include precalculating a Random Access Response (RAR) message for normal PRACH operation. Thus, the UE can receive the first uplink grant directly from the RU.
Embodiments also include a method for causing an RU to autonomously process transmission of periodic broadcast information by:
-updating the predictable dynamic information (e.g. timing information) in the periodic broadcast transmissions on its own regularly, or
Using pre-calculated values pre-stored in memory, these pre-calculated values may be updated as needed or at a low frequency, for example.
The described embodiments and their equivalents may be implemented in software or hardware or a combination thereof. Embodiments may be performed by general purpose circuitry. Examples of general purpose circuits include Digital Signal Processors (DSPs), central Processing Units (CPUs), coprocessor units, field Programmable Gate Arrays (FPGAs), and other programmable hardware. Alternatively or in addition, embodiments may be performed by special purpose circuits, such as an Application Specific Integrated Circuit (ASIC). The general purpose circuitry and/or the dedicated circuitry may be associated with or included in, for example, an apparatus (e.g., a central unit, a remote unit, or a network node).
Embodiments may occur within an electronic device (e.g., a central unit, a remote unit, or a network node) comprising an arrangement, circuitry, and/or logic according to any of the embodiments described herein. Alternatively or additionally, an electronic device (e.g., a central unit, a remote unit, or a network node) may be configured to perform the method according to any of the embodiments described herein.
According to certain embodiments, a computer program product includes a computer readable medium, such as Universal Serial Bus (USB) memory, a plug-in card, an embedded drive, or Read Only Memory (ROM). Fig. 7 illustrates an example computer-readable medium in the form of a Compact Disk (CD) ROM 700. The computer readable medium has stored thereon a computer program comprising program instructions. The computer program can be loaded into a data Processor (PROC) 720, which data processor 720 can be comprised in a central unit, a remote unit, or a network node 710, for example. When loaded into a data processing unit, the computer program may be stored in a memory (MEM) 730 associated with or comprised in the data processing unit. According to some embodiments, the computer program may, when loaded into and executed by a data processing unit, cause performance of the method steps described in accordance with any of the methods shown, for example, in fig. 1 or otherwise described herein.
Reference has been made herein to various embodiments. However, those skilled in the art will recognize that many variations of the described embodiments will still fall within the scope of the claims. For example, method embodiments described herein disclose an example method by steps performed in a particular order. It should be recognized, however, that these sequences of events may occur in another order without departing from the scope of the claims. Furthermore, certain method steps may be performed in parallel even though they have been described as being performed in sequence.
In the same way, it should be noted that in the description of the embodiments, the division of the functional blocks into specific units is in no way intended to be limiting. Rather, these divisions are merely examples. The functional blocks described herein as one unit may be divided into two or more units. Furthermore, functional blocks described herein as being implemented as two or more units may be combined into fewer (e.g., a single) units.
It is therefore to be understood that the details of the described embodiments are presented by way of example only and that all variations falling within the scope of the claims are intended to be included therein.

Claims (26)

1. A method for a centralized unit, CU, of a wireless communication network, wherein the CU is associated with each of one or more remote units, RU, of the wireless communication network via a respective communication interface, wherein the CU is adapted to operate in one of a plurality of modes, including at least a normal operation mode and a power saving operation mode, and wherein the normal operation mode defines a plurality of base station functions to be performed by the CU,
The method comprises the following steps: when the CU is in the normal mode of operation (112),
determining (114) that a traffic load associated with the one or more RUs meets a power saving operation criterion, wherein the traffic load is related to a wireless communication device, WCD, associated with the one or more RUs;
configuring (116) each of the RUs for autonomous operation via the respective communication interface, whereby each of the RUs is configured to perform at least one of the plurality of base station functions defined for the CU in the normal operation mode; and
the CU is transitioned from the normal operating mode to the power saving operating mode (118, 132).
2. The method of claim 1, wherein the at least one of the plurality of base station functions comprises one or more of:
-responding to a random access request from the WCD by issuing a random access grant for transmission;
-responding to a WCD's need for system information by providing a block of system information for transmission;
-providing a synchronization signal for transmission;
-providing a main information block for transmission; and
-providing a system information block for transmission.
3. The method of any of claims 1-2, wherein the power saving operation criteria includes that none of the one or more RUs is associated with a WCD in connected mode.
4. The method of any of claims 1-2, wherein configuring each RU for autonomous operation comprises at least one of:
-providing a pre-generated random access grant to the RU;
-providing a pre-generated system information block to the RU;
-providing a timing reference to the RU; and
-providing the RU with a pre-generated master information block.
5. The method of any of claims 1-2, wherein the power saving mode of operation is a sleep mode (118).
6. The method of claim 5, the method further comprising: when the CU is in the power save mode of operation,
detecting (120) a normal operation mode trigger event;
configuring (122) each of the RUs for non-autonomous operation via the respective communication interfaces; and
transition from the power saving mode of operation to the normal mode of operation (112).
7. The method of claim 6, wherein detecting the normal operation mode trigger event comprises at least one of:
-receiving an interrupt signal from one of the one or more RUs;
-receiving a paging signal from the wireless communication network; and
-detecting that a predetermined time period for said power saving operation mode has elapsed.
8. The method of any of claims 1-2, wherein the power saving mode of operation is a shutdown mode (132).
9. The method of claim 8, wherein the CU is a first CU, the method further comprising configuring (130) a second CU to:
controlling respective communication interfaces of the one or more RUs;
detecting a normal operation mode trigger event for the first CU;
configuring each of the RUs for non-autonomous operation via the respective communication interfaces; and
causing the first CU to transition from the shutdown mode to the normal operation mode.
10. A method for a remote unit, RU, of a wireless communication network, wherein the RU is associated with a centralized unit, CU, of the wireless communication network via a communication interface, wherein the RU is adapted to operate in one of a plurality of modes including at least a non-autonomous mode of operation associated with a normal mode of operation of the CU and an autonomous mode of operation associated with a power save mode of operation of the CU, and wherein the normal mode of operation defines a plurality of base station functions to be performed by the CU,
The method comprises the following steps: when the RU is in the non-autonomous mode of operation (152),
-receiving (154) autonomous operation mode configuration signaling from the CU via the communication interface;
configuring (154) the RU to perform at least one of the plurality of base station functions defined for the CU in the normal operating mode; and
the RU is transitioned from the non-autonomous mode of operation to the autonomous mode of operation (156).
11. The method of claim 10, wherein the at least one of the plurality of base station functions comprises one or more of:
-responding to a random access request from a wireless communication device WCD by issuing a random access grant for transmission;
-responding to a WCD's need for system information by providing a block of system information for transmission;
-providing a synchronization signal for transmission;
-providing a main information block for transmission; and
-providing a system information block for transmission.
12. The method of any of claims 10 to 11, wherein the configuration signaling comprises at least one of:
-a pre-generated random access authorization;
-a pre-generated system information block;
-a timing reference; and
-a pre-generated master information block.
13. The method of any one of claims 10 to 11, the method further comprising: when the RU is in the autonomous mode of operation (156),
detecting (160) a non-autonomous mode of operation trigger event; and
transition from the autonomous mode of operation to the non-autonomous mode of operation (152), whereby the RU is not configured (162) to perform any of the plurality of base station functions.
14. The method of claim 13, wherein detecting the non-autonomous operation mode trigger event comprises at least one of:
-receiving a random access request from a wireless communication device associated with the RU;
-detecting that more pre-generated random access grants are needed;
-detecting that more pre-generated system information blocks are needed;
-detecting that more pre-generated main information blocks are needed; and
-detecting that a new timing reference is required;
and wherein the method further comprises: and sending an interrupt signal for triggering a normal operation mode of the CU to the CU.
15. The method of claim 13, wherein detecting the non-autonomous operation mode trigger event comprises at least one of:
-receiving a paging signal from the CU;
-receiving non-autonomous operation mode configuration signaling from the CU via the communication interface; and
-detecting that a predetermined time period for the autonomous mode of operation has elapsed.
16. A non-transitory computer readable medium (700) having thereon a computer program comprising program instructions, the computer program being loadable into a data-processing unit and configured to cause execution of the method according to any of claims 1 to 15 when the computer program is run by the data-processing unit.
17. An apparatus for a centralized unit, CU, of a wireless communication network, wherein the CU is associated with each of one or more remote units, RUs, of the wireless communication network via a respective communication interface, wherein the CU is adapted to operate in one of a plurality of modes, including at least a normal operating mode and a power saving operating mode, and wherein the normal operating mode defines a plurality of base station functions to be performed by the CU,
the apparatus comprises a controller (620), the controller (620) being configured to cause, when the CU is in the normal operation mode:
Determining that a traffic load associated with the one or more RUs meets a power saving operation criterion, wherein the traffic load relates to a wireless communication device, WCD, associated with the one or more RUs;
configuring each of the RUs for autonomous operation via the respective communication interfaces, whereby each of the RUs is configured to perform at least one of the plurality of base station functions defined for the CU in the normal operation mode; and
the CU is transitioned from the normal operating mode to the power save operating mode.
18. The apparatus of claim 17, wherein the power saving mode of operation is a sleep mode.
19. The apparatus of claim 18, wherein the controller is further configured to cause, when the CU is in the power save mode of operation:
detecting a normal operation mode trigger event;
transitioning from the power saving mode of operation to the normal mode of operation; and
each of the RUs is configured for non-autonomous operation via the respective communication interface.
20. The apparatus of claim 17, wherein the power saving mode of operation is a shutdown mode.
21. The apparatus of claim 20, wherein the CU is a first CU, the controller is further configured to cause a second CU to be configured to:
Controlling respective communication interfaces of the one or more RUs;
detecting a normal operation mode trigger event for the first CU;
configuring each of the RUs for non-autonomous operation via the respective communication interfaces; and
causing the first CU to transition from the shutdown mode to the normal operation mode.
22. An apparatus for a remote unit, RU, of a wireless communication network, wherein the RU is associated with a centralized unit, CU, of the wireless communication network via a communication interface, wherein the RU is adapted to operate in one of a plurality of modes including at least a non-autonomous mode of operation associated with a normal mode of operation of the CU and an autonomous mode of operation associated with a power saving mode of operation of the CU, and wherein the normal mode of operation defines a plurality of base station functions to be performed by the CU,
the apparatus includes a controller (660), the controller (660) configured to cause, when the RU is in the non-autonomous mode of operation:
receiving autonomous operation mode configuration signaling from the CU via the communication interface;
configuring the RU to perform at least one of the plurality of base station functions defined for the CU in the normal operating mode; and
The RU is transitioned from the non-autonomous mode of operation to the autonomous mode of operation.
23. The apparatus of claim 22, wherein the controller is further configured to cause, when the RU is in the autonomous mode of operation:
detecting a non-autonomous mode of operation trigger event; and
the method further includes transitioning from the autonomous mode of operation to the non-autonomous mode of operation, whereby the RU is not configured to perform any of the plurality of base station functions.
24. A centralized unit CU comprising the apparatus of any one of claims 17 to 21.
25. A remote unit RU comprising the apparatus according to any of claims 22 to 23.
26. A network node comprising at least one of: the centralized unit of claim 24, and one or more remote units of claim 25.
CN201780094932.9A 2017-09-27 2017-09-27 Network Node Power Control Active CN111133802B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311058464.3A CN117082601A (en) 2017-09-27 2017-09-27 Method and apparatus for network node power control

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/074492 WO2019063072A1 (en) 2017-09-27 2017-09-27 Network node power control

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202311058464.3A Division CN117082601A (en) 2017-09-27 2017-09-27 Method and apparatus for network node power control

Publications (2)

Publication Number Publication Date
CN111133802A CN111133802A (en) 2020-05-08
CN111133802B true CN111133802B (en) 2023-09-01

Family

ID=59969177

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202311058464.3A Pending CN117082601A (en) 2017-09-27 2017-09-27 Method and apparatus for network node power control
CN201780094932.9A Active CN111133802B (en) 2017-09-27 2017-09-27 Network Node Power Control

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202311058464.3A Pending CN117082601A (en) 2017-09-27 2017-09-27 Method and apparatus for network node power control

Country Status (4)

Country Link
US (2) US11044667B2 (en)
EP (1) EP3689037B1 (en)
CN (2) CN117082601A (en)
WO (1) WO2019063072A1 (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11343846B2 (en) * 2020-02-04 2022-05-24 Altiostar Networks, Inc. Status messaging protocol
US20230170973A1 (en) * 2020-05-08 2023-06-01 Telefonaktiebolaget Lm Ericsson (Publ) Versatile aas receiver
CN112637960B (en) * 2020-12-23 2023-10-17 沈阳农业大学 GNSS-based network node power control method
CN113613319B (en) * 2021-08-19 2023-11-21 联想(北京)有限公司 Communication processing method, system and communication node
WO2024062806A1 (en) * 2022-09-22 2024-03-28 日本電気株式会社 Ru device, control device, method, and program
WO2024119302A1 (en) * 2022-12-05 2024-06-13 Telefonaktiebolaget Lm Ericsson (Publ) Energy saving for radio

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1689247A (en) * 2002-06-27 2005-10-26 高通股份有限公司 Adjusting transmit power in a wireless communication system
WO2011157116A1 (en) * 2010-12-31 2011-12-22 华为技术有限公司 Lithium battery module parallel using method and system
CN102648642A (en) * 2009-11-20 2012-08-22 高通股份有限公司 Methods and apparatus for assisting in network discovery
CN103379593A (en) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 Terminal electricity-saving method, terminal electricity-saving device and network side electricity-saving device
WO2014182236A1 (en) * 2013-05-10 2014-11-13 Telefonaktiebolaget L M Ericsson (Publ) Power control of uplink control channels in heterogeneous networks
CN106797641A (en) * 2014-06-09 2017-05-31 艾尔瓦纳有限合伙公司 Identical resource is dispatched in radio access network

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4018972B2 (en) * 2002-11-18 2007-12-05 Ｎｅｃインフロンティア株式会社 Wireless communication system
US7756548B2 (en) 2005-09-19 2010-07-13 Qualcomm Incorporated Methods and apparatus for use in a wireless communications system that uses a multi-mode base station
US8576759B2 (en) * 2008-07-11 2013-11-05 Marvell World Trade Ltd. Partial power save mode for access points during device discovery
JP5303752B2 (en) 2008-07-11 2013-10-02 マーベル ワールド トレード リミテッド Power saving mode at the access point
EP2157824A1 (en) 2008-08-18 2010-02-24 Nokia Siemens Networks OY Network node, network and a method for waking up a network node
KR102221565B1 (en) 2013-08-22 2021-02-26 인터디지털 씨이 페턴트 홀딩스 Wakeup message for a digital television system
WO2017080436A1 (en) * 2015-11-09 2017-05-18 Intel IP Corporation System and method for beamed reference signal with hybrid beam
US10536878B2 (en) * 2017-03-24 2020-01-14 Mediatek Inc. User equipment and methods for PDCP duplication in 5G RAN

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1689247A (en) * 2002-06-27 2005-10-26 高通股份有限公司 Adjusting transmit power in a wireless communication system
CN102648642A (en) * 2009-11-20 2012-08-22 高通股份有限公司 Methods and apparatus for assisting in network discovery
WO2011157116A1 (en) * 2010-12-31 2011-12-22 华为技术有限公司 Lithium battery module parallel using method and system
CN103379593A (en) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 Terminal electricity-saving method, terminal electricity-saving device and network side electricity-saving device
WO2014182236A1 (en) * 2013-05-10 2014-11-13 Telefonaktiebolaget L M Ericsson (Publ) Power control of uplink control channels in heterogeneous networks
CN105230087A (en) * 2013-05-10 2016-01-06 瑞典爱立信有限公司 The power of the uplink control channel in heterogeneous network controls
CN106797641A (en) * 2014-06-09 2017-05-31 艾尔瓦纳有限合伙公司 Identical resource is dispatched in radio access network

Also Published As

Publication number Publication date
US20200413331A1 (en) 2020-12-31
US11044667B2 (en) 2021-06-22
EP3689037A1 (en) 2020-08-05
CN117082601A (en) 2023-11-17
US20210282086A1 (en) 2021-09-09
WO2019063072A1 (en) 2019-04-04
CN111133802A (en) 2020-05-08
US11622324B2 (en) 2023-04-04
EP3689037B1 (en) 2021-07-07

Similar Documents

Publication Publication Date Title
CN111133802B (en) Network Node Power Control
JP7443334B2 (en) Methods of transmitting and receiving signals, network devices and terminals
EP3338510B1 (en) Prose relay delay reduction
EP3639573B1 (en) Wireless communications system, communications device and wireless network infrastructure
WO2019029538A1 (en) Scheduling request transmitting method, scheduling request processing method and related device
JP7074219B2 (en) User equipment, base station, user equipment method, and base station method
CN115088370A (en) Method and apparatus for operating resource selection and HARQ operation in NR V2X
CN110958673A (en) Method for determining activation state of secondary cell and user equipment
JP7498850B2 (en) Multiple DRX Settings for D2D Communication
JP2018535565A5 (en)
US20230300795A1 (en) Apparatuses and methods for downlink notification monitoring
JP2020510352A (en) User node, network node and method for allocating and using resources for control signals
US20220191788A1 (en) Permissible transmission gap assistance by ue
JP2024511097A (en) User equipment and base stations involved in small data transmission
CN110945922B (en) Method, device, terminal and storage medium for acquiring pattern parameters of power saving signal
WO2017205999A1 (en) Data transmission method, device and system
CN114785376B (en) Frequency-voltage pre-configuration method and related device
RU2799488C1 (en) Method, device for indicating the state of channels in the unlicensed spectrum and information carrier
CN117835433A (en) Communication method and device
CN106922001B (en) Method and device for contention-based communication and corresponding communication system
CN113228728A (en) Method, apparatus and system for saving energy in wireless communications
CN117440477A (en) Communication method and device
CN118301749A (en) Communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant