Enabling radio base station for assisted services

Abstract

A method, system, and device are disclosed. A management node (24) configured to communicate with a grid operator and with a plurality of RBSs (16) is provided. Each RBS of the plurality of RBS (16) is configured to be switchable between power from the grid and power from a respective plurality of backup battery cells (59) associated with the RBS (16). The management node (24) is configured to determine a primary subset of the plurality of RBSs (16) to participate in at least one FCR event occurring during a predefined time interval, and to determine a backup subset of the plurality of RBSs (16) each configured to participate in the at least one FCR event in place of a failure of a respective one of the primary subset of the plurality of RBSs (16).

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular, to enabling provision of auxiliary services (eg, Frequency Containment Reserve (FCR) events / services) by a radio base station in a wireless communications network. Background Art

[0002] Fifth Generation New Radio (5G NR) services and high performance 5G enabled radio units open up multiple opportunities for businesses such as utilities and mobile network operators (MNOs), enabling various business-to-business (B2B) operations. One aspect of future business is the sustainability approach of companies related to their operations, e.g., aiming to reduce negative environmental impacts, negative social impacts, etc. of these operations. Sustainability can be enabled / improved by using new communication technologies, requirements and capabilities such as 5G NR.

[0003] Utility operators, including transmission system operators (TSOs) and distribution system operators (DSOs), face the challenge of improving their sustainability while maintaining efficient operation of the grids they operate. In addition, the infrastructure of the grid (e.g., construction of power lines and substations) often has longer cycles and investments when compared to other vertical businesses (such as telecommunications).

[0004] Additionally, while the installed capacity of renewable energy sources in the grid tends to increase over time, user demand and energy consumption also increase simultaneously. Since renewable energy sources cannot be predicted, the grid may sometimes be unstable in terms of the balance between generation and demand (consumption), for example, due to the stochastic nature of these power sources. Planning / operating the grid in an efficient and stable manner for delivering energy to users / customers with high availability / reliability while improving sustainability is a challenging task for utility operators.

[0005] To help alleviate this problem, utilities have been proposed to encourage and invest in ancillary services (AS). Ancillary services are transactions of energy performed by selected electricity customers (e.g., participating business customers) that are affected by increasing or decreasing participating customers' energy consumption in response to grid requests, where special (e.g., monetary) incentives may be provided to those customers who participate. These ancillary services support the grid to help maintain the proper balance between generation and consumption and therefore improve grid stability.

[0006] One of the ancillary services is the Frequency Control Reserve (FCR) service. In the FCR service, active operating reserves (eg of participating customers) are used to stabilize grid frequency deviations (fluctuations) from its nominal value (eg 50 Hz or 60 Hz).

[0007] The FCR service is divided into two different services, named: Frequency Control Reserve for Normal Operation (FCR-N) and Frequency Control Reserve for Disturbance (FCR-D). These reserves (also referred to as FCR capacity) can be auctioned by utilities and participating customers on a market basis on an hourly (or other time period) basis and with a predefined minimum power bid (e.g., the auction can take place before the day when FCR capacity is needed (which may be different in each country)).

[0008] Additionally, in order to participate in the bidding process, some general requirements may need to be met by the participating customer (such as prequalification of the customer's equipment) to obtain approval from the utility company prior to participation. These requirements may vary by market / location / region / etc. Table 1 below is an example requirement for participating in an electricity market, in this case the Swedish electricity market:

[0009]

[0010]

[0011] Table 1 - Characteristics of FCR-N and FCR-D for the Swedish market.

[0012] As described in Table 1, the FCR-N service requires an activation time of 63% within 60 seconds and 100% within 3 minutes, i.e., within 60 seconds, the participating entity / customer must reduce (or increase, depending on configuration / signaling) its power consumption by 63% within 60 seconds and reduce (or increase, depending on configuration / signaling) its power consumption by 100% within 3 minutes.

[0013] Existing systems consider enabling FCR energy services for utilities with relevant components and functions (such frequency monitoring), and when using battery energy storage systems, such systems utilize various strategies for ancillary services. For example, in some power systems, technical requirements for FCR do not allow the battery storage system to be controlled in a manner other than based on frequency. Therefore, control mechanisms such as restoring the state of charge (SoC) have been proposed that comply with such regulation and use the lifeline model of the battery storage system to maximize the profit of the battery storage system.

[0014] Existing systems have considered optimal bidding strategies for battery storage in electricity markets. Battery storage can improve its profitability by providing fast regulation services under a performance-based regulation mechanism that better utilizes the fast ramping capability of the battery. However, battery life may be degraded by frequent charge-discharge cycles, especially when providing fast regulation services. It is profitable for battery storage to extend its service life by restricting its operating strategy to some extent. Therefore, incorporating a battery cycle life model into a profit maximization model to determine the optimal bid in terms of day-ahead energy, spinning reserve, and regulation markets can improve the profitability of such operations.

[0015] Existing systems consider determining suitable strategies that allow battery energy storage system owners to maximize profits when participating in the electricity market. For example, a mixed integer linear programming (MILP) optimization problem has been proposed for determining the optimal operation of a battery energy storage system. The formula includes a battery degradation model based on an upper piecewise linear approximation method. However, existing systems may be too expensive to implement, which reduces profitability.

[0016] Therefore, existing systems for battery energy storage may not be optimally suited for providing ancillary services to utilities. Summary of the invention

[0017] In an embodiment of the present disclosure, multiple entities of radio base stations / network nodes (including local batteries) in one or more clusters may be coordinated for auxiliary services / FCR, where the batteries are also used as radio base stations / network node backup batteries and not just for AS (e.g. FCR) services, and where changes in radio traffic load (and therefore power consumption at the radio base station (RBS)) may be dynamic.

[0018] Embodiments of the present disclosure contemplate generating different profiles across multiple radio base stations (RBSs) to control multiple batteries, efficiently aggregating RBSs (e.g., based on power level, battery degradation (e.g., battery life cycle), cost performance, physical proximity, etc.), selecting the best RBS to participate, and selecting one or more spare RBSs as backup.

[0019] Embodiments of the present disclosure utilize a control strategy to efficiently aggregate RBSs in response to FCR requests. A coordination algorithm is disclosed for controlling a radio access network (RAN) when participating in FCR services. In some embodiments, the goal of the MNO / CSP may be to maximize profits while meeting FCR minimum requirements and maintaining the quality of service (QoS) of the mobile network. In addition, battery degradation and associated costs are taken into account to improve system accuracy, reliability, and profitability.

[0020] In some embodiments of the present disclosure, an optimization algorithm such as, for example, the Dantzig-Wolfe decomposition method for mixed integer linear programming (MILP) may be utilized. For example, for each bidding period (e.g., bidding hour), the most efficient group(s) / the most efficient cluster(s) of RBSs are selected, such as forming a primary cluster and a backup cluster (for redundant capacity). In some embodiments, the most efficient group(s) / the most efficient cluster(s) may be determined by comparing one or more characteristics associated with each group / cluster.

[0021] In some embodiments of the present disclosure, after one or more clusters are selected, a synchronization signal with various profiles (e.g., operation settings) is sent to each cluster in the system (e.g., to one or more RBSs in each cluster) for activation. The various operations based on the profiles can improve coordination and efficiency when activating power infrastructure equipment (e.g., power supply units (PSUs)).

[0022] In some embodiments of the present disclosure, transmission of a synchronization signal including an AS profile to the RBS of each cluster occurs before an active hour, the AS profile optionally including a profile control indicating at least one of: synchronization of the RBS in response to each requirement from a network management unit for executing the AS profile, and local execution on at least one local controller for executing at least one power modification process based on at least one threshold indicated by the AS profile.

[0023] According to one aspect of the present disclosure, a management node configured to communicate with a grid operator and with a plurality of RBSs is provided. Each of the plurality of RBSs is configured to be switchable between power from the grid and power from a corresponding plurality of backup battery units associated with the RBS. The management node is configured to: determine a primary subset of a plurality of RBSs to participate in at least one frequency control reserve FCR event occurring during a predefined time interval; determine a backup subset of a plurality of RBSs each configured to participate in at least one FCR event in place of a failure of a corresponding one of the primary subsets of the plurality of RBSs; cause the transmission of a synchronization signal with an operational setting to the primary subset and the backup subset of the plurality of RBSs, wherein the operational setting is associated with participating in at least one FCR event; and during an activation period, cause the transmission of an activation signal to at least one of the primary subsets of the plurality of RBSs, the activation signal being configured to cause the RBS to modify its power consumption based on the synchronization signal to participate in at least one FCR event.

[0024] According to one aspect of the present disclosure, there is provided an RBS in communication with a management node. The RBS is configured to be switchable between power from a power grid and power from a plurality of backup battery units associated with the RBS. The radio station includes a processing circuit configured to: receive a synchronization signal with an operation setting associated with a primary subset and a backup subset of a plurality of RBSs forming a cluster, wherein the operation setting is associated with participating in at least one frequency control reserve FCR event; during an activation period, receive an activation signal configured to cause the RBS to modify its power consumption based on the synchronization signal in response to the activation signal; and modify the power consumption of the RBS to participate in at least one FCR event based on the synchronization signal and the activation signal.

[0025] According to another aspect of the present disclosure, a method implemented by a management node configured to communicate with a grid operator and with a plurality of RBSs is provided. Each of the plurality of RBSs is configured to be switchable between power from the grid and power from a corresponding plurality of backup battery units associated with the RBS. A primary subset of the plurality of RBSs to participate in at least one frequency control reserve FCR event occurring during a predefined time interval is determined. A backup subset of the plurality of RBSs each configured to participate in at least one FCR event in place of a failure of a corresponding one of the primary subset of the plurality of RBSs is determined. Transmission of a synchronization signal with an operational setting to the primary subset and the backup subset of the plurality of RBSs is facilitated, wherein the operational setting is associated with participation in at least one FCR event. During an activation period, transmission of an activation signal to at least one of the primary subset of the plurality of RBSs is facilitated, wherein the activation signal is configured to facilitate the RBS to modify its power consumption based on the synchronization signal to participate in at least one FCR event.

[0026] According to another aspect of the present disclosure, a method implemented by an RBS in communication with a management node is provided. The RBS is configured to be switchable between power from a power grid and power from a plurality of backup battery units associated with the RBS. A synchronization signal with an operational setting associated with a primary subset and a backup subset of a plurality of RBSs forming a cluster is received, wherein the operational setting is associated with participating in at least one frequency control reserve (FCR) event. During an activation period, an activation signal is received, the activation signal being configured to cause the RBS to modify its power consumption based on the synchronization signal in response to the activation signal. The power consumption of the RBS is modified based on the synchronization signal and the activation signal to participate in at least one FCR event.

[0027] Some embodiments therefore advantageously provide methods, systems, and apparatus for enabling frequency control functionality in a telecommunications network. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] A more complete understanding of the present embodiments and its attendant advantages and features will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0029] Figure 1 is a schematic diagram of an example network architecture according to the principles of the present disclosure;

[0030] Figure 2 is a schematic diagram illustrating an example network architecture of a communication system connected to a management node via an intermediate network according to the principles of the present disclosure;

[0031] Figure 3 is a flow chart illustrating an example method for transmitting user data from a management node implemented in a communication system including a management node, an RBS / network node, and a wireless device according to some embodiments of the present disclosure;

[0032] Figure 4 is a flow chart illustrating an example method for receiving user data at a management node implemented in a communication system including a management node, an RBS / network node, and a wireless device according to some embodiments of the present disclosure;

[0033] Figure 5 is a flow chart illustrating an example method for receiving user data at a management node implemented in a communication system including a management node, an RBS / network node, and a wireless device according to some embodiments of the present disclosure;

[0034] Figure 6 is a flow chart illustrating an example method for receiving user data at a management node implemented in a communication system including a management node, an RBS / network node, and a wireless device according to some embodiments of the present disclosure;

[0035] Figure 7 is a flow chart of an example process in an RBS for providing auxiliary services based on a control signal received from a management node according to some embodiments of the present disclosure;

[0036] Figure 8 is a flowchart of another example process in an RBS according to some embodiments of the present disclosure;

[0037] Fig. 9 is a flow chart of an example process in a management node for managing provision of auxiliary services by multiple RBSs according to some embodiments of the present disclosure;

[0038] Fig.10 is a flowchart of another example process in a management node according to some embodiments of the present disclosure;

[0039] Fig.11is a schematic diagram of an RBS in normal operation, FCR-up regulation operation, and FCR-down regulation operation according to an embodiment of the present disclosure;

[0040] Fig.12 is a schematic diagram of an example network architecture according to some embodiments of the present disclosure;

[0041] Fig.13 is a flow chart of an example optimization model workflow according to some embodiments of the present disclosure;

[0042] Fig.14 is a schematic diagram of an example network including a primary cluster and a backup cluster according to some embodiments of the present disclosure;

[0043] Fig.15 is a flow chart of an example solution according to some embodiments of the present disclosure;

[0044] Fig.16 is a table of example configurations generated in an optimization model for bidding according to some embodiments of the present disclosure;

[0045] Fig.17A , 17B , 17C and 17D are timing diagrams of example operations according to some embodiments of the present disclosure;

[0046] Fig.18 is a schematic diagram of an example network architecture according to some embodiments of the present disclosure; and

[0047] Fig.19 is a graph depicting example latency measurements in an RBS according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0048] As described above, existing systems for battery energy storage may not be suitable for providing ancillary services to utilities. For example, participating customers (such as communication service providers (CSPs) and / or mobile network operators (MNOs)) may be potential candidates for providing AS / FCR services. Current network deployments (such as 4G, 5G, etc.) may allow CSPs to utilize network assets (such as radio base stations, network nodes, etc.) including local energy storage (e.g., batteries) and operating network manager systems to enable the provision of various ancillary services to the grid. Given the rapid response capabilities of batteries, such power sources may be suitable for providing FCR. By participating, CSPs can expand their business to new industries and reduce their energy operating costs by providing ancillary services.

[0049] Many MNOs and Utilities face challenges and require new technologies and approaches to enable sustainable operation of their assets. Ancillary services enhance the sustainability of Utilities while enabling new revenues for MNOs by leveraging existing equipment / batteries without expensive investments in separate battery energy storage systems.

[0050] Implementing ancillary services, such as FCR services, presents several challenges to telecommunications operators in efficiently orchestrating multiple sites to participate in the ancillary services.

[0051] The battery energy storage unit of the Radio Base Station (RBS) has energy constraints and may therefore not be able to provide FCR if the State of Charge (SoC) limit is reached and may therefore not be able to participate during a regulation request (i.e. when the FCR service is activated). Furthermore, and within the first constraint, the energy storage unit may have to be restored to an appropriate level in order to be able to attend to future requests (ensuring the agreed FCR capacity), while failure to comply with grid requests may result in penalties.

[0052] Prior to the bidding process (e.g., FCR auction), in order to participate in the FCR service, and within the second constraint, a set of RBSs / network nodes may need to be identified and selected that meet all FCR service requirements (such as the example requirements of Table 1), while maximizing the profit of the MNO. Additionally, during the bidding period (e.g., bidding hour) and during the AS / FCR service, the operation of the activated RBSs must be maintained to operate with minimal or zero mobile service loss / interruption experienced by the users of the MNO.

[0053] Furthermore, and in a third constraint, some of the RBSs selected to participate in the bidding may generate alarms / failures / etc. and may be suddenly disconnected for various reasons. Therefore, some backup methods may be necessary to improve the reliability of the system.

[0054] An additional challenge for CSP is battery degradation (the fourth constraint) related to the amortization of the capital costs associated with the battery. This natural process reduces the amount of energy that a battery can store over time. This process is unavoidable, but it can be slowed down, for example, using smart battery usage techniques and cluster control.

[0055] One or more embodiments of the present invention help solve one or more problems / challenges of existing systems.

[0056] Before describing the example embodiments in detail, it is noted that the embodiments reside primarily in combinations of equipment components and process steps related to providing ancillary services (e.g., FCR event participation) to a power grid. Accordingly, components have been represented where appropriate by conventional symbols in the figures, which show only those specific details relevant to understanding the embodiments so as not to obscure the disclosure with details that would be readily apparent to one of ordinary skill in the art having the benefit of the description herein. Like reference numerals refer to like elements throughout the description.

[0057] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc., may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to be limitations of the concepts described herein. Unless the context clearly indicates otherwise, as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It will be further understood that when used herein, the terms "comprises", "comprising", "includes", and / or "including" specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0058] In the embodiments described herein, connection terms "in communication with" and the like may be used to indicate electrical or data communications that may be achieved through, for example, physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that the various components may interoperate and that modifications and variations are possible to achieve electrical and data communications.

[0059] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate connection (although not necessarily direct) and may include wired and / or wireless connections.

[0060] The term "radio base station" (RBS) used herein may be any kind of radio base station and / or network node included in a radio network, which may further include any of the following: base station (BS), base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gNodeB (gNB), evolved NodeB (eNB or eNodeB), NodeB, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU) remote radio head (RRH), core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. The RBS may also include test equipment. The term "radio node" as used herein may also be used to denote a wireless device (WD) such as a wireless device (WD) or a radio network node / RBS.

[0061] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD herein may be any type of wireless device, such as a wireless device (WD), capable of communicating with a network node or another WD via a radio signal. The WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded equipment (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0062] Moreover, in some embodiments, the general term "radio network node" is used. It can be any kind of radio network node, which can include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU) remote radio head (RRH).

[0063] Note that while terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in the present disclosure, this should not be viewed as limiting the scope of the disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas included in the present disclosure.

[0064] It is further noted that the functions described herein as being performed by a wireless device, a (cloud-based) management node or an RBS may be distributed to multiple wireless devices, RBSs and / or management nodes. In other words, it is contemplated that the functions of the RBSs, management nodes and wireless devices described herein are not restricted to being performed by a single physical device and may in fact be distributed to several physical devices.

[0065] In some embodiments, a general description element in the form of "one of A and B" corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B, or AB, or corresponds to one or more of A and B. In some embodiments, at least one of A, B, and C corresponds to one or more of A, B, and C, and / or A, B, C, or a combination thereof.

[0066] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meanings in the context of this specification and in the relevant field, and unless explicitly defined as such herein, the terms used herein will not be interpreted in an idealized or overly formal sense.

[0067] Some embodiments provide systems and functionality for efficiently managing a radio access network comprising a plurality of RBSs connected to a power grid and capable of participating in ancillary services including FCR services.

[0068] Referring now to the drawings, wherein like elements are referenced by like reference numerals, Figure 11 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), the communication system 10 including an access network 12 such as a radio access network and a core network 14. The access network 12 includes a plurality of radio base stations (RBSs) 16a, 16b, 16c (collectively referred to as radio base stations (RBSs) 16) such as network nodes, NBs, eNBs, gNBs and / or other types of wireless access points / base stations, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each RBS 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding RBS 16a or to be paged by the corresponding RBS 16a. A second WD 22b in the coverage area 18b is wirelessly connectable to the corresponding RBS 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to situations where only a single WD 22 is in the coverage area or where a single WD 22 is connecting to a corresponding RBS 16. Note that although only two WDs 22 and three RBSs 16 are shown for convenience, the communication system may include more WDs 22 and RBSs 16.

[0069] Moreover, it is contemplated that the WD 22 may communicate with more than one RBS 16 and more than one type of RBS 16 simultaneously and / or be configured to communicate with more than one RBS 16 and more than one type of RBS 16, respectively. For example, the WD 22 may have dual connectivity with an RBS 16 supporting LTE and with the same or different RBS 16 supporting NR. As an example, the WD 22 may communicate with an eNB for LTE and / or E-UTRAN and a gNB for NR / NG-RAN.

[0070] The communication system 10 itself may be connected to a management node 24, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The management node 24 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the management node 24 may extend directly from the core node 14 to the management node 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or managed network or a combination of more than one of a public, private, or managed network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0071] Figure 1 The communication system as a whole enables connectivity between one of the RBS16 and / or WD 22 and the management node 24. Connectivity can be described as an over-the-top (OTT) connection. The management node 24 and the connected RBS16 and / or WD 22 are configured to use the access network 12, the core node 14, any intermediate network 30 (note from the network 30 that in some cases, a utility signal is provided from the DSO / TSO) and possible additional infrastructure (not shown) as an intermediary to pass data and / or signaling (e.g., control signaling) via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes do not know the routing of uplink and downlink communications. For example, the RBS16 may not be notified or need not be notified of the past routing of incoming downlink communications, where data originating from the management node 24 is to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the RBS16 does not need to know the future routing of outgoing uplink communications originating from the WD 22a toward the management node 24.

[0072] The RBS 16 may be configured to include a status reporting unit 32 configured to monitor and / or report one or more conditions / statuses / requirements etc. associated with the RBS 16, e.g. based on control signals received from the management node 24. The RBS 16 may be configured to include a power management unit 33 configured to control power supplied to and / or from one or more hardware components of the RBS 16, e.g. based on control signals received from the management node 24.

[0073] The management node 24 is configured to include a network management unit 34 (e.g., an orchestrator and / or an operations and support system (OSS)) that can be referred to as operating "in the cloud." For example, the network management unit 34 includes an Ericsson Network Manager (ENM) or a similar entity / function. Alternatively, in some embodiments of the present disclosure, the network management unit 34 may be located in the core node 14 and / or in one or more RBSs 16, so that at least some functionality associated with the management node 24 may be performed in the core network 30 or the access network 12 by one or more nodes / devices described herein.

[0074] Now refer to Figure 2 To describe an example implementation according to an embodiment of the WD 22, RBS 16, and management node 24 discussed in the previous paragraphs. In the communication system 10, the management node 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 10. The management node 24 further includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or instead of a processor such as a central processing unit and a memory, the processing circuit 42 may also include, for example, one or more processors and / or processor cores suitable for executing instructions and / or an integrated circuit of an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) for processing and / or control. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any kind of volatile and / or non-volatile memory such as a cache memory and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0075] The processing circuit 42 may be configured to control any of the methods and / or processes described herein and / or configured to cause such methods and / or processes to be performed, for example, by the management node 24. The processor 44 corresponds to one or more processors 44 for performing the management node 24 functions described herein. The management node 24 includes a memory 46 configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 48 and / or the management application 50 may include instructions that, when executed by the processor 44 and / or the processing circuit 42, cause the processor 44 and / or the processing circuit 42 to perform the processes described herein with respect to the management node 24. The instructions may be software associated with the management node 24.

[0076] The software 48 may be executable by the processing circuit 42. The software 48 includes a management application 50. The management application 50 may be operable to provide services to remote users such as WD 22 connected via an OTT connection 52 terminated at the WD 22 and the management node 24. When providing services to remote users, the management application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the described functionality. In one embodiment, the management node 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 42 of the management node 24 may enable the management node 24 to observe, monitor, control, transmit to and / or receive from the RBS 16 and / or the wireless device 22 and / or a third party (such as a power grid / utility operator) to the RBS 16 and / or the wireless device 22 and / or a third party (such as a power grid / utility operator). The processing circuit 42 of the management node 24 may include a network management unit 34, which is configured to enable the service provider to observe / monitor / control / transmit signaling to / receive signaling from the RBS 16 and / or the grid / utility operator, such as determining which RBS 16 to assign to participate in ancillary services and at what times (e.g., based on an optimization model), determining signaling for assigning the RBS 16 to participate, determining a profile for the RBS 16 for controlling its operation when providing ancillary services, activating / deactivating / controlling the RBS 16 before, during and after participating in ancillary services, and / or generating reports based on the provision of ancillary services (e.g., sending reports to a utility operator to receive payment for providing ancillary services).

[0077] The communication system 10 further includes an RBS 16 provided in the communication system 10 and including hardware 58 that enables it to communicate with the management node 24 and with the WD 22. The hardware 58 may include one or more batteries 59 (collectively referred to as batteries 59) for storing energy, for example as a backup power supply for the RBS 16. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to an interface with different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the RBS 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the management node 24. The connection 66 (which may be used to transmit one or more synchronization signals, such as control signaling indicating one or more operating settings / profiles) may be direct or it may pass through the core node 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10. The hardware may include a power supply unit 67 for managing the charging and discharging of power from a battery, the reception of power from an external source (e.g., a power grid), monitoring power consumption / battery status / SoC, etc. based on control signals received from a power management unit 33 / management node 24 / network management unit 34 / etc.

[0078] In the illustrated embodiment, the hardware 58 of the RBS 16 further comprises a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, the processing circuit 68 may include, in addition to or in lieu of a processor such as a central processing unit and a memory, one or more processors and / or processor cores and / or an integrated circuit such as an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) adapted to execute instructions for processing and / or control. The processor 70 may be configured to access (e.g. write to and / or read from) a memory 72, which may include, for example, a cache memory and / or a buffer memory and / or a RAM (random access memory) and / or a ROM (read only memory) and / or an optical memory and / or an EPROM (erasable programmable read only memory) of any kind of volatile and / or non-volatile memory.

[0079] Therefore, the RBS 16 further has software 74, which is stored internally, for example, in the memory 70 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the RBS 16 via an external connection. The software 74 may be executable by the processing circuit 68. The processing circuit 68 may be configured to control any of the methods and / or processes described herein and / or configured to cause such methods and / or processes to be performed, for example, by the RBS 16. The processor 70 corresponds to one or more processors 70 for performing the RBS 16 functions described herein. The memory 72 is configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the processes described herein with respect to the RBS 16. For example, the processing circuitry 68 of the RBS 16 may include a status reporting unit 32 configured to monitor and / or report one or more conditions / statuses / requirements, etc. associated with the RBS 16, such as hardware status (e.g. battery status / power level / SoC), traffic load information (e.g. actual or predicted communication requirements, such as predicted traffic / signaling load on the RBS 16 in a particular time slot based on historical data, wireless device 22 signaling, etc.), geographic information (e.g. location coordinates, proximity to other RBSs 16, proximity to a particular power grid, etc.), capability information (e.g. latency of signaling within the RBS 16), etc. The processing circuitry 68 may also include a power management unit 33 configured to control power supplied to and / or supplied from one or more hardware components of the RBS 16, e.g. based on signaling received from the management node 24, based on the status of the battery 59, based on actual or predicted traffic load, etc.

[0080] The communication system 10 further includes the already mentioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain a wireless connection 64 with the RBS 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers and / or one or more RF transceivers.

[0081] The hardware 80 of the WD 22 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor such as a central processing unit and a memory such as a central processing unit, the processing circuit 84 may also include, for example, one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions, for processing and / or control. The processor 86 may be configured to access (e.g., write to and / or read from) a memory 88, which may include, for example, a cache memory and / or a buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory) of any kind of volatile and / or non-volatile memory.

[0082] Therefore, WD 22 may further include software 90, which is stored in, for example, a memory 88 at WD 22 or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. Software 90 may be executable by processing circuit 84. Software 90 may include client application 92. With the support of management node 24, client application 92 may be operable to provide services to human or non-human users via WD 22. In management node 24, the executing management application 50 may communicate with the executing client application 92 via an OTT connection 52 terminated at WD 22 and management node 24. When providing services to users, client application 92 may receive request data from management application 50 and provide user data in response to the request data. OTT connection 52 may transmit both request data and user data. Client application 92 may interact with the user to generate the user data it provides.

[0083] The processing circuit 84 may be configured to control any of the methods and / or processes described herein and / or configured to cause such methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein with respect to the WD 22.

[0084] In some embodiments, the internal workings of RBS 16, WD 22, and management node 24 may be as follows: Figure 2As shown in , and independently, the surrounding network topology can be Figure 1 The surrounding network topology.

[0085] In some embodiments, core nodes 14 (not in Figure 2 The hardware of the RBS 16 and / or the management node 24 may be similar to that of the RBS 16 and / or the management node 24.

[0086] exist Figure 2 In the diagram, the OTT connection 52 has been abstractly drawn to illustrate the communication between the management node 24 and the wireless device 22 via the RBS 16, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the WD 22 or hidden from the service provider operating the management node 24, or hidden from both. When the OTT connection 52 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0087] The wireless connection 64 between WD 22 and RBS 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to WD 22 using OTT connection 52, where wireless connection 64 can form the last segment. More specifically, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, looser restrictions on file size, better responsiveness, extended battery life, etc.

[0088] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors that are improved by one or more embodiments. In response to changes in the measurement results, there may be further optional network functionality for reconfiguring the OTT connection 52 between the management node 24 and the WD 22. The measurement process and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the management node 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 52 passes or may be associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity illustrated above or providing the value of other physical quantities by which the software 48, 90, 74 can calculate or estimate the monitoring quantity. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing selection, etc.; the reconfiguration does not need to affect the RBS 16, and it may be unknown or imperceptible to the RBS 16. Some such processes and functionalities may be known and implemented in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates measurement of throughput, propagation time, latency, etc. by the management computer 24. In some embodiments, the measurements may be achieved because the software 48, 90, 74 uses the OTT connection 52 to cause messages to be transmitted, particularly empty messages or "fake" messages to be transmitted, while the software 48, 90, 74 monitors propagation time, errors, etc.

[0089] Thus, in some embodiments, the management node 24 includes a processing circuit 42 configured to provide user data and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes an RBS 16 having a radio interface 62. In some embodiments, the RBS 16 is configured and / or the RBS 16 processing circuit 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the WD 22 and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from the WD 22.

[0090] In some embodiments, the management node 24 includes a processing circuit 42 and a communication interface 40 configured to receive user data originating from a transmission from the WD 22 to the RBS 16. In some embodiments, the WD 22 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the RBS 16 and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from the RBS 16 and / or includes a radio interface 82 and / or processing circuit 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the RBS 16 and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from the RBS 16.

[0091] Although Figure 1 and Figure 2 Various "units" are shown, such as status reporting unit 32, power management unit 33, and network management unit 34, as being within respective processors, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented within the processing circuitry in hardware or in a combination of hardware and software.

[0092] Figure 3 is a diagram illustrating a method for transmitting a signal in a communication system (such as, for example, Figure 1 and Figure 2 A flowchart of an example method implemented in a communication system of Figure 2 The method includes a management node 24, an RBS 16, and a WD 22 as described above. In a first step of the method, the management node 24 provides user data (box S100). In an optional sub-step of the first step, the management node 24 provides user data by executing a management application (such as, for example, the management application 50) (box S102). In a second step, the management node 24 initiates a transmission carrying the user data to the WD 22 (box S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the RBS 16 transmits the user data carried in the transmission initiated by the management node 24 to the WD 22 (box S106). In an optional fourth step, the WD 22 executes a client application (such as, for example, the client application 92) associated with the management application 50 executed by the management node 24 (box S108).

[0093] Figure 4 is a diagram illustrating a method for transmitting a signal in a communication system (such as, for example, Figure 1 A flowchart of an example method implemented in a communication system of Figure 1 and Figure 21 and 2. In the method, the management node 24, RBS 16 and WD 22 are described in detail. In a first step of the method, the management node 24 provides user data (box S110). In an optional sub-step (not shown), the management node 24 provides the user data by executing a management application (such as, for example, the management application 50). In a second step, the management node 24 initiates a transmission carrying the user data to the WD 22 (box S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can pass through the RBS 16. In an optional third step, the WD 22 receives the user data carried in the transmission (box S114).

[0094] Figure 5 is a diagram illustrating a method for transmitting a signal in a communication system (such as, for example, Figure 1 A flowchart of an example method implemented in a communication system of Figure 1 and Figure 2 The management node 24, RBS 16 and WD 22 described above. In an optional first step of the method, WD 22 receives input data provided by the management node 24 (box S116). In an optional sub-step of the first step, WD 22 executes a client application 92, which provides user data as a reaction to the received input data provided by the management node 24 (box S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (box S120). In an optional sub-step of the second step, WD provides user data by executing a client application (such as, for example, client application 92) (box S122). When providing user data, the executed client application 92 can further consider user input received from the user. Regardless of the specific manner in which the user data is provided, WD 22 can initiate the transmission of user data to the management node 24 in an optional third sub-step (box S124). In a fourth step of the method, management node 24 receives user data transmitted from WD 22 (block S126 ), in accordance with the teachings of the embodiments described throughout this disclosure.

[0095] Figure 6 is a diagram illustrating a method for transmitting a signal in a communication system (such as, for example, Figure 1 A flowchart of an example method implemented in a communication system of Figure 1 and Figure 2The management node 24, RBS 16 and WD 22 described above are those described above. In an optional first step of the method, the RBS 16 receives user data from the WD 22 (block S128) in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step, the RBS 16 initiates a transmission of the received user data to the management node 24 (block S130). In a third step, the management node 24 receives the user data carried in the transmission initiated by the RBS 16 (block S132).

[0096] Figure 7 1 is a flow chart of an example process for FCR operation in the RBS 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the RBS 16, such as one or more of the processing circuit 68 (including the status reporting unit 32 and / or the power management unit 33), the processor 70, the radio interface 62, the communication interface 60, the battery 59 and / or the power supply unit 67. The RBS 16 is configured to receive (block S134) a synchronization signal from the network management unit 34 (e.g., the management node 24), wherein the synchronization signal indicates a schedule including an activation period. The RBS 16 is configured to receive (block S136) an activation signal from the network management unit 34 during the activation period. The RBS 16 is configured to modify (block S138) the power consumption of the RBS 16 based on the synchronization signal and the activation signal in response to the activation signal.

[0097] In some embodiments of the present disclosure, transmission of a synchronization signal including an AS profile to the RBS 16 of each cluster occurs before the active hour, the AS profile optionally including a profile control, the profile control indicating at least one of: synchronization of the RBS 16 in response to each demand from the network management unit to execute the AS profile, and local execution on at least one local controller for executing at least one power modification process based on at least one threshold indicated by the AS profile. In one or more embodiments, when the synchronization signal is sent to the cluster, the profile can be executed during the hour by sending the profile and before the service hour. The optional profile control can be included in the operation so that a) synchronization occurs at each demand from the ENM / OSS to execute the profile, b) local execution occurs at the local level, on the local controller, and based on various thresholds provided by the profile.

[0098] In one or more embodiments, the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the RBS 16. In one or more embodiments, the AS profile indicates one of the primary cluster 100 and the backup cluster 102 to which the RBS 16 is assigned, and the AS profile is shared by at least one other RBS 16 of the cluster to which the RBS 16 is assigned. In one or more embodiments, the AS profile indicates the backup cluster 102 to which the RBS 16 is assigned, wherein the RBS 16 is further configured to receive an updated synchronization signal indicating an updated AS profile from the network management unit 34, the updated AS profile indicating a reassignment to the primary cluster 100, and the reassignment is associated with at least one failure condition of another radio base station 16 assigned to the primary cluster 100.

[0099] In one or more embodiments, the RBS 16 is further configured to: determine a status report indicating a condition of the RBS 16; and cause transmission of the status report to the network management unit 34, wherein the synchronization signal is determined based on the status report. In one or more embodiments, the activation signal indicates a frequency control reserve FCR-down regulation event, wherein the modification of power consumption by the RBS 16 includes reducing power supplied from the grid to the RBS 16 from the utility operator. In one or more embodiments, the RBS 16 includes a battery 59, wherein reducing the power supplied from the grid includes switching from power supplied by the grid to power supplied by the battery 59. In one or more embodiments, the synchronization signal indicates a first threshold and a second threshold below the first threshold, wherein the schedule includes a first period before the activation period, and the RBS 16 is further configured to: maintain the battery 59 charge above the first threshold during the first period; and reduce the battery 59 charge to the second threshold during the activation period based on the activation signal indicating the FCR-down regulation event.

[0100] In one or more embodiments, the activation signal indicates an FCR-up regulation event, and the modification of power consumption by the RBS 16 includes increasing power supplied from the grid to the RBS 16. In one or more embodiments, the RBS 16 includes a battery 59, and increasing the power supplied from the grid includes charging the battery 59. In one or more embodiments, the synchronization signal indicates a first threshold and a second threshold that is higher than the first threshold, wherein the schedule includes a first period before the activation period, and the RBS 16 is further configured to: maintain the battery 59 charge below the first threshold during the first period; and increase the battery 59 charge to the second threshold during the activation period based on the activation signal indicating the FCR-up regulation event.

[0101] Figure 81 is a flowchart of another example process for FCR operation in an RBS 16 according to some embodiments of the present disclosure. The RBS 16 is configured to be switchable between power from the grid and power from a plurality of backup battery units associated with the RBS 16. One or more blocks described herein may be performed by one or more elements of the RBS 16, such as one or more of the processing circuit 68 (including the status reporting unit 32 and / or the power management unit 33), the processor 70, the radio interface 62, the communication interface 60, the battery 59 and / or the power supply unit 67. The RBS 16 is configured to receive (block S140) a synchronization signal with an operational setting associated with a primary subset and a backup subset of a plurality of RBSs 16 forming a cluster, wherein the operational setting is associated with participating in at least one frequency control reserve FCR event. The RBS 16 is configured to receive (block S141) an activation signal during an activation period, the activation signal being configured to cause the RBS 16 to modify its power consumption based on the synchronization signal in response to the activation signal. The RBS 16 is configured to modify (block S142 ) power consumption of the RBS 16 based on the synchronization signal and the activation signal to participate in at least one FCR event.

[0102] According to one or more embodiments, the RBS 16 is part of one of a primary subset and a backup subset of a plurality of RBSs 16. According to one or more embodiments, the activation signal indicates that the RBS 16 is to participate in an FCR-down event, and the modification of power consumption by the RBS 16 includes reducing power used from the grid by the RBS 16. According to one or more embodiments, the activation signal indicates that the RBS 16 is to participate in an FCR-up event, and the modification of power consumption by the RBS 16 includes increasing power used from the grid by the RBS 16 by at least partially charging at least one of the plurality of backup battery units.

[0103] According to one or more embodiments, a synchronization signal is received by the RBS 16 prior to an active time period, wherein the processing circuit 68 is further configured to: execute an operation setting during the active time period, wherein the operation setting includes a profile control, and the profile control indicates at least one of the following: synchronization of the RBS 16 in response to each request from the management node 24 to execute the operation setting, local execution on at least one local controller, and execution of at least one power modification process based on at least one threshold indicated by the operation setting.

[0104] Fig. 91 is a flow chart of an example process for FCR operation in a management node 24 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the management node 24, such as one or more of the processing circuit 42 (including the network management unit 34), the processor 44, and / or the communication interface 40. The management node 24 (e.g., the network management unit 34) is configured to cause transmission of a synchronization signal to a first RBS 16 of a plurality of RBSs 16 (block S143), wherein the synchronization signal indicates a schedule including an activation period. The management node 24 (e.g., the network management unit 34) is configured to cause transmission of an activation signal to the first RBS 16 during the activation period (block S144), wherein the activation signal is configured to cause the first RBS 16 to modify its power consumption based on the synchronization signal.

[0105] In one or more embodiments, the network management unit 34 (e.g., the management node 24) is further configured to: receive an indication indicating a bidding schedule and a frequency control reserve FCR configuration from a grid operator; and determine a primary cluster 100 for a plurality of RBSs 16 participating in the FCR service during an active period of the bidding schedule based on the bidding schedule and the FCR configuration, wherein the primary cluster 100 includes a first RBS 16. In one or more embodiments, the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the first RBS 16. In one or more embodiments, the AS profile is shared by the RBSs 16 of the primary cluster 100.

[0106] In one or more embodiments, the network management unit 34 is further configured to: determine a backup cluster 102 of the plurality of RBSs 16 different from the primary cluster 100 based on the bidding schedule and the FCR configuration, the backup cluster 102 including the second RBS 16; receive a status report from the first RBS 16 indicating a fault in the first RBS 16; and based on the received status report, replace the first RBS 16 with the second RBS 16 by causing transmission of a deactivation indication to the first RBS 16, the deactivation indication being configured to cause the first RBS 16 to ignore future activation signals; and cause transmission of an AS profile to the second RBS 16 indicating to reassign the second RBS 16 from the backup cluster 102 to the primary cluster 100. In one or more embodiments, determining the backup cluster 102 of the plurality of RBSs 16 is based on proximity of the RBSs 16 of the backup cluster 102 to at least one RBS 16 of the primary cluster 100. In one or more embodiments, the activation signal indicates an FCR-down regulation event, and the modification of power consumption by the first RBS 16 includes reducing power supplied from the grid to the first RBS 16.

[0107] In one or more embodiments, the first RBS 16 includes a battery 59, wherein reducing the power supplied from the grid includes switching from power supplied by the grid to power supplied by the battery 59. In one or more embodiments, the synchronization signal indicates a first threshold and a second threshold below the first threshold, wherein the schedule includes a first period prior to the activation period, wherein the synchronization signal is configured to cause the first RBS 16 to: maintain the battery 59 charge above the first threshold during the first period; and reduce the battery 59 charge to the second threshold during the activation period based on the activation signal indicating the FCR-down regulation event. In one or more embodiments, the activation signal indicates an FCR-up regulation event, wherein the modification of power consumption by the first RBS 16 includes increasing the power supplied to the first RBS 16 by the grid.

[0108] In one or more embodiments, the first RBS 16 includes a battery 59, wherein increasing the power supplied from the grid includes charging the battery 59. In one or more embodiments, the synchronization signal indicates a first threshold and a second threshold that is higher than the first threshold, wherein the schedule includes a first period prior to the activation period, and wherein the synchronization signal causes the first RBS 16 to: maintain the battery 59 charge below the first threshold during the first period; and increase the battery 59 charge to the second threshold during the activation period based on the activation signal indicating the FCR-up regulation event. In one or more embodiments, determining the plurality of RBSs 16 to be assigned to the primary cluster 100 is based on an optimization model, wherein the optimization model is configured to at least one of: maximize profit; minimize disruption to quality of service; minimize degradation of the battery 59; and minimize penalties from a grid operator.

[0109] In some embodiments, a synchronization signal may be sent to a cluster (e.g., primary cluster 100 or standby cluster 102) prior to a service / activity hour, for example, by sending profile(s) to one or more RBSs 16. The profile(s) may be executed during the hour by one or more RBSs 16. Optional profile controls may be included in the operation, such as a) synchronization upon every demand from a network management unit 34 (e.g., ENM / OSS) executing the profile; and / or b) execution at a local level, locally on a local controller (e.g., processing circuitry 68 of an RBS 16) and based on various thresholds provided by the profile(s).

[0110] Fig.10is a flowchart of another example process for FCR operation in the management node 24 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the management node 24, such as one or more of the processing circuit 42 (including the network management unit 34), the processor 44 and / or the communication interface 40. The management node 24 is configured to communicate with a grid operator and with a plurality of RBSs 16, wherein each of the plurality of RBSs is configured to be switchable between power from the grid and power from a corresponding plurality of backup battery units associated with the RBS 16. The management node 24 (e.g., the network management unit 34) is configured to determine (block S145) a primary subset of the plurality of RBSs 16 to participate in at least one frequency control reserve FCR event occurring during a predefined time interval. The management node 24 is configured to determine (block S146) a backup subset of the plurality of RBSs 16, each of which is configured to participate in at least one FCR event in place of a failure of a corresponding one of the primary subsets of the plurality of RBSs. The management node 24 is configured to cause (block S147) transmission of a synchronization signal having operational settings to a primary subset and a backup subset of the plurality of RBSs 16, wherein the operational settings are associated with participation in at least one FCR event. The management node 24 is configured to cause (block S148) transmission of an activation signal to at least one of the primary subset of the plurality of RBSs 16 during an activation period, wherein the activation signal is configured to cause the RBS 16 to modify its power consumption based on the synchronization signal.

[0111] According to one or more embodiments, determining the primary subset and the backup subset of the plurality of RBSs 16 is based on an optimization model that maximizes availability to participate in at least one FCR event and an energy compensation event while minimizing penalty costs for failure to meet energy requirements for at least one FCR event, battery degradation costs, physical ranges of the primary subset and the backup subset of the plurality of RBSs 16, and the number of RBSs 16 in the primary subset and the backup subset of the plurality of RBSs 16.

[0112] According to one or more embodiments, the optimization model iteratively generates a set of operating settings according to an iterative pricing problem model, wherein the iterative pricing problem model is configured to calculate contributions of estimated battery degradation, FCR-up events, and FCR-down events for a corresponding RBS 16 participating in at least one FCR event at time t, wherein different FCR events of the RBS 16 are considered, and wherein the FCR-down event corresponds to a decrease in power supplied from the grid to at least one of the major subsets of the plurality of RBSs 16, and wherein the FCR-up event corresponds to an increase in power supplied by the grid to at least one of the major subsets of the plurality of RBSs 16.

[0113] According to one or more embodiments, an iterative pricing problem model output is an RBS configuration among a plurality of RBS configurations, the RBS configuration having a minimum cost for participating in at least one FCR event compared to costs associated with remaining RBS configurations, and wherein the minimum cost is based on availability for participating in at least one FCR event, compensation for participating in at least one FCR event, penalty cost for failure to meet energy requirements for at least one FCR event, battery degradation cost, physical ranges of a primary subset and a backup subset of the plurality of RBSs 16, and the number of RBSs 16 in the primary subset and the backup subset of the plurality of RBSs 16.

[0114] According to one or more embodiments, the battery degradation cost is estimated based on linearizing a battery degradation curve that maps a maximum battery cycle number to a discharge depth of the battery, segmenting the linearized battery degradation curve, and determining a degradation rate for each segment of the linearized battery degradation curve for each event in a battery degradation model.

[0115] According to one or more embodiments, the at least one FCR event corresponds to a plurality of FCR events occurring during a predefined time interval, wherein a first portion of a primary subset of the plurality of RBSs 16 is scheduled to participate in a first FCR event of the plurality of FCR events, and a second portion of the primary subset of the plurality of RBSs 16 is scheduled to participate in a second FCR event of the plurality of FCR events, and wherein the first portion of the primary subset of the plurality of RBSs 16 is different from the second portion.

[0116] Having described the general process flow of the disclosed arrangement and provided examples of hardware and software arrangements for implementing the disclosed processes and functions, the following section provides details and examples of arrangements for a wireless network including RBS 16 to provide ancillary services such as FCR services to a grid.

[0117] One or more management node 24 functions described below may be performed by one or more of the network management unit 34, the processing circuitry 42, the processor 44, the communication interface 40, etc. That is, although some functions are described as being performed by the network management unit 34, these functions may be performed by the management node 24 and / or another element in the management node 24. One or more RBS 16 functions described below may be performed by one or more of the processing circuitry 68, the status reporting unit 32, the power management unit 33, the radio interface 62, the communication interface 60, etc.

[0118] According to the principles of the present disclosure, the network architecture disclosed herein can enable a power supply unit 67 (PSU 67) of an RBS 16 in multiple FCR "zones" (e.g., a cluster of RBS 16 participating in FCR) of a plurality of RBSs 16 to distribute FCR control signals to support a grid with FCR services. Thus, it may be feasible to act as an entity (from a utility's perspective) and distribute FCR signals to multiple radio base stations 16 (RBSs), meet many or all minimum requirements for services, and in this way support a grid with FCR services by reusing existing CSP assets. The PSU 67 may have a connection to the grid (e.g., a direct connection or an indirect connection), wherein the connection is in accordance with local grid specifications (e.g., a 230VAC grid in Sweden). The PSU 67 has a connection to one or more components of the hardware 58. For example, the PSU 67 has a connection to a battery 59, for example, to provide power to charge the battery. The PSU 67 has a connection to a radio interface 62, which may include, for example, a radio antenna and other radio hardware. The PSU 67 is controlled by signals received from the processing circuitry 68 (eg from the power management unit 33 or similar controller), which in turn may be determined based on control signals (such as profiles) received by the RBS 16 from the management node 24 / network management unit 34 .

[0119] The RBS 16 may provide mobile services to the wireless devices 22 (eg, via the radio interface 62), while the network management unit 34 may simultaneously provide radio scheduling and orchestration of both mobile radio traffic and scheduling for FCR (or any other ancillary service).

[0120] Some embodiments provide a cloud operating system and functionality to efficiently manage a RAN network consisting of multiple RBSs 16 / network nodes connected to the grid and capable of participating in ancillary services / FCR.

[0121] This method controls and triggers various activities before the service is activated, such as:

[0122] Prior to the day, the best cluster (e.g., a set of RBSs 16 / network nodes) within a bidding period (e.g., bidding hour) is identified and the clusters are optionally divided into primary clusters and backup / standby clusters. The primary cluster actively participates in the service and the standby cluster works as an additional asset (e.g., for redundancy purposes).

[0123] Modeling methods are used to indicate / determine the most profitable time slot(s) to participate in the next day (taking into account, for example, energy storage / battery degradation, price / expected revenue, potential penalties, etc.).

[0124] From the perspective of RBS16 control, a synchronization signal (e.g., with a profile) is provided for each bidding period (e.g., bidding hour), which can be formed and operated as a single entity based on clusters (e.g., primary cluster and backup cluster) given the same identity (relative to the bidding cluster) / associated with clusters (e.g., primary cluster and backup cluster) given the same identity (relative to the bidding cluster).

[0125] Auxiliary identities identifying elements of the primary and backup clusters are generated internally, where different RBSs 16 can be activated and operate as one entity (which is required to participate in AS / FCR) or several entities within the cluster, forming a control strategy for the primary and backup RBSs 16.

[0126] The method further determines and manages the clusters, sends synchronized activation signals before (or during) the bidding hour to activate and deactivate multiple RBSs 16 and deliver AS / FCR signals. Signals may also be sent before activation or before the day of the day.

[0127] The method supports CSPs / MNOs willing to offer AS / FCR and realize additional revenue streams. The method finds / predicts the most profitable cluster (e.g. compared to one or more other clusters) within a bidding hour to maximize the operator's revenue. The method allows identification / prediction of the most profitable time slot (e.g. compared to one or more other time slots) to participate in the next day.

[0128] For each bidding hour, the method may also select one (or more) standby clusters to operate and one as a backup, improving the reliability of the system described herein.

[0129] The method takes into account one or more elements present in the RAN system, including batteries and their degradation effects.

[0130] The method enables synchronization signals, where the signals may contain different information such as site profile, power profile, cluster profile, battery profile, capacity profile, control profile (PSU 67, battery 59, radio equipment), etc., for faster reaction time and preparation of RBS16 before and during active service hours.

[0131] Clusters may be formed depending on need and operation, for example based on: 1) power level, 2) latency, 3) location (proximity to each other), 4) performance, 5) battery capacity (RBS battery 59 capacity may vary in different locations / different RBS16 / etc.), 6) PSU 67 capacity, 7) radio interface 62 power consumption, 8) time of day, 9) cost of electricity, 10) business needs, etc.

[0132] In the event of a power outage or if the RBS 16 functionality fails, the RBS 16 battery 59 provides a backup power source. However, in countries where the grid is very stable, the power source 67 and battery 59 may not be fully utilized, or it may be used only a few times a year, and those assets can be utilized by the CSP / MNO, for example by providing AS / FCR as described herein.

[0133] Fig.11 An example of a group of RBSs 16 providing FCR-N (or alternatively providing FCR-D) is depicted, taking into account both upward and downward adjustments based on requests, namely: normal operation, upward adjustment requests and downward adjustments. In one or more embodiments, normal operation may refer to not participating in FCR-N. These requests may be transmitted as signals sent by a utility provider (e.g., at the level of seconds), and / or such signals may be generated locally (e.g., by one or more RBSs 16 in response to detected conditions, etc.). For example, one or more of a set of RBSs 16 belonging to a particular area 93 (in this example, referred to as "Stockholm area / region 1") participate in FCR-N provision.

[0134] Example Operation Before FCR Hour: In one or more embodiments, the RBS 16 may be configured (e.g., based on a profile / control signal received from the management node 24) to charge the battery 59 to a threshold value (e.g., 80% of the charge capacity), where the threshold value may vary. For example, during a time period before the active hour, the RBS 16 may reduce the threshold value (e.g., to 40% of the charge capacity), while during other periods (e.g., during periods during which electricity prices are relatively cheap), the threshold value may be increased (e.g., to 90% of the charge capacity). These threshold values ​​and when / under what conditions the threshold values ​​apply may be defined by a synchronization signal / profile received from the management node 24. In this way, the network manager may reduce the charging of the battery 59 (thereby increasing the amount of backup battery 59 capacity) so that the battery 59 can absorb some power from the grid 95 during FCR-up regulation events, while also maintaining a sufficient charge in the battery 59 so that the battery 59 can power the RBS 16 during FCR-down regulation events. These thresholds may be configured on a per-cluster basis (eg, all RBSs 16 in a cluster share the same thresholds), and / or may be configured on a per-RBS 16 basis (eg, each RBS 16 has its own corresponding thresholds).

[0135] Normal operation 94 during, e.g., FCR hours: For normal operation 94, there are no FCR-up or FCR-down regulation requests received from the power utility, and in this case, the RBS 16 may be provided with power from the grid 95 to, e.g., provide RBS functionality but without charging / recharging the battery 59. FCR-up regulation 96: During FCR-up regulation 96, an upward regulation request is received (e.g., as a signal sent by the management node 24, as a signal from the utility operator, as a result of the RBS 16 observing the condition of the connection to the grid 95, etc.), where the utility operator requests the CSP / MNO to increase grid energy consumption.

[0136] The increase in energy consumption at the RBS 16 may be achieved by recharging one or more RBS 16 batteries 59. For example, the RBS 16 may increase the threshold at which the battery 59 is charged during the FCR-up regulation 96 period, e.g., from 60% to 90% of the charge capacity, so that if the battery 59 was not previously charging (because it was "full" at 60%), the battery 59 will now begin charging, thereby increasing the overall energy consumption at the RBS 16. Other techniques for increasing the power consumption of the RBS 16 during the FCR-up regulation 96 event may be utilized. For example, the RBS 16 may increase the power supplied to the radio interface 62 (e.g., to increase the power of wireless signaling), increase the power supplied to the processing circuitry 68, perform one or more maintenance / backup operations that increase power consumption, and the like.

[0137] FCR-down regulation 98: In FCR-down regulation 98, a down regulation request is received, wherein the utility requests the CSP / MNO to reduce grid energy consumption, which may be achieved by the RBS 16 switching its power source from the grid 95 to the battery 59, causing the RBS to reduce or eliminate its power consumption from the grid 95 and instead utilize power from the battery 59. Other techniques for reducing the power consumption of the RBS 16 during the FCR down regulation 98 may be utilized without departing from the scope of the present disclosure. For example, the RBS 16 may reduce the power supplied to the radio interface 62 (e.g., reducing the power of wireless signaling), reduce the power supplied to the processing circuit 68, reduce the threshold of the maximum charge of the battery 59 (stopping charging the battery 59 and thereby reducing overall energy consumption), etc.

[0138] To activate ancillary services and manage the energy system, a cloud-based network manager such as a network management unit 34 in the management node 24 may be used in some embodiments of the present disclosure. For example, external signals regarding ancillary services / FCR services may be received from a utility company (e.g., a TSO), and all communications between the utility and the RBS 16 are handled via the management node 24 (e.g., via the network management unit 34) in conjunction with the RBS 16 enabling such functionality (e.g., via the power management unit 33 and / or the status reporting unit 32).

[0139] For increased accuracy and control, frequent monitoring (eg, on a one-minute scale) from the network management unit 34 may be required to meet AS / FCR service requirements.

[0140] Alarms during operation may be raised by the RBS 16 and may be handled directly with corresponding actions from the network management unit 34. Local control functionality (eg implemented at the power management unit 33) may have a shorter time scale, such as 1 second.

[0141] A synchronization signal may be sent to a cluster (e.g., primary cluster 100 or standby cluster 102) prior to a service / activity hour, for example, by sending the profile(s) to one or more RBSs 16. The profile(s) may be executed by the one or more RBSs 16 during the hour. Optional profile controls may be included in the operation, such as a) synchronization upon every demand from a network management unit 34 (e.g., ENM / OSS) executing the profile; and / or b) execution at a local level, locally on a local controller (e.g., processing circuitry 68 of an RBS 16) and based on various thresholds provided by the profile(s).

[0142] In one embodiment, functionality within management node 24 (e.g., network management unit 34) enables orchestration of RBS 16 in providing various FCR services. Some or all FCR service requirements may be embedded within this functionality and / or may be locally activated and operated on each site / RBS 16 or cluster of sites / RBS 16.

[0143] Primary / Standby Cluster Determination and Operation

[0144] like Fig.12As depicted in FIG. 1 , the management node 24 receives FCR signaling (e.g., utility operator signaling 99) from a third-party utility operator (e.g., from a TSO / DSO platform running in the cloud, the details of which are beyond the scope of this disclosure). The utility operator signaling 99 may include, for example, a TSO / DSO activation signal (for turning on / off FCR service), may indicate one or more AS / FCR requirements, may indicate the cost of electricity for one or more time periods, may provide scheduling / timing information, penalty information, bidding information, etc. In one embodiment, for each bidding hour, the management node 24 (e.g., via the network management unit 34) determines two or more clusters, including a primary cluster 100 and a backup cluster 102. The primary cluster 100 (e.g., the serving cluster) may be responsible for answering all FCR requests and policy requirements during the bidding hour, while the backup cluster 102 (e.g., the backup cluster) acts as a redundant asset for backup purposes in the event of a failure of one or more RBSs 16 of the primary cluster 100. The backup cluster 102 may be important due to unpredictable system failures related to RBS 16 alarms and alarm handling. The primary cluster 100 and the backup cluster 102 may be defined / determined the day before the bidding hour and / or on the day of the bidding hour, and may be activated on the service day (intraday). Additional primary clusters 100 and / or additional backup clusters 102 may be utilized without departing from the scope of the present disclosure.

[0145] In one embodiment, management node 24 determines a cluster relationship between primary cluster 100 and backup cluster 102 .

[0146] RBS16 cluster synchronization and control

[0147] During the bidding hour, a service alarm may be raised, and for various reasons the RBS 16 may not be able to deliver the pre-agreed power level subject to the primary cluster 100. For example, the RBS 16x of the primary cluster 100 may not be able to reduce power consumption from the grid 95 (e.g., its battery is dead, its traffic load is too high, etc.), or the RBS 16x may not be able to increase power consumption from the grid 95 (e.g., its battery 59 may be fully charged, its traffic load may be too low, etc.). In either case, an alarm may be raised and transmitted to the network manager unit 34 to handle the RBS 16x alarm. To avoid penalties resulting from not meeting the power request, the network manager unit 34 may select one or more other RBSs 16y from the backup cluster 102 (which may be predefined and ready to be activated), remove the RBS 16x from the primary cluster 100 (and terminate the provision of FCR service by the RBS 16x, for example by instructing the RBS 16x to ignore future FCR activation signals), replace the RBS 16x with one or more other RBSs 16y from the backup cluster 102 by switching the RBS 16y from the backup cluster 102 to the primary cluster 100 and activating the FCR service on the RBS 16y, which may include transmitting a profile (or updated profile) and / or other synchronization signals to the RBS 16y and / or RBS 16x. Additional RBSs 16 may be determined / selected and added to the backup cluster 102 to replace the RBS 16y that was switched to the primary cluster 100.

[0148] In another embodiment, cluster determination (i.e., determining which RBSs 16 are to be assigned to the primary cluster 100 and which RBSs 16 are to be assigned to the backup cluster 102) can be based on an optimization process / algorithm, such as a Dantzig-Wolfe decomposition of a mixed integer linear program (MILP), where the objective function is to find the most profitable cluster for the next day's bidding hour (e.g., determining which RBSs 16 are to be assigned to the primary cluster 100) and the most profitable time period (or multiple time periods, depending on the setup) to participate in, seeking maximum profit gain and minimum battery degradation without compromising the quality of service on the wireless communication network 10.

[0149] Fig.13A diagram of a model workflow describing an example optimization process is illustrated. In step S1 (next day FCR events), grid requests from a utility (TSO) are received during the day (e.g., via management node 24). Each FCR request may be received periodically / intervally (e.g., every 9 seconds) and may indicate a power reduction / increase requested by the grid (e.g., as determined by a third-party utility operator to maintain the grid 95 frequency near its nominal value). The indication may provide these power values ​​in watts (W) that may be proportional to the FCR bid capacity. In step S2 (next day clearing bid price), the clearing bid price (one or more) for each hour of the next day is determined / predicted (e.g., via management node 24). These values ​​may be unknown in advance and are only defined during the auction. In some power markets, for example, FCR capacity is auctioned day-ahead based on one-hour time slots (e.g., for the Swedish power market).

[0150] For convenience, embodiments of the present disclosure relate to "day-ahead bidding", but other power markets may employ different timing (e.g., two days in advance, 12 hours in advance, etc.), and the teachings of the present disclosure apply to any power market, regardless of the specific bidding / FCR timing utilized in that market. Thus, as used herein, "day-ahead" may refer to any time period (whether longer or shorter than day-ahead) as defined in a particular power market during which bidding occurs for the provision of future ancillary services (such as FCR services).

[0151] In step S3, the RBS 16 and / or WD 22 traffic for a particular time period (e.g. one or more bidding hours of the next day) is determined / predicted / indicated (e.g. by the management node 24), which may be indicated / represented as, for example, the number of physical resource blocks, the number of connections per RBS 16 (but other parameters / representations may be included / taken into account). In step S4 (Next Day RBS Energy Consumption), the energy consumption of each RBS 16 for the next day is predicted / determined (e.g. by the management node 24), which may be predicted for each potential bidding hour. These values ​​may not be known in advance (i.e. during the day-ahead period), but may be predicted / estimated (e.g. based on historical traffic data for the particular RBS 16, based on historical clearing bid prices, etc.).

[0152] In step S5 (next day conventional electricity price), the price of electricity in the conventional energy market for the next day is determined. These values ​​may be indicated by the utility operator on the day before. In step S6, an optimization process is performed (e.g., by the management node 24), such as according to a decomposed optimization model. In step S7, the optimization process (e.g., as performed by the management node 24) determines the best next day time period (e.g., bidding hours) to bid. In step S8, the optimization process (e.g., as performed by the management node 24) determines the (predicted) most profitable primary cluster 100 and backup cluster 102 (e.g., determining which RBS 16 to assign to each cluster) and the most profitable time period (s) to participate / bid. The optimization model can dynamically (e.g., in real time) monitor the operation of the primary cluster 100 / backup cluster 102 and adjust the parameters of the model accordingly.

[0153] As described above, some of the inputs to the optimization model (e.g., one or more of the inputs to steps S1, S2, S3, and / or S4) may not be known in advance. Therefore, predictions may be made (e.g., by the management node 24) to facilitate application of the optimization model / process. Specific techniques for predicting these inputs are beyond the scope of this disclosure.

[0154] Fig.14 Depicted is an example network architecture according to some embodiments of the present disclosure. Fig.14 In the diagram, twenty RBSs 16 are depicted as belonging to either the primary cluster 100, the backup cluster 102, or neither (i.e., being "unused"). The management node 24 may determine the clusters of RBSs 16 that are to participate in the FCR service (e.g., the primary cluster 100, the backup cluster 102, additional primary and / or backup clusters, etc.), and may determine the primary cluster 100 and backup clusters 102 for each bidding hour (e.g., determining which RBSs 16 are to be assigned to the primary cluster 100 and which are to be assigned to the backup cluster 102).

[0155] Each RBS 16 belonging to the primary cluster 100 is "protected" by at least one RBS 16 belonging to the backup cluster 102 (i.e., each RBS 16 belonging to the primary cluster 100 is associated with at least one RBS 16 belonging to the backup cluster 102), e.g., if an RBS 16 of the primary cluster 100 fails, an RBS 16 belonging to the backup cluster 102 is designated as a (potential) replacement for the associated RBS 16 of the primary cluster 100. Such an association may be based on cell relations, power consumption, radio traffic, battery capacity, location, etc. Fig.14 The dashed lines connecting some RBSs 16 (eg, RBSs in the main cluster 100) are shown in FIG. 1 16 and RBS of standby cluster 1022 16) to represent these relationships. In some embodiments, RBSs 16 belonging to the backup cluster 102 may be "shared" by multiple RBSs 16 of the primary cluster 100 (e.g., RBSs 16 belonging to the backup cluster 102 may be associated with multiple RBSs 16 of the primary cluster 100), under the assumption that only one RBS 16 in the primary cluster may fail at any particular time. In some embodiments, it may be beneficial to select / determine / associate RBSs 16 belonging to the backup cluster 102 with one or more RBSs 16 belonging to the primary cluster 100 based on proximity (e.g., geographic proximity, logical proximity, etc.) to RBSs 16 of the primary cluster 100 (e.g., "protected" RBSs 16), for example to minimize latency, thereby ensuring that RBSs 16 belonging to the backup cluster 102 are similar to RBSs 16 of the primary cluster 100, so that minimal disruption occurs when replacing a "protected" RBS 16 of the primary cluster 100 with an associated RBS 16 of the secondary cluster. In some embodiments, for example, more than one RBS 16 of the backup cluster 102 may protect a given RBS 16 of the primary cluster 100 (i.e., more than one RBS 16 of the backup cluster 102 may be associated with a given RBS 16 of the primary cluster 100) (e.g., based on their battery capacity and SoC) (e.g., Fig.14 RBS 13 16 and RBS 17 16). The specific assignment of RBS 16 to a particular cluster may vary for each bidding hour.

[0156] In another aspect of the present disclosure, a primary cluster 100 and / or a backup cluster 102 is determined / selected to facilitate satisfying one or more future utility requests, e.g., the backup cluster 102 is selected to have a predefined (e.g., by policy) backup power capacity (e.g., 10% of the bid capacity). Note that this power capacity threshold is merely an example, and further, the power capacity threshold may vary, such that 10% may be, for example, a starting number that may be increased / decreased based on future predictions / expectations of operations. Policy-based operations may set variable level thresholds (e.g., determined daily or weekly) at various steps.

[0157] In some embodiments, the RBSs 16 belonging to a particular cluster may be configured with the same profile (e.g., received as a control / synchronization signal from the management node 24). These profiles may define one or more behaviors / conditions / operations / triggers / etc., such as controlling the power management unit 33 (e.g., to determine when to charge / discharge the battery 59 and how much to charge / discharge the battery 59, how much power to increase / decrease through the power supply unit 67), controlling the status reporting unit 32 (e.g., determining what information to report and when / how often to report it), etc., and these behaviors may be shared by one or more RBSs 16 of a particular cluster.

[0158] In another embodiment, the method of forming two clusters gives them the same identity to be able to belong to the same cluster (forming entity) from the utility point of view, but internally each cluster receives a secondary identity to be able to operate and be activated separately. This secondary identity allows for rapid replacement of any given active RBS 16 in the event of a failure (to avoid and minimize penalties).

[0159] Analysis and synchronization

[0160] In another embodiment, clusters can be formed depending on need and operation, for example based on power level, latency, location (proximity to each other), performance, battery capacity (RBS16 battery 59 capacity may vary in different locations), PSU67 capacity, radio interface 62 power consumption, etc.

[0161] Based on the selected profile(s) and / or control signals (eg, signaled to the RBS 16 by the management node 24), different technical effects related to FCR (eg, on the operation of the cluster) may be achieved.

[0162] Decomposition Optimization Model

[0163] In some embodiments of the present disclosure, in order to at least partially solve the problem of identifying the most profitable one-hour bid (e.g., determining which RBS 16 to assign to which clusters, determining how much to bid, which hours to bid, etc.), an optimization based on the Dantzig-Wolfe decomposition method of mixed integer linear programming (MILP) can be utilized. This method includes the main problem of coordinating a set of pricing problems that are solved alternately (as described below) Fig.15 This particular example model only addresses one bidding hour scenario (e.g., when the CSP / MNO wants to participate only during one hour the next day). Other optimization techniques may be utilized without departing from the scope of this disclosure.

[0164] The main and pricing issues are described below. Battery degradation is also detailed below.

[0165] Fig.15 An example solution flow chart according to an embodiment of the present disclosure is depicted. For example, these steps may be performed by the management node 24, or may be performed by any other entity of the system 10. It should be noted that some or all pricing problems may be solved in parallel in order to save computation time. In step S10, an initial set of RBS16 battery 59 schedule configurations is determined. In step S12, the main problem is performed / solved: the most profitable bidding hours are selected for assigning RBS16 using the corresponding clusters of the primary cluster 100 and the backup cluster 102. The values ​​of the dual variables are provided to step S14 (Pricing Problem (PP)), where the generation of an improved RBS16 configuration for time period t is determined. In step S16, it is determined whether the optimality condition is met and all reduced costs are greater than or equal to 0. If not, the enhanced RBS16 configuration is added and provided to the main problem, and the flow goes to step S12 again. If yes, the flow goes to step S18 (Linear Program (LP*) Relaxation). The flow goes to step S20 where an ε-optimal integer linear programming solution (ILP*) is determined / executed.

[0166] Main issue: Base station / battery configuration

[0167] For a given bidding hour participation, the management node 24 (e.g., via the network management unit 34) may identify the set of RBSs 16 (having batteries 59) that are participating in order to answer FCR requests from the utility operator (e.g., by means of utility operator signaling 99). However, the selected RBSs 16 may not participate in every individual FCR event, but as a whole must be able to answer all FCR events during the bidding hour (even if not all parts of the demand may be used).

[0168] Table 2 below depicts an example of potential RBSs participating in a one-hour bidding.

[0169]

[0170] Table 2 - Examples of potential RBS involvement in FCR events within a single t period.

[0171] Note that within a single time period t, there may be multiple events to be answered by the selected RBS 16. In addition, the selection of RBSs 16 is divided into primary and standby RBSs 16 (ie, as described herein with respect to Fig.14 As depicted, the RBSs 16 are assigned to the primary cluster 100 and the backup cluster 102 , respectively. In the event that one or more of the primary RBSs 16 experience a failure, the backup RBSs 16 may be considered “backup” RBSs 16 .

[0172] For a given RBS 16b and a given time period t, the battery configuration γ is defined by the set of FCR events that the RBS 16b participates in at time t. As an example, Fig.16 As can be seen in the figure, each RBS16 (for example, RBS 1 16. RBS 2 16. RBS 3 16) There may be a different number of generated configurations within each time slot (eg, time slot 104 from 3pm to 4pm), where '0' indicates non-participation and '1' indicates participation. Fig.16 In the example, RBS 1 16 At time slot 104, participate in event e 1 and e 3 , while RBS 2 16 and RBS n 16 only participated in the event 1 (eg, participation in 106a, 106b, and 106c).

[0173] Such a configuration γ∈Γ is characterized in the model by the following terms:

[0174] If RBS 16b can participate in the bidding in time period t, then Otherwise 0.

[0175] =Energy consumed from the grid and stored in the battery 59 of the RBS 16b during hour t (during the FCR upward request).

[0176] = Reduction in energy grid consumption (obtained by providing RBS b with its battery) during time period t (during FCR down request).

[0177] = the state of charge of the battery 59 of RBS b at the end of time period t.

[0178] = Battery degradation of battery 59 of RBS b at the end of time period t. See equation (48) below and the "Calculating Battery Degradation" section.

[0179] parameter

[0180] B: the number / set of base stations b.

[0181] T: The number of intervals or time slots t within a trading day.

[0182] t: one-hour time slot index

[0183] b: RBS index

[0184] e b : Power range of RBS b (RBS16b)

[0185] a: Power area of ​​RBS b

[0186] A b : Available capacity (in %)

[0187] A ELEC :Set the power zone α

[0188] The sum of FCR upward adjustment requests at hour t (in W)

[0189] The sum of FCR downward adjustment requests at hour t (in W)

[0190] RBS b is the capacity of the battery to absorb energy

[0191] RBS b is the capacity of the battery to release energy

[0192] Battery replacement cost for RBS b

[0193] p REP : Battery replacement cost for RBS b (in $ / W)

[0194] Battery capacity of RBS b

[0195] Maximum battery charge level for RBS b

[0196] Maximum battery charge level of RBS b during time t

[0197] Minimum battery charge level of RBS b during time t

[0198] Minimum battery charge level for RBS b

[0199] Initial battery charge level of RBS b during time t

[0200] Initial battery charge level of RBS b

[0201] Power consumption of RBS b during time t

[0202] Dist b，b′ : The distance between RBSb and b' (in meters)

[0203] w 1 and w 2 : The weights of the last two components of the optimization objective

[0204] p BID : Negotiated power bids

[0205] = the energy price in the conventional market at hour t (in $ / W).

[0206] = FCR clearing price at hour t (in $ / W). The clearing price is the equilibrium monetary value of a traded security, asset, or commodity. This price may be determined by a bidding process between buyers and sellers, or more generally, by the interaction of supply and demand forces, government regulations, etc.

[0207] = Penalty price (in $ / W) for hour t when FCR demand cannot be met.

[0208] N(b) = Neighborhood of RBS 16b: If RBS 16b fails / is faulty, each RBS 16b' belonging to it can act as a backup RBS 16. It is called spare RBS 16. In some embodiments, each N(b) is formed by the k closest RBSs 16 to b (k is also a parameter).

[0209] = Energy consumption (in W) for operation of RBS 16b during hour t.

[0210] variable

[0211] z γ ∈{0, 1}: if configuration γ is selected, otherwise 0.

[0212] 1 if RBS 16b is bidding as the primary RBS 16, 0 otherwise.

[0213] If RBS 16b is bidding as backup RBS 16, otherwise it is 0.

[0214] 1 if RBS 16b is bidding as the primary RBS 16 during time period t, 0 otherwise.

[0215] It is 1 if RBS 16b is bidding as a backup RBS 16 during time period t, and 0 otherwise.

[0216] y t ∈{0,1}: 1 if t is the best time to participate in the bidding, 0 otherwise.

[0217] If a RBS 16 is selected for participation in a tender for the electricity sector e, then s e =1, otherwise 0.

[0218] s a ∈{0,1}: 1 if some RBS16 is selected for bidding participation in power region a, 0 otherwise

[0219] Cluster diameter

[0220] Example 1 - Optimization Model Example: One Bidding Hour and Maximum Profit

[0221] In some embodiments of the present disclosure, an optimization model for identifying the best bidding hour (assuming a single day-ahead bidding hour is selected (e.g., out of the available 24 bidding hours)) is used to determine the bidding hour that results in the maximum profit as shown below:

[0222] maxprofit (Equation 1)

[0223] in

[0224]

[0225] and

[0226]

[0227] in:

[0228] The total FCR_UP and FCR_DOWN contributions for each hour are modeled by the following equations:

[0229]

[0230]

[0231] The penalty for not providing the requested FCR requirement is modeled by the following equation:

[0232]

[0233] Recharging of the battery 59 (to full load level, using periodic arbitrage energy services) is modeled according to the following equation:

[0234]

[0235] The total battery 59 degradation rate is modeled as:

[0236]

[0237] The objective function can be rewritten as follows:

[0238]

[0239] where the last two terms are constant values ​​(and can therefore be omitted during optimization), and where

[0240]

[0241] constraint:

[0242] Select the participating RBS16 (primary and backup)

[0243]

[0244] Select a single bidding hour to participate

[0245]

[0246] At least one backup RBS 16 is guaranteed for each selected primary RBS 16

[0247]

[0248] The reduction in grid consumption of energy used to answer FCR down services is limited by the energy consumption of the RBS 16. SoC Limitation: See pricing discussion above.

[0249]

[0250] The backup RBS 16 must provide their SoC to the loads of the protected primary RBS 16. Assumption: No more than one RBS 16 fails at any time

[0251]

[0252] Selecting RBS 16 in the same geographical area (e.g. based on a predefined diameter)

[0253]

[0254] Make sure to select RBS16 in the same power zone

[0255]

[0256]

[0257] The scope of a variable

[0258]

[0259] y t t∈T (Equation 29)

[0260] s e ∈{0,1} e∈E (Equation 30)

[0261] z γ ∈{0,1} γ∈Γ (Equation 31)

[0262] The constraint (Equation 16) determines which RBS 16 battery configuration is selected for a given RBS 16 and time period. Then RBS 16b participates in the bidding event during time period t, otherwise it is 0.

[0263] The constraint (Equation 17) concerns the variable and The consistency of the value of Then in at least one time slot the variable On the other hand, if the variable For t∈T all equal to 0, then Similarly, a constraint (Equation 18) is written to ensure that the variable and The consistency between them.

[0264] The constraints (Equation 19) and (Equation 20) select the hour period of participation: if the variable y t =1, then base station b participates in the bidding event in time period t either as the primary or as the backup (but not both), otherwise it is 0.

[0265] The constraint (Equation 21) ensures that at least one backup RBS 16 is selected for each primary RBS in a closed neighborhood of each primary RBS 16.

[0266] The constraint (Equation 22) ensures that the reduction in energy grid consumption (FCR down service) is limited by the RBS 16 energy.

[0267] The constraint (Equation 23) ensures that the backup RBSs 16 have sufficient power load (SoC) to protect the primary RBSs 16 in the event of a single RBS 16 failure, ie, their overall SoC is greater than the required energy of the failed primary RBS 16 .

[0268] The constraint (Equation 24) ensures that the selected RBSs 16 are in the same geographical area. This is checked using the diameter, ie the farthest RBS 16 is checked to be within a given threshold (ie the input diameter value). Other constraints may be added, such as for example being within the same urban area.

[0269] Constraints (Equation 25) and (Equation 26) ensure that RBS 16 in the same power zone are selected.

[0270] Constraints (Equation 27) to (Equation 31) describe the variable domain.

[0271] Pricing Problem: Generate hourly FCR patterns for a given participating RBS16

[0272] The following problem / solution is described from the perspective of a given RBS 16b and a given time period (hours) t, and therefore b and t indices are omitted below to simplify notation. The pricing problem describes the set of FCR events in which the RBS 16 under study is participating and how many during the time period under study.

[0273] Assumptions: Since the model is for a single bidding hourly period, it can be assumed that the time period begins with a fully loaded battery 59. In one or more embodiments, the model can be used for multiple bidding hourly periods.

[0274] Output of the pricing problem associated with the FCR configuration γ during time period t: Battery degradation and SoC as measured by (Eq. 48) t .

[0275] The pricing problem allows to calculate the SoC for a given t t and DoD t The value of (assuming knowledge of all individual FCR events (on the order of seconds)). It depends on the participation of the individual FCR events. Therefore, for a given t, different hourly FCR configurations are considered and then the solution to the main problem is used to select the best (i.e. the one that leads to the greatest profit) configuration. Each will vary with the participation of the RBS 16 battery 59 in each individual FCR event.

[0276] variable:

[0277] If the RBS16 under investigation is participating in FCR event e, then y e =1, otherwise 0.

[0278] If the battery 59 of the RBS 16 under consideration participates in the bidding, then a=1, otherwise it is 0.

[0279] SoC e = the state of charge of the battery 59 of the RBS 16 under consideration at the end of event e.

[0280] =Energy received from the grid and stored in battery 59 (in response to FCR up event e).

[0281] = Provided by the battery to supply RBS (in response to FCR down event e)

[0282] 16 energy.

[0283] Example: Consider a given RBS 16 with a set of FCR events during time t: E during time t = {e 1 , e 2 , ..., e 10} → (low-level pricing output) SoC at the end of time t t and DoD t .

[0284] Configuration 1: τ 1 → RBS16 under investigation for involvement in FCR incident 1 and e 7 .

[0285] Configuration 2: τ 2 → RBS16 under investigation for involvement in FCR incident 1 、e 7 and e 9 .

[0286] Goal: Reduced costs

[0287] Linear programming: The maximum cx obeys: Ax≤b, x≥0.

[0288]

[0289] Reduced costs The algebraic formula is: For column j

[0290]

[0291] Where i is the row index

[0292]

[0293] Where COST is described in (Equation 15) γ . Omitting the indices b and t becomes:

[0294]

[0295] constraint:

[0296] BS participation means participation in at least one FCR event

[0297] a≥y e e∈E (Equation 36)

[0298] SoC value after each event: if there is no participation, the value does not change. Note that if there is no participation, the E value is empty

[0299]

[0300] Participate in the FCR upward event. The linear version requires writing two sets of constraints.

[0301]

[0302]

[0303] Participate in FCR Down events.

[0304]

[0305] SoC must stay within valid boundaries

[0306] SoC min ≤SoC e ≤SoC max e∈E (Equation 42)

[0307] The scope of a variable

[0308] a∈{0,1} (Equation 43)

[0309] y e ∈{0,1} e∈E (Equation 44)

[0310]

[0311] Using the solution to the pricing problem, the following values ​​can be calculated, which are the values ​​of the coefficients in the main problem of configuring γ(b, t):

[0312]

[0313] in express The rounded value that is closest to the set of discrete battery discharge values.

[0314] Example 2 - Optimization Model: One Bidding Hour

[0315] Objective: maximize profit (capacity and energy compensation profit) and minimize penalties, battery degradation costs, cluster range (diameter) and number of selected RBS 16.

[0316]

[0317] For t∈T, b∈B:

[0318] Total FCR-up and FCR-down contributions per hour of time.

[0319]

[0320] Penalties for not providing requested FCR requirements.

[0321]

[0322] Calculate the sum of the degradation costs of all batteries.

[0323]

[0324] The objective function can be rewritten as follows:

[0325]

[0326] where the last three terms are constant values ​​(and can therefore be omitted during optimization), and where:

[0327]

[0328] constraint:

[0329] Select the participating RBS16 (primary and backup):

[0330]

[0331] Select a single bidding hour to participate:

[0332]

[0333] Guarantee: The entity will not provide more energy than requested in either the up- or down-throttle:

[0334]

[0335] Ensure that the entity is able to answer requests with the maximum agreed power bid (in MW) in both directions:

[0336]

[0337]

[0338] Ensure that the entity has enough energy available (in MWh) to be fully activated in both directions for at least 15 minutes:

[0339]

[0340] At least one backup RBS 16 is guaranteed for each primary RBS 16:

[0341]

[0342] The spare RBSs 16 must be prepared to provide their SoC for all FCR requests related to their primary RBS 16:

[0343]

[0344] Select RBS16 in the same geographical area:

[0345]

[0346] Select RBS16 in the same power region:

[0347]

[0348] The domain of the variable:

[0349]

[0350] y t ∈{0,1} t∈T, (Equation 23A)

[0351] s α ∈{0,1}, α∈A ELEC (Equation 24A)

[0352] z γ ∈{0,1}, γ∈Γ (Equation 25A)

[0353]

[0354] The constraint (Equation 4A) determines which RBS 16 battery configuration is selected for a given RBS 16 and time period. Then RBS 16b participates in the bidding event during time period t, otherwise it is 0.

[0355] The constraint (Equation 5A) concerns the variable and The consistency of the value of Then in at least one time slot the variable On the other hand, if the variable For all t∈T equal to 0, then

[0356] Similarly, a constraint (Equation 6A) is written to ensure that the variable and The consistency between them.

[0357] The constraints (Equation 7A) and (Equation 8A) select the hourly period of participation. If the variable y t =1, then RBS 16b participates in the bidding event for time period t either as primary or as backup (but not both), otherwise it is 0.

[0358] The constraints (Equation 9A) and (Equation 10A) ensure that all selected RBSs 16 operating as primary will not provide more energy than requested in either upward or downward regulation.

[0359] Constraints (Equation 11A) and (Equation 12A) ensure that the entities (all selected primary RBSs 16) have a greater discharge power capacity than the bid value and also have a greater absorption power capacity than the bid value (satisfying upward and downward regulation power requirements, respectively).

[0360] The constraints (Equation 13A) and (Equation 14A) guarantee that the entities (all selected primary RBSs 16) have enough energy to discharge until the bid value is reached (upward-regulation) and recharge until the bid value is reached (downward-regulation), respectively. However, units with limited energy reserves may be able to be fully activated for at least 15 minutes within the bid hour. The constraint (Equation 15A) ensures that at least one backup RBS 16 will be selected for each primary RBS 16.

[0361] Constraints (Equation 16A) and (Equation 17A) ensure that the selected backup RBS 16 has sufficient energy to handle all FCR requests (upward and downward) associated with the primary RBS 16. In other words, when b fails, b' is prepared to contribute to the bidding in place of b.

[0362] The constraint (Eq. 18A) together with the objective function (see Eq. 1A) ensures that: all distances DIST between all selected RBS16b and b' are taken into account b，b′ , minimize the cluster diameter δ DIAM .

[0363] Constraints (Equation 19A) and (Equation 20A) ensure that all selected primary and backup RBSs 16 belong to the same power zone. And finally, constraints (Equation 21A) to (Equation 26A) concern the domains of the variables.

[0364] Pricing Problem: Generate hourly FCR patterns for a given participating RBS16

[0365] It is written for a given RBS 16b and a given time period (hours) t, so that the b and t indices can be omitted to simplify the notation. It describes the contribution of the RBS 16 under study (the set of FCR requests (events) for participation t).

[0366] Let E be the set of events with non-zero FCR (indexed by e). The set E is partitioned into E Down and E Up (for downward regulation requests and upward regulation requests respectively). Each FCR event is associated with a given requested energy amount or Note that BS b may contribute only partially to the requested event e and may not participate in all events.

[0367] The pricing problem allows to calculate the contribution for a given RBS 16b and time t and and its related battery degradation D bt As described in (Equation 28A) and (Equation 29A), the contributions are defined and calculated considering all event participations. The output of the pricing problem is associated with the FCR configuration τ during time period t. Each newly generated configuration is inserted into the main problem only if it can improve the solution.

[0368] variable

[0369] SoC e = the charge state of the battery of the base station under consideration after FCR event e.

[0370] = Reduction in energy grid consumption (obtained by providing the RBS 16 under investigation with its battery) for FCR event e.

[0371] = the energy consumed from the grid and stored in the batteries of the RBS 16 under investigation for FCR event e.

[0372] D t =battery degradation rate associated with the current time t (see subsection VB).

[0373] Example: Consider a given RBS 16b and a set of FCR events E = {e 1 , e 2 , ..., e 10}. At the end of time t, the output of low-level pricing can be represented by the following formula:

[0374]

[0375] Goal: Reduced costs

[0376] With each variable z γ The associated reduced cost can be written as:

[0377]

[0378] where COST is described in Equation (7A) γ ,and u (Eq.9A) ≥0,u (Eq.10A) ≥10,u (Eq.16A) ≥0 and u (Eq.17A) ≥0 are the dual value vectors of constraints (Equation 4A), (Equation 9A), (Equation 10A), (Equation 16A), (Equation 17A) respectively

[0379]

[0380] In the expression instead of (See (Equation 3A)) and after substituting the above expressions (Equation 28A) and (Equation 29A) into (Equation 27A) and (Equation 3A):

[0381]

[0382] The constraints are written as follows.

[0383] Non-zero FCR events are associated with either up or down regulation. Therefore, the set E can be represented by the following formula:

[0384]

[0385] In addition, assuming where e 0 is an artificial event of the initial charge state of the battery containing RBS16b. pred (e) shows the SoC value at the end of the previous FCR event.

[0386] Update SoC value:

[0387]

[0388] Participate in FCR Down Events:

[0389]

[0390] Participate in FCR Upward Events:

[0391]

[0392] The SoC must stay within certain boundaries:

[0393]

[0394] For the requested connection contribution:

[0395]

[0396] The constraints (Equation 31A) and (Equation 32A) concern the SoC value update after each FCR participates. Note that the artificial event e representing the initial SoC is included in the set 0 Therefore, in and After each FCR participation indicated, the SoC value at the end of the current event is updated. If there is no participation, the SoC value remains unchanged.

[0397] The constraint (Equation 33A) handles downward regulation requests, which means reducing energy production or increasing consumption (in our case, by charging the battery). Since the battery has a finite storage capacity, (Equation 33A) ensures that: max -SoC e ) the battery will not receive any more energy than the

[0398] On the other hand, constraints (Equation 34A) and (Equation 35A) deal with upward-regulation requests, which means increasing energy production or reducing consumption. In one or more embodiments, in order to reduce energy consumption, the RBS 16b is partially or fully powered by its battery. More specifically, the constraint (Equation 34A) ensures that the reduction in energy consumption is less than or equal to the current energy consumption of the RBS 16 under analysis.

[0399] The constraint (Equation 35A) ensures that: min The battery will not be discharged further than the current value.

[0400] The constraint (Equation 36A) ensures that the SoC remains within its allowed boundaries. And finally, constraints (Equation 37A) and (Equation 38A) ensure that no more energy will be provided than requested.

[0401] It is worth noting that to simplify the model, charge / discharge losses (regarding battery efficiency) are not considered.

[0402] Calculate battery degradation:

[0403] Using the same solution to the pricing problem, the battery degradation can be deduced as D, taking into account the degradation caused by each event. t The estimates are as follows:

[0404]

[0405] The calculation of battery degradation can be performed based on a degradation curve (e.g., maximum cycles versus DoD). Since this curve is nonlinear, it may be necessary to linearize it using some method (e.g., piecewise approximation) so that it can be introduced into our model. Then, after the linearization method, the curve is divided into d linear parts. Assuming that the end of battery life (EoL) occurs when its nominal capacity drops by 20%, the degradation rate for each DoD value can be determined as follows:

[0406]

[0407] where D is the degradation rate (in pu / cycle) and N max_cycles is the maximum number of cycles under each specific DoD. Then, each segment of the degradation rate can be described as follows:

[0408]

[0409] Where D d is the degradation rate value (pu / cycle) of a specific DoD in segment d, DoD e，d is the DoD in segment d at time event e, is the slope of segment d, and is the y-intercept point of segment d. The following equation restricts the DoD to a specific segment:

[0410]

[0411] The parameters and are the minimum and maximum values ​​of DoD for each segment d, respectively. In order to introduce the degradation rate of each event into the model, the following restrictions are necessary:

[0412]

[0413]

[0414] in is a binary variable indicating the segment corresponding to the battery discharge, E CAP Indicates the total battery capacity, and D e is the degradation rate at event e. Equation (Equation 53) relates the relationship between energy release and DoD. Equations (Equation 54)-(Equation 56) assign the total DoD obtained using (Equation 40) to a specific segment of the curve. Equation (57) determines the degradation rate at event e.

[0415] Battery maintenance strategies can therefore impact overall profits.

[0416] Fig.17A -D depicts the recent ( Fig.17A), within the day ( Fig. 17B ), during synchronization and orchestration of operations of the failed RBS 16 ( Fig. 17C ) and report generation after the end of the operation and bidding hours ( Fig.17D ) example timing diagram.

[0417] Fig.17A (Step A: Day-Ahead) depicts an example day-ahead process during which the network management unit 34 examines the FCR services available for participation / bidding in a given power region / grid / region / etc. It should be noted that although the term "day-ahead" is used in this example, "day-ahead" is merely used as an example time period, which may vary, for example, based on the configuration of a particular grid and / or utility operator. For example, a utility operator may solicit FCR bids at any time period prior to the bidding hour (e.g., day-ahead, two days in advance, two hours in advance, one year in advance, etc.). In other words, the "day-ahead" period as used herein refers to the period during which the utility company solicits bids, which may or may not be the actual day before the FCR period that is the subject of the bid. Note that these steps are described as being performed by the network management unit 34, but it is to be understood that in some embodiments, one or more of these steps may also / alternatively be performed by one or more other units / entities of the management node 24, RBS 16, core node 14, etc., without departing from the scope of the present disclosure.

[0418] In step A.1, the network management unit 34 collects information of all RBSs 16 available in a particular area / grid / region / etc. Specifically, in step S150, the network management unit examines the FCR service of a particular utility area to determine participation and service requirements. In step S152, the network management unit 34 requests information from one or more active RBSs 16 (e.g., from one or more of the RBS n+1 in the primary cluster 100 in the utility area) to determine a list of participating RBSs 16 or a similar data structure, which may include, for example, RBS ID, location [longitude, latitude], power capacity [W], battery [Wh], alarms, constraints, capabilities, etc., which may be reported in step S154, for example, by the status reporting unit 32 of one or more RBSs 16 of the primary cluster 100, along with an acknowledgement. In step S156, the network management unit 34 requests information from one or more RBSs 16 of the standby cluster 102, similar to the information requested in step S152, and one or more of the RBSs 16 respond accordingly, similar to the response of step S158. The network management unit 34 now has information corresponding to the identity and status / status of the plurality of RBSs 16 in each of the primary cluster 100 and the backup cluster 102 .

[0419] If the primary cluster 100 and / or the backup cluster 102 have not been previously determined, the network management unit 34 may be pre-configured with a list or similar data structure identifying candidate RBSs 16 in the utility area for assignment to the new primary cluster 100 and / or the backup cluster 102. In some embodiments, the backup cluster 102 may be dynamically selected and may vary during different days, for example, based on the performance of the backup cluster 102, or alternatively may be a policy-defined backup cluster. For example, in step S160, which may be an optional step, a backup policy profile is determined, for example, based on the location of the primary cluster 100, the number of fixed RBSs (one or more) in the backup cluster 102 is determined by policy (e.g., 10%, 5%, etc.).

[0420] In step A.2, the network management unit 34 runs an optimization model for data prediction (as described herein) and uses the optimization model to find the best time slot(s) to participate / bid for, to determine which RBS 16 to assign to one or more primary clusters 100, which RBS 16 to assign to one or more backup clusters 102, to determine which profiles to assign to which RBS 16 / which clusters, etc. Specifically, in step S162, the network management unit 34 performs optimization calculations as described herein for assigning one or more RBSs 16 to various clusters, and / or for determining the profile(s) to assign to the RBS 16 for local implementation of AS / FCR. In step S164, which may be an optional step, the network management unit 34 causes the profile to be sent to one or more RBSs 16 of the primary cluster 100 and / or the backup cluster 102, thereby enabling local control and reducing the delay associated with control signaling from the network management unit 34 / management node 24 to each of the RBSs 16. For example, a profile may specify / instruct the RBS 16 (e.g., the power management unit 33) to use one or more thresholds (e.g., maximum battery 59 charge, minimum battery 59 charge, etc.), timing values, performance parameters, etc. to control power consumption, for example, by powering / powering one or more elements of the hardware 58 in response to signals received from the network management unit 34, the power grid 95, utility operator signaling 99, other RBSs 16 (e.g., other RBSs 16 of the primary cluster 100 that relays the activation signal), etc.

[0421] In step A.3, the network management unit 34 performs synchronization of the primary cluster 100 and the backup cluster 102, as described herein, which synchronization may be either periodic and / or aperiodic (e.g., based on conditions), such as by causing a profile to be transmitted to one or more of the RBSs 16 in each cluster, the profile being configured to cause the RBSs 16 in each cluster to implement the provided AS / FCR service. Specifically, in step S166, the network management unit 34 causes synchronization signaling (such as a profile) to be sent to one or more RBSs 16 of the primary cluster 100. In step S168, the one or more RBSs 16 of the primary cluster 100 respond with an acknowledgement and / or with status information (e.g., as reported by the status reporting unit 32). Similarly, in step S170, the profile is sent to one or more RBSs 16 of the backup cluster 102, which respond similarly to the response of step S170.

[0422] Fig. 17B (Step B, intra-day) depicts an example intra-day process. In step B.1, the network management unit 34 checks the status of the RBSs 16 of the primary cluster 100 and / or the backup cluster 102. Specifically, in step S174, the network management unit 34 checks whether the performance / status / battery 59 status / etc. (e.g., as monitored by one or more status reporting units 32 of one or more corresponding RBSs 16) has changed on the primary cluster 100 and / or the backup cluster 102, for example by requesting and receiving from the RBSs 16 / status reporting units 32 a status report indicating the status / condition / etc. of the hardware 58 of one or more RBSs 16 in each cluster, indicating which (if any) RBSs 16 are experiencing a fault / error condition, indicating a traffic condition (e.g., actual or predicted, based on control information indicating traffic demand received from one or more wireless devices 22 served by the corresponding RBSs 16), etc. Similarly, in step S176, the network management unit 34 requests and receives status information from one or more RBSs 16 of the standby cluster 102. If the status of any of the RBSs 16 of the primary cluster 100 has changed (i.e., such that the RBS 16 no longer meets one or more requirements for participating in the AS / FCR service), the network management unit 34 replaces at least one RBS 16 from the primary cluster 100 with at least one other RBS 16 from the standby cluster 102 in steps S178 and S180. Optionally, as described herein, the network management unit 34 finds at least one replacement RBS 16 to re-complete / re-populate the standby cluster 102.

[0423] In step B.2, the network management unit 34 synchronizes the primary cluster 100 and / or the backup cluster 102, which synchronization may be periodic and / or aperiodic (e.g., based on conditions). Specifically, in step S182, the network management unit 34 causes synchronization signaling (such as a profile) to be sent to one or more RBSs 16 of the primary cluster 100. In step S184, the one or more RBSs 16 of the primary cluster 100 respond with an acknowledgement and / or with status information (e.g., as reported by the status reporting unit 32). Similarly, in step S186, the profile is sent to one or more RBSs 16 of the backup cluster 102, which respond similarly to the response of step S188.

[0424] Fig. 17C (Step C) depicts an example active hour (bid hour) operation. In step C.1, the network management unit 34 monitors for incoming FCR activation signals received, for example, from an electric utility. As previously noted herein, an "active hour" or "bid hour" can be any length of time (e.g., 1 hour, 30 minutes, 30 seconds, etc.) defined / determined, for example, based on a bidding process for the grid. Specifically, in step S190, the network management unit 34 monitors AS / FCR service for a particular utility area, such as receiving a set of indications corresponding to participation and service requirements from a utility operator (e.g., via utility operator signaling 99), and / or monitoring activation signals, and / or monitoring changes in conditions in the grid 95 that trigger AS / FCR service. In step S192, an arbitrary amount of time passes. In steps S194 and S196, the network management unit 34 initiates a 1 minute synchronization of the RBSs 16 of the primary cluster 100 and the RBSs 16 of the secondary cluster 102, respectively, every minute in 15 minute increments prior to the activity hour (note that these are merely example times and the specific time intervals / period lengths may vary based on power utility preferences / requirements, MNO preferences / requirements, optimization processes, etc.). The synchronization process may include, for example, causing a profile to be transmitted to one or more RBSs 16 in the cluster prior to the bidding hour and during the activity / service / operation hour. The synchronization may be used to run tests / simulations prior to or during the activity / service / operation hour, for example, performing a test activation to determine whether the RBSs 16 of the primary cluster 100 are able to meet timing, latency, and / or power modification requirements. In steps 198 and S200, the RBSs 16 of the primary cluster 100 and the backup cluster 102 respectively indicate to the network management unit 34 that synchronization is complete (i.e., the RBSs 16 are operating as required, the profile has been successfully received and implemented, (one or more) tests are running without failures / errors, etc.).

[0425] In step C.2, the network management unit 34 performs normal synchronization (e.g., causes the profile to be transmitted to the RBS 16 in the appropriate cluster along with updated instructions for implementing the AS / FCR service). In step C.3, the network management unit 34 checks for alarms and, if a failure occurs, enables the next RBS 16 from the backup cluster 102 to participate. Specifically, steps S202, S204 and S206 describe a similar process for replacing the RBS 16 of the primary cluster 100 with the RBS 16 of the secondary cluster 102, as described above in relation to steps S178 and S180. In step S208, the network management unit 34 either initiates the start of a new cluster, and / or waits for an activation signal for the AS / FCR service.

[0426] Fig.17D An example reporting process (step S210) is depicted which, for example, occurs after the end of an activity hour, with the network management unit 34 generating a report which may include, for example, the RBS ID, power level delivered to the grid 95 (in Watts), SoC (e.g., as a % of total charge capacity), battery 59 degradation (e.g., as a % of initial charge capacity), cost / cost reduction (e.g., in %), and determined profit (e.g., in USD / EUR / etc.).

[0427] Synchronization of clusters based on performance from the network management unit 34

[0428] In finding the best cluster for participating in each next-day bidding hour (e.g., selecting the RBS 16 that results in the greatest profit while minimizing disruption to the quality of service provided to the wireless device 22 and / or minimizing degradation to the battery 59) (e.g., Fig.14 ), the network management unit 34 enables synchronization signals (periodic or aperiodic) / determines the profile and causes the profile to be transmitted to the RBS 16 during the day so that the multiple RBSs 16 of each cluster are aligned with each other and their status is constantly checked (e.g. as reported by the status reporting unit 32). Note that this synchronization signaling that can be sent via the connection 66 is not necessarily the same signal as the activation signaling received from the utility operator (e.g. by means of utility operator signaling 99), although the management node 24 can cause the activation signaling to be forwarded / relayed to one or more RBSs 16 via the same connection 66 as the synchronization signaling.

[0429] In some embodiments, the synchronization signaling (e.g., sent via connection 66) can include information / operation settings such as 1) on / off signaling, 2) site profile (e.g., operational settings), 3) battery profile, 4) PSU 67 profile, 5) power profile, 6) load profile, 7) MW / Hz profile, 8) cluster profile, and / or 9) radio profile.

[0430] like Fig.16 As depicted in the example of , a profile may contain thresholds, patterns, and activation signals used to start a service participating RBS 16 or a sequence of RBSs 16, wherein different profiles are used by the power management unit 33 to control different inputs and outputs of one or more of the RBSs 16. For example, Fig.18 Various control signals 109 are depicted for controlling and synchronizing components of each RBS 16 based on profiles received from the network management unit 34 (e.g., via connection 66) and activation signals (e.g., utility operator signaling 99) received from the utility operator (e.g., indirectly received via connection 66, via the network management unit 34). Different profiles may respond differently to control signals, producing different technical effects in operation. The PSU 67 input 110 may be controlled (e.g., based on utility operator signaling 99 indicating an FCR activation request) to facilitate stabilizing input power and setting the PSU 67 input current (e.g., different thresholds) to different input power levels, for example, based on demand. In some embodiments, the profiles of the RBSs 16 of the main cluster 100 are configured so that the PSU 67 inputs within the same cluster have the same or similar values, resulting in similar / stable behavior for the RBSs 16 across the clusters. In response to each FCR request, the RBS 16 may be required (e.g., by utility operator specifications) to deliver stable power in order to avoid penalties.

[0431] The PSU 67 output 111 may be controlled (by the power management unit 33) such that PSU voltage output adjustments may be made to reduce the output voltage and keep the input power constant or to reduce the PSU 67 input power to a specified power level based on demand during a synchronization signal or when local control is applied. In this way, some of the power is delivered from the battery 59.

[0432] The battery 59 input 112 may be controlled (e.g., by the power management unit 33) so as to avoid charging during active bidding hours. Charging may occur later, may occur at night to avoid excessive peak power, or may occur during FCR active hours (e.g., when utility operator signaling 99 including an activation signal is received indicating an FCR-down regulation period in which power consumption of one or more RBSs 16 of the primary cluster 100 should be increased).

[0433] The battery 59 output 113 may be active to support both powering the radio during the FCR request signal (within the same bid / service hour) and supporting powering the radio, including radio power variations.

[0434] The radio input power 114 will depend greatly on radio traffic variations related to the number of wireless devices 22 connected, their traffic needs, time of day, interference / noise levels, signaling efficiency, etc. The radio input power 114 to the radio may fluctuate during operation. In some embodiments, the power management unit 33 can handle such variations in fluctuations within the power architecture (e.g., by appropriately increasing / decreasing power from the battery 59).

[0435] In addition, control profiles may be sent in advance, may be changed during operation, and may be activated locally during service hours. For example, as described herein, each power management unit 33 of one or more RBSs 16 of the main cluster 100 may respond to an activation signal and / or utility operator signaling 99 received from the network management unit 34 by increasing the power supplied to / from the battery (via control signal 109), thereby reducing latency as compared to embodiments in which the network management unit 34 must send one or more of the control signals 109. In addition, profiles may be stored locally or may be changed at any time from a centralized location. In some embodiments of the present disclosure, profiles may be changed or modified intraday based on new information related to the rerun method.

[0436] In some embodiments of the present disclosure, the synchronization signal received via the connection 66 may also contain information relayed from the utility operator signaling 99 and / or may include control information associated with and / or determined based on the utility operator signaling 99. A policy may be set (e.g., by means of a profile signaling the RBS 16) to avoid charging the battery 59 during FCR bidding hours, which may affect the operation of the PSU 67 during unsolicited signal periods during service hours.

[0437] In some embodiments, the network management unit is configured to report values ​​back to the TSO / DSO, such as the power level of one or more RBSs 16, the SoC of one or more batteries 59, and the like.

[0438] Fig.19is a histogram depicting an example simulated PSU 67 output control according to an embodiment of the present disclosure. The histogram depicts the distribution of latency timing of PSU 67 control signaling 109, where the X-axis represents latency in seconds and the Y-axis represents the number of tests. For example, a PSU 67 latency of 1 second is within the limits of actual operation of many FCR services. As another example, the round-trip latency associated with utility operator signaling 99 was calculated / simulated to be 2 seconds. Overall, utilizing existing power infrastructure equipment, the simulation example produced a total latency of between 3.5 and 4 seconds to enable a control signal (e.g., utility operator signaling 99 activating an FCR service). As described in the example of Table 1 above, this is within the limits / requirements of the service.

[0439] Some examples

[0440] Example A1: An RBS 16 powered by a power grid and configured to communicate with a network management unit 34 (e.g., a management node 24), the RBS 16 being configured to and / or comprising a radio interface 62 and / or comprising a processing circuit 68, the processing circuit 68 being configured to:

[0441] receiving a synchronization signal from the network management unit 34, the synchronization signal indicating a schedule including an activation period;

[0442] During the activation period, receiving an activation signal from the network management unit 34; and in response to the activation signal, modifying the power consumption of the RBS 16 based on the synchronization signal and the activation signal.

[0443] Example A2: The RBS 16 of Example A1, wherein the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the RBS 16.

[0444] Example A3: The RBS 16 of Example A2, wherein the AS profile indicates one of a primary cluster and a backup cluster to which the RBS 16 is assigned, the AS profile being shared by at least one other RBS 16 of the cluster to which the RBS 16 is assigned.

[0445] Example A4: An RBS 16 as described in Example A3, wherein the AS profile indicates a backup cluster to which the RBS is assigned, and the RBS 16 is further configured to receive an updated synchronization signal indicating an updated AS profile from a network management unit 34, the updated AS profile indicating a reassignment to a primary cluster, the reassignment being associated with at least one failure condition of another RBS 16 assigned to the primary cluster.

[0446] Example A5: The RBS 16 of any of Examples A1 to A4, wherein the RBS 16 is further configured to:

[0447] determining a status report indicating a condition of the RBS 16; and

[0448] The transmission of a status report to the network management unit 34 is caused, and the synchronization signal is determined based on the status report.

[0449] Example A6: The RBS 16 of any of Examples A1 to A5, wherein the activation signal indicates a frequency control reserve FCR downward adjustment event, and the modification of power consumption by the RBS 16 includes reducing power supplied to the RBS 16 from the grid.

[0450] Example A7: The RBS 16 of Example A6, wherein the RBS 16 includes a battery 59, and reducing the power supplied from the grid includes switching from power supplied by the grid to power supplied by the battery 59.

[0451] Example A8: The RBS 16 of Example A7, wherein the synchronization signal indicates a first threshold and a second threshold lower than the first threshold, the schedule includes a first period before the activation period, and the RBS 16 is further configured to:

[0452] maintaining the battery charge above a first threshold during a first period; and

[0453] The battery charge is reduced to a second threshold during the activation period based on the activation signal indicating a FCR-down regulation event.

[0454] Example A9: The RBS 16 of any of Examples A1 to A8, wherein the activation signal indicates an FCR-up regulation event, and the modification of power consumption by the RBS 16 includes increasing power supplied to the RBS 16 by the grid.

[0455] Example A10 The RBS 16 of any Example A9, wherein the RBS 16 includes a battery, and increasing the power supplied from the grid includes charging the battery 59 .

[0456] Example A11: The RBS 16 of Example A10, wherein the synchronization signal indicates a first threshold and a second threshold higher than the first threshold, the schedule includes a first period before the activation period, and the RBS 16 is further configured to:

[0457] maintaining the battery charge below a first threshold during a first period; and

[0458] The battery charge is increased to a second threshold during the activation period based on the activation signal indicating a FCR-up regulation event.

[0459] Example A12: The RBS of any of Examples A3 to A11, wherein the synchronization signal including the AS profile is received by the RBS 16 before the activity hour, the processing circuit 68 is further configured to:

[0460] The AS profile is executed during the activity hours, the AS profile optionally including a profile control indicating at least one of the following:

[0461] Responding to synchronization of the RBSs from the network management unit 34 to perform each requirement of the AS profile; and

[0462] local execution on at least one local controller; and

[0463] At least one power modification procedure is performed based on at least one threshold indicated by the AS profile.

[0464] Example B1: A method implemented in an RBS 16 powered by a power grid and configured to communicate with a network management unit 34 (eg, a management node 24), the method comprising:

[0465] receiving a synchronization signal from the network management unit 34, the synchronization signal indicating a schedule including an activation period;

[0466] During the activation period, receiving an activation signal from the network management unit 34; and in response to the activation signal, modifying the power consumption of the RBS 16 based on the synchronization signal and the activation signal.

[0467] Example B2: The method of Example B1, wherein the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the RBS 16.

[0468] Example B3: The method of Example B2, wherein the AS profile indicates one of a primary cluster and a backup cluster to which the RBS 16 is assigned, the AS profile being shared by at least one other RBS 16 of the cluster to which the RBS 16 is assigned.

[0469] Example B4: A method as described in Example B3, wherein the AS profile indicates a backup cluster to which RBS16 is assigned, the method further comprising receiving an updated synchronization signal indicating an updated AS profile from the network management unit 34, the updated AS profile indicating a reassignment to the primary cluster, the reassignment being associated with at least one failure condition of another RBS16 assigned to the primary cluster.

[0470] Example B5: The method as described in any of Examples B1 to B4, further comprising:

[0471] determining a status report indicating a condition of the RBS 16; and

[0472] The transmission of a status report to the network management unit 34 is caused, and the synchronization signal is determined based on the status report.

[0473] Example B6: The method of any of Examples B1 to B5, wherein the activation signal indicates a frequency control reserve FCR downward adjustment event, and the modification of power consumption by the RBS 16 includes reducing power supplied to the RBS 16 from the grid.

[0474] Example B7: The method of Example B6, wherein the RBS 16 includes a battery 59 , and reducing the power supplied from the grid includes switching from the power supplied by the grid to the power supplied by the battery 59 .

[0475] Example B8: The method of Example B7, wherein the synchronization signal indicates a first threshold and a second threshold lower than the first threshold, the schedule includes a first period prior to the activation period, the method further comprising:

[0476] maintaining the battery charge above a first threshold during a first period; and

[0477] The battery charge is reduced to a second threshold during the activation period based on the activation signal indicating a FCR-down regulation event.

[0478] Example B9: The method of any of Examples B1 to B8, wherein the activation signal indicates an FCR-up regulation event, the modification of power consumption by the RBS 16 comprising increasing power supplied by the grid to the first RBS 16 .

[0479] Example B10 The method of any Example B9, wherein the RBS 16 includes a battery, and increasing the power supplied from the grid includes charging the battery 59 .

[0480] Example B11: The method of Example B10, wherein the synchronization signal indicates a first threshold and a second threshold that is higher than the first threshold, the schedule includes a first period prior to the activation period, the method further comprising:

[0481] maintaining the battery charge below a first threshold during a first period; and

[0482] The battery charge is increased to a second threshold during the activation period based on the activation signal indicating a FCR-up regulation event.

[0483] Example B12: The method of any of Examples B3 to B11, wherein a synchronization signal including the AS profile is received by the RBS 16 before the activity hour, the method further comprising:

[0484] The AS profile is executed during the activity hours, the AS profile optionally including a profile control indicating at least one of the following:

[0485] Responding to synchronization of the RBS 16 from the network management unit 34 to perform each requirement of the AS profile; and

[0486] local execution on at least one local controller; and

[0487] At least one power modification procedure is performed based on at least one threshold indicated by the AS profile.

[0488] Example C1: A network management unit 34 (eg, management node 24) configured to communicate with a grid operator and with a plurality of RBSs 16, each of the plurality of RBSs 16 being powered by a grid, the network management unit 34 being configured to:

[0489] causing transmission of a synchronization signal to a first RBS 16 of the plurality of RBSs 16, the synchronization signal indicating a schedule including an activation period; and

[0490] During the activation period, transmission of an activation signal is caused to the first RBS 16, the activation signal being configured to cause the first RBS 16 to modify its power consumption based on the synchronization signal.

[0491] Example C2: The network management unit 34 of Example C1, wherein the network management unit 34 is further configured to:

[0492] receiving instructions from the grid operator indicating a bidding schedule and configuration of a frequency control reserve FCR; and

[0493] A primary cluster of a plurality of RBSs 16 participating in the FCR service during an active period of the bidding schedule is determined based on the bidding schedule and the FCR configuration, the primary cluster including the first RBS 16 .

[0494] Example C3 The network management unit 34 of Example C2, wherein the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the first RBS 16 .

[0495] Example C4: The network management unit 34 of Example C3, wherein the AS profile is shared by the RBSs 16 of the primary cluster.

[0496] Example C5: The network management unit 34 of Example C4, wherein the network management unit 34 is further configured to:

[0497] determining a backup cluster of a plurality of RBSs 16 different from the primary cluster based on the bidding schedule and the FCR configuration, the backup cluster including a second RBS 16;

[0498] receiving a status report from the first RBS 16 indicating a fault in the first RBS 16; and

[0499] Based on the received status report, the first RBS 16 is replaced by the second RBS 16 in the following manner:

[0500] causing transmission of a deactivation indication to the first RBS 16, the deactivation indication being configured to cause the first RBS 16 to ignore future activation signals; and

[0501] A transmission of an AS profile to the second RBS 16 is caused, the AS profile indicating reassignment of the second RBS 16 from the standby cluster to the primary cluster.

[0502] Example C6 The network management unit 34 of any of Examples C1 to C4, wherein determining a backup cluster of the plurality of RBSs 16 is based on proximity of the RBSs 16 of the backup cluster to at least one RBS 16 of the primary cluster.

[0503] Example C7 The network management unit 34 of any of Examples C1 to C5, wherein the activation signal indicates an FCR-down event, the modification of power consumption by the first RBS 16 comprising reducing power supplied to the first RBS 16 from the grid.

[0504] Example C8: The network management unit 34 of Example C7, wherein the first RBS 16 includes a battery 59 , and reducing the power supplied from the grid includes switching from the power supplied by the grid to the power supplied by the battery 59 .

[0505] Example C9: The network management unit 34 of Example C8, wherein the synchronization signal indicates a first threshold and a second threshold lower than the first threshold, the schedule includes a first period before the activation period, and the synchronization signal is configured to cause the first RBS 16 to:

[0506] maintaining the battery charge above a first threshold during a first period; and

[0507] The battery charge is reduced to a second threshold during the activation period based on the activation signal indicating a FCR-down regulation event.

[0508] Example C10 The network management unit 34 of any of Examples C1 to C9, wherein the activation signal indicates an FCR-up regulation event, the modification of power consumption by the first RBS 16 comprising increasing power supplied by the grid to the first RBS 16 .

[0509] Example C11 The network management unit 34 of any Example C10, wherein the RBS 16 includes a battery, and increasing the power supplied from the grid includes charging the battery 59 .

[0510] Example C12: The network management unit 34 of Example C11, wherein the synchronization signal indicates a first threshold and a second threshold higher than the first threshold, the schedule includes a first period before the activation period, and the synchronization signal causes the first RBS 16 to:

[0511] maintaining the battery charge below a first threshold during a first period; and

[0512] The battery charge is increased to a second threshold during the activation period based on the activation signal indicating a FCR-up regulation event.

[0513] Example C13: The network management unit 34 of any of Examples C1 to C12, wherein determining the number of RBSs 16 to assign to the primary cluster is based on an optimization model, the optimization model being configured to at least one of:

[0514] Maximize profits;

[0515] Minimize disruption to service quality;

[0516] Minimize battery degradation; and

[0517] Minimize penalties from grid operators.

[0518] Example C14: The network management unit 34 of any of Examples C3 to C13, wherein the transmission of the synchronization signal including the AS profile to the RBS 16 of each cluster occurs before the activity hour, the AS profile optionally including a profile control indicating at least one of the following:

[0519] in response to synchronization of the RBS 16 from the network management unit 34 to execute each requirement of the AS profile, and

[0520] Local execution on at least one local controller is for performing at least one power modification process based on at least one threshold indicated by the AS profile.

[0521] Example D1: A method implemented in a network management unit 34 (e.g., a management node 24), the network management unit 34 being configured to communicate with a grid operator and with a plurality of RBSs 16, each of the plurality of RBSs 16 being powered by a grid, the method comprising:

[0522] causing transmission of a synchronization signal to a first RBS 16 of the plurality of RBSs 16, the synchronization signal indicating a schedule including an activation period; and

[0523] During the activation period, transmission of an activation signal is caused to the first RBS 16, the activation signal being configured to cause the first RBS 16 to modify its power consumption based on the synchronization signal.

[0524] Example D2: The method of Example D1, wherein the method is further configured to:

[0525] receiving instructions from the grid operator indicating a bidding schedule and configuration of a frequency control reserve FCR; and

[0526] A primary cluster of a plurality of RBSs 16 participating in the FCR service during an active period of the bidding schedule is determined based on the bidding schedule and the FCR configuration, the primary cluster including the first RBS 16 .

[0527] Example D3: The method of Example D2, wherein the synchronization signal indicates an auxiliary service AS profile for controlling power consumption of the first RBS 16 .

[0528] Example D4: A method as in Example D3, wherein the AS profile is shared by the RBSs 16 of the primary cluster.

[0529] Example D5: The method as described in Example D4, further comprising:

[0530] determining a backup cluster of a plurality of RBSs different from the primary cluster based on the bidding schedule and the FCR configuration, the backup cluster including a second RBS 16;

[0531] receiving a status report from the first RBS 16 indicating a fault in the first RBS 16; and

[0532] Based on the received status report, the first RBS 16 is replaced by the second RBS 16 in the following manner:

[0533] causing transmission of a deactivation indication to the first RBS 16, the deactivation indication being configured to cause the first RBS 16 to ignore future activation signals; and

[0534] A transmission of an AS profile to the second RBS 16 is caused, the AS profile indicating reassignment of the second RBS 16 from the standby cluster to the primary cluster.

[0535] Example D6: A method as in any of Examples D1 to D4, wherein determining a backup cluster of the plurality of RBSs 16 is based on proximity of the RBSs 16 of the backup cluster to at least one RBS 16 of the primary cluster.

[0536] Example D7: The method of any of Examples D1 to D5, wherein the activation signal indicates an FCR-down regulation event, and the modification of power consumption by the first RBS 16 includes reducing power supplied to the first RBS 16 from the grid.

[0537] Example D8: The method of Example D7, wherein the first RBS 16 includes a battery, and reducing the power supplied from the grid includes switching from the power supplied by the grid to the power supplied by the battery 59 .

[0538] Example D9: The method of Example D8, wherein the synchronization signal indicates a first threshold and a second threshold lower than the first threshold, the schedule includes a first period before the activation period, and the synchronization signal is configured to cause the first RBS 16 to:

[0539] maintaining the battery charge above a first threshold during a first period; and

[0540] The battery charge is reduced to a second threshold during the activation period based on the activation signal indicating a FCR-down regulation event.

[0541] Example D10 The method of any of Examples D1 to D9, wherein the activation signal indicates an FCR-up regulation event, and the modification of power consumption by the first RBS 16 includes increasing power supplied by the grid to the first RBS 16 .

[0542] Example D11 The method of any Example D10, wherein RBS 16 includes battery 59 and increasing the power supplied from the grid includes charging battery 59.

[0543] Example D12: The method of Example D11, wherein the synchronization signal indicates a first threshold and a second threshold higher than the first threshold, the schedule includes a first period before the activation period, and the synchronization signal causes the first RBS 16 to:

[0544] maintaining the battery charge below a first threshold during a first period; and

[0545] The battery charge is increased to a second threshold during the activation period based on the activation signal indicating a FCR-up regulation event.

[0546] Example D13: A method as in any of Examples D1 to D11, wherein determining the number of RBSs 16 to be assigned to the primary cluster is based on an optimization model, the optimization model being configured to at least one of:

[0547] Maximize profits;

[0548] Minimize disruption to service quality;

[0549] Minimize battery degradation; and

[0550] Minimize penalties from grid operators.

[0551] Example D14: The method of any of Examples D3 to D13, wherein the transmission of the synchronization signal including the AS profile to the RBS 16 of each cluster occurs before the activity hour, the AS profile optionally including a profile control indicating at least one of the following:

[0552] Responding to synchronization of the RBS 16 from the network management unit 34 to perform each requirement of the AS profile; and

[0553] Local execution on at least one local controller is for performing at least one power modification process based on at least one threshold indicated by the AS profile.

[0554] Example E1: A system 10, comprising:

[0555] An RBS 16 as described in any of Examples A1 to A12 in communication with a network management unit 34 as described in any of Examples C1 to C13.

[0556] Abbreviations

[0557] AC

[0558] AC / DC Alternating Current Direct Current

[0559] AS Auxiliary Services

[0560] BS Base Station

[0561] BSS Battery Storage System

[0562] BESS Battery Energy Storage System

[0563] CSP Communications Service Provider

[0564] DOD Depth of Discharge

[0565] DSO Distribution System Operator

[0566] ENM Ericsson Network Manager

[0567] EOL Battery End of Life

[0568] FCR-N Frequency Control Reserve-Normal

[0569] FCR-D Frequency Control Reserve-Interference

[0570] HZ Hertz

[0571] KV kilovolt

[0572] LP Linear Programming

[0573] MILP Mixed Integer Linear Optimization

[0574] MNO Mobile Network Operator

[0575] MW Megawatt

[0576] OSS Operation and Support System

[0577] PP Pricing Issues

[0578] PSU Power Supply Unit

[0579] QOS Quality of Service

[0580] RAN Radio Access Network

[0581] RBS Radio Base Station

[0582] SBA Service Infrastructure

[0583] SOC State of Charge

[0584] UPS Uninterruptible Power Supply

[0585] VAC Volts AC

[0586] TCO Total Cost of Ownership

[0587] TSO Transmission System Operator

[0588] WP White Paper

[0589] 4G Fourth Generation

[0590] 5G Fifth Generation

[0591] Note that although the term "bid hour" is used herein, any time period used in the bidding process (e.g., 30 minutes, 10 seconds, 3 weeks, etc.) is applicable to embodiments of the present disclosure. For example, a particular utility may solicit bids in 10 minute increments / periods rather than hourly increments / periods, and thus a "bid hour" in that instance would refer to one such 10 minute period.

[0592] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware embodiments generally referred to herein as "circuits" or "modules". Any process, step, action, and / or functionality described herein may be performed by a corresponding module and / or any process, step, action, and / or functionality described herein may be associated to a corresponding module, which may be implemented with software and / or firmware and / or hardware. In addition, the disclosure may take the form of a computer program product on a tangible computer-usable storage medium, the computer program product having a computer program code executable by a computer included in the medium. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0593] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be appreciated that each frame of the flowchart illustration and / or block diagram and the combination of frames in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by a processor of a computer or other programmable data processing device create components for implementing the functions / actions specified in a flowchart and / or block diagram frame or multiple flowcharts and / or block diagram frames.

[0594] These computer program instructions that can direct a computer or other programmable data processing device to operate in a specific manner may also be stored in a computer-readable memory or storage medium, so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction components that implement the functions / actions specified in a flowchart and / or block diagram or multiple flowcharts and / or block diagrams.

[0595] Computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions / actions specified in the flowchart and / or block diagram block or multiple flowcharts and / or block diagram blocks.

[0596] It is to be understood that the functions / actions annotated in the blocks may not occur in the order annotated in the operating instructions. For example, depending on the functionality / actions involved, two blocks shown in succession may actually be executed substantially simultaneously or the blocks may sometimes be executed in the reverse order. Although some of the figures in the figures include arrows on the communication paths to illustrate the primary direction of communication, it is to be understood that communication may occur in the direction opposite to the arrows depicted.

[0597] You can use Python, The computer program code for performing the operation of the concept described herein can be written in an object-oriented programming language such as C++ or C++. However, the computer program code for performing the disclosed operation can also be written in a conventional process programming language such as "C" programming language. The program code can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or executed completely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or (for example, using an Internet service provider through the Internet) can be made to be connected to an external computer.

[0598] Many different embodiments have been disclosed herein in conjunction with the above description and figures. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be overly repetitive and obscure. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the figures should be interpreted as constituting a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and this specification including the figures should support claims to any such combination or subcombination.

[0599] Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been particularly shown and described above. In addition, unless otherwise mentioned above, it should be noted that all figures in the accompanying drawings are not drawn to scale. Various modifications and variations are possible in accordance with the above teachings without departing from the scope and spirit of the invention, which is limited only by the following claims.

Claims

1. A management node (24) configured to communicate with a grid operator and with a plurality of radio base stations (RBS) (16), each of the plurality of RBS (16) being configured to be switchable between power from the grid and power from a respective plurality of backup battery units (59) associated with the RBS (16), the management node (24) being configured to: determining a primary subset of the plurality of RBSs (16) to participate in at least one frequency control reserve (FCR) event occurring during a predefined time interval; determining a spare subset of the plurality of RBSs (16) each configured to participate in the at least one FCR event in place of a failure of a corresponding one of the primary subset of the plurality of RBSs (16); causing transmission of a synchronization signal having operational settings associated with participation in the at least one FCR event to the primary subset and the backup subset of the plurality of RBSs (16); as well as During an activation period, transmission of an activation signal is caused to at least one of the primary subset of the plurality of RBSs (16), the activation signal being configured to cause the RBS (16) to modify its power consumption based on the synchronization signal to participate in the at least one FCR event.

2. The management node (24) according to claim 1, wherein: The determination of the primary subset and the backup subset of the plurality of RBSs (16) is based on an optimization model that maximizes availability to participate in at least one FCR event and an energy compensation event while minimizing: Penalty costs for failure to meet energy requirements for at least one FCR event; Battery degradation costs; physical extents of the primary and backup subsets of the plurality of RBSs (16); and The number of RBSs (16) in the primary subset and the backup subset of the plurality of RBSs (16).

3. The management node (24) according to claim 2, wherein: the optimization model iteratively generates a set of operating settings according to an iterative pricing problem model, the iterative pricing problem model being configured to calculate contributions of estimated battery degradation, FCR-up events and FCR-down events for a respective RBS (16) participating in the at least one FCR event at time t, wherein different FCR events of the RBS (16) are considered; and the FCR-down event corresponds to a reduction in power supplied from the grid to at least one of the primary subset of the plurality of RBSs (16); as well as The FCR-up event corresponds to an increase in power supplied by the grid to at least one of the primary subset of the plurality of RBSs (16).

4. The management node (24) according to claim 3, wherein: The iterative pricing problem model output is an RBS configuration among a plurality of RBS configurations, the RBS configuration having a minimum cost for participating in the at least one FCR event compared to the costs associated with the remaining RBS configurations, the minimum cost being based on: Availability to participate in at least one FCR event; Compensation for participation in at least one FCR event; Penalty costs for failure to meet energy requirements for at least one FCR event; Battery degradation costs; physical extents of said primary subset and backup subset of said plurality of RBSs (16); The number of RBSs (16) in the primary subset and the backup subset of the plurality of RBSs (16).

5. The management node (24) according to claim 2, wherein: The battery degradation cost is estimated based on: linearizing a battery degradation curve that maps a maximum battery cycle number to a depth of discharge of the battery; Divide the linearized battery degradation curve into segments; as well as A degradation rate for each segment of the linearized battery degradation curve is determined for each event in the battery degradation model.

6. The management node (24) according to any one of claims 1 to 5, wherein: the at least one FCR event corresponds to a plurality of FCR events occurring during the predefined time interval; a first portion of the primary subset of the plurality of RBSs (16) being scheduled to participate in a first FCR event of the plurality of FCR events; and A second portion of the primary subset of the plurality of RBSs (16) is scheduled to participate in a second FCR event of the plurality of FCR events, the first portion of the primary subset of the plurality of RBSs (16) being different from the second portion.

7. A radio base station (RBS) (16) in communication with a management node (24), the RBS (16) being configured to be switchable between power from a power grid and power from a plurality of backup battery units associated with the RBS (16), the radio station (16) comprising: A processing circuit (68), the processing circuit (68) being configured to: receiving synchronization signals associated with a primary subset and a backup subset of a plurality of RBSs (16) forming a cluster having operational settings associated with participation in at least one frequency control reserve (FCR) event; as well as receiving, during an activation period, an activation signal configured to cause the RBS (16) to modify its power consumption based on the synchronization signal in response to the activation signal; as well as The power consumption of the RBS (16) is modified based on the synchronization signal and the activation signal to participate in the at least one FCR event.

8. The RBS (16) according to claim 7, wherein: The RBS (16) is part of one of the primary subset and the backup subset of the plurality of RBSs (16).

9. The RBS (16) according to any one of claims 7 to 8, wherein: The activation signal indicates that the RBS (16) is to participate in an FCR-down event, the modification of the power consumption by the RBS (16) comprising reducing the power used by the RBS (16) from the grid.

10. The RBS (16) according to any one of claims 7 to 9, wherein: The activation signal indicates that the RBS (16) is to participate in an FCR-up event, and the modification of the power consumption by the RBS (16) includes increasing the power used by the RBS (16) from the grid by at least partially charging at least one of the plurality of backup battery units.

11. The RBS (16) according to any one of claims 7 to 10, wherein: The synchronization signal is received by the RBS (16) before an active time period, the processing circuit (68) being further configured to: The operation settings are performed during the activity time period, the operation settings comprising a profile control, the profile control indicating at least one of the following: synchronization of the RBS (16) in response to each request from the management node (24) to perform the operational setup; as well as local execution on at least one local controller; as well as At least one power modification process is performed based on at least one threshold indicated by the operational setting.

12. A method implemented by a management node (24), the management node (24) being configured to communicate with a grid operator and with a plurality of radio base stations (RBS) (16), each of the plurality of RBS (16) being configured to be switchable between power from the grid and power from a respective plurality of backup battery units (59) associated with the RBS (16), the method comprising: determining (block S145) a primary subset of the plurality of RBSs (16) to participate in at least one frequency control reserve FCR event occurring during a predefined time interval; determining (block S146) a backup subset of the plurality of RBSs (16) each configured to participate in the at least one FCR event in place of a failure of a corresponding one of the primary subset of the plurality of RBSs (16); causing (block S147) transmission of a synchronization signal having operational settings associated with participation in said at least one FCR event to said primary subset and backup subset of said plurality of RBSs (16); as well as During an activation period, transmission of an activation signal to at least one of the primary subset of the plurality of RBSs (16) is caused (block S148), the activation signal being configured to cause the RBS (16) to modify its power consumption based on the synchronization signal to participate in the at least one FCR event.

13. The method of claim 12, wherein: The determination of the primary subset and the backup subset of the plurality of RBSs (16) is based on an optimization model that maximizes availability to participate in at least one FCR event and an energy compensation event while minimizing: Penalty costs for failure to meet energy requirements for at least one FCR event; Battery degradation costs; physical extents of the primary and backup subsets of the plurality of RBSs (16); and The number of RBSs (16) in the primary subset and the backup subset of the plurality of RBSs (16).

14. The method of claim 13, wherein: the optimization model iteratively generates a set of operating settings according to an iterative pricing problem model, the iterative pricing problem model being configured to calculate contributions of estimated battery degradation, FCR-up events and FCR-down events for a respective RBS (16) participating in the at least one FCR event at time t, wherein different FCR events of the RBS (16) are considered; and the FCR-down event corresponds to a reduction in power supplied from the grid to at least one of the primary subset of the plurality of RBSs (16); as well as The FCR-up event corresponds to an increase in power supplied by the grid to at least one of the primary subset of the plurality of RBSs (16).

15. The method of claim 14, wherein: The iterative pricing problem model output is an RBS configuration among a plurality of RBS configurations, the RBS configuration having a minimum cost for participating in the at least one FCR event compared to the costs associated with the remaining RBS configurations, the minimum cost being based on: Availability to participate in at least one FCR event; Compensation for participation in at least one FCR event; Penalty costs for failure to meet energy requirements for at least one FCR event; Battery degradation costs; physical extents of said primary subset and backup subset of said plurality of RBSs (16); The number of RBSs (16) in the primary subset and the backup subset of the plurality of RBSs (16).

16. The method of claim 13, wherein: The battery degradation cost is estimated based on: linearizing a battery degradation curve that maps a maximum battery cycle number to a depth of discharge of the battery; Divide the linearized battery degradation curve into segments; as well as A degradation rate for each segment of the linearized battery degradation curve is determined for each event in the battery degradation model.

17. The method according to any one of claims 12 to 16, wherein: the at least one FCR event corresponds to a plurality of FCR events occurring during the predefined time interval; a first portion of the primary subset of the plurality of RBSs (16) being scheduled to participate in a first FCR event of the plurality of FCR events; and A second portion of the primary subset of the plurality of RBSs (16) is scheduled to participate in a second FCR event of the plurality of FCR events, the first portion of the primary subset of the plurality of RBSs (16) being different from the second portion.

18. A method implemented by a radio base station (RBS) (16) in communication with a management node (24), the RBS (16) being configured to be switchable between power from a power grid and power from a plurality of backup battery units associated with the RBS (16), the method comprising: receiving (block S140) synchronization signals associated with a primary subset and a backup subset of a plurality of RBSs (16) forming a cluster and having operational settings associated with participation in at least one frequency control reserve FCR event; During an activation period, receiving (block S141) an activation signal, the activation signal being configured to cause the RBS (16) to modify its power consumption based on the synchronization signal in response to the activation signal; as well as The power consumption of the RBS (16) is modified (block S142) based on the synchronization signal and the activation signal to participate in the at least one FCR event.

19. The method of claim 18, wherein: The RBS (16) is part of one of the primary subset and the backup subset of the plurality of RBSs (16).

20. The method according to any one of claims 18 to 19, wherein: The activation signal indicates that the RBS (16) is to participate in an FCR-down event, and the modification of the power consumption performed by the RBS (16) includes reducing the power used by the RBS (16) from the grid by at least partially charging at least one of the plurality of backup battery units.

21. The method according to any one of claims 18 to 20, wherein: The activation signal indicates that the RBS (16) is to participate in an FCR-up event, the modification of the power consumption by the RBS (16) comprising increasing the power used by the RBS (16) from the grid.

22. The method of any one of claims 18 to 21, wherein: Receiving the synchronization signal by the RBS (16) before an active time period; as well as The method further comprises: The operation settings are performed during the activity time period, the operation settings comprising a profile control, the profile control indicating at least one of the following: synchronization of the RBS (16) in response to each request from the management node (24) to perform the operational setup; and local execution on at least one local controller; and At least one power modification process is performed based on at least one threshold indicated by the operational setting.

Images