CN106717047B

CN106717047B - Ad-hoc network mechanism for saving energy during power outages

Info

Publication number: CN106717047B
Application number: CN201580051438.5A
Authority: CN
Inventors: 巴勃罗·塔皮亚
Original assignee: T Mobile USA Inc
Current assignee: T Mobile USA Inc
Priority date: 2014-09-25
Filing date: 2015-09-17
Publication date: 2020-07-03
Anticipated expiration: 2035-09-17
Also published as: WO2016048796A3; CN106717047A; EP3180936A2; WO2016048796A2; EP3180936A4

Abstract

A self-organizing network (SON) configured to receive information indicating that an access network device is experiencing a power outage is described herein. In response, the SON determines at least one of a time since the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator associated with the access network device. The SON then generates an updated configuration of the access network device based at least in part on at least one of a time since the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator. Further, the SON then provides the updated configuration to the access network device.

Description

Ad-hoc network mechanism for saving energy during power outages

RELATED APPLICATIONS

This patent application claims priority to U.S. utility patent application serial No. 14/496,185, filed on 9/25/2014, the entire contents of which are incorporated herein by reference in their entirety.

Background

Self-organizing networks (SON) are networks that are capable of any or all of automatic self-configuration, automatic self-optimization, or automatic self-healing. Recent developments in SON have focused on wireless access networks, but any kind of network can be developed as SON, such as smart grid systems or medical health systems. For wireless access networks, such as telecommunications networks, self-configuration may include the use of "plug and play" technology to automatically configure and integrate new base stations into the network. Self-optimization includes automatically adjusting base station parameters based on performance indicators. The self-healing may also involve automatically adjusting base station parameters. For example, neighboring base stations may be automatically reconfigured to support users of failed base stations.

Tools have been developed for wireless access networks implementing SON technology. Such tools may include performance management tools, Radio Frequency (RF) planning tools, automatic frequency planning tools, cutover (rehoming) tools, or automatic cell planning tools. Each of these tools is completely self-contained and processes everything from directly connecting with network components to retrieve measurement and configuration parameters, to intelligently analyzing and deciding about measurements and configurations, to presenting relevant information to a user. Because each tool is self-contained while performing many of the same tasks, there is a great deal of redundancy between tools, and the burden on tool developers is increased, thereby hindering the adoption of SON.

Drawings

The detailed description explains in detail with reference to the drawings. In the drawings, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears. The use of the same reference symbols in different drawings indicates similar or identical items or features.

Fig. 1 shows an overview of a SON having an Application Programming Interface (API) common to a plurality of SON tools, the SON tools receiving a performance indicator via the API and performing at least one action based on the performance indicator.

Fig. 2 illustrates an exemplary environment that includes multiple SON components for a telecommunications network that share a common API and that each perform some aspect of planning, configuring, managing, optimizing, or repairing the telecommunications network in an automated manner. The API enables additional SON components to be added or modified.

Fig. 3 illustrates another example environment that includes a SON device that can include one or more SON tools configured to receive information indicating that an access network device is experiencing a power outage, and to generate an updated configuration for the access network device based on at least one of a time after the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator associated with the access network device.

Fig. 4 illustrates a component-level view of a computing device configured to implement one or more SON components.

Fig. 5 illustrates an exemplary process for receiving, by a SON tool, a performance indicator through an API of a SON and performing at least one action based on the performance indicator.

Fig. 6 illustrates an exemplary process for receiving information indicating that an access network device is experiencing a power outage and generating an updated configuration for the access network device based on the power outage data or access network device data.

Detailed Description

The present disclosure describes, in part, an API for a SON that is common to at least a plurality of SON tools of a particular SON. The API enables each of a plurality of SON components to focus on a purpose (e.g., data integration, visualization, etc.) while communicating with each other to achieve overall SON planning. Thus, one component may collect network information and determine performance indicators, another component may receive updated network configurations and configure network components, and the SON tool may receive the performance indicators and use the API to provide the updated network configurations to the components or perform at least one action based on the performance indicators. The SON tool may also or alternatively be triggered by another SON component and perform actions, such as restoring the parameters to a particular value after a parameter consistency check, regardless of the performance indicator.

Additionally, the API can be extended by a new SON tool, and the SON can include a SON automation engine to receive, integrate, and execute the new SON tool. The SON automation engine can handle a series of tasks for SON tools, significantly reducing the amount of development required for a given SON tool. In some implementations, the SON automation engine can receive specifications of the SON tool from a developer through, for example, a SON portal.

The present disclosure also describes one or more SON tools configured to receive information indicating that an access network device is experiencing a power outage. The received information may be an alarm received by the SON tool indicating a power outage, or may be a performance indicator used by the SON tool to determine that a power outage occurred. In response, the SON tool determines at least one of a time since the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator associated with the access network device. Based on the determination, the SON tool then generates an updated configuration of the access network device and provides the updated configuration to the access network device. If the power outage continues for a period of time, the SON tool may periodically repeat the determining, generating the updated configuration, and providing the updated configuration, gradually applying changes to the configuration of the access network device that reduce the service capabilities of the access network device and conserve power of the access network device.

In some implementations, the SON tool receives the information and provides the updated configuration through an API of the SON (such as the API described in greater detail herein). The API can connect the SON tool with other SON components.

In various implementations, the access network devices may include base stations, node bs, and eNode bs, or access points whose primary power source has been lost or experienced a reduction in its power source resources below a threshold. Such access network devices may have a potential power source, a backup power source (such as a battery or battery pack), and a fuel generator. The access network device may expose or report performance indicators of the primary power source, battery level, fuel level, generator status, backup power source status, etc. to the SON. The access network device may also expose or report other performance metrics such as signal-to-noise ratio, bit error rate, frame error rate, number of carriers, number of connections, type of cellular technology of the connection, maximum transmit power, or maximum bit rate. In response to receiving the updated configuration from the SON, the access network device may turn off the air conditioner, turn off the primary power supply, adjust the voltage of the backup power supply, disconnect 2G, 3G, 4G/LTE or other cellular or wireless services, turn off one or more carriers, reduce the maximum transmit power, or adjust the maximum bit rate. As noted above, these changes may be applied gradually over time as the power outage continues.

SUMMARY

Fig. 1 shows an overview of a SON having an Application Programming Interface (API) common to a plurality of SON tools, the SON tools receiving a performance indicator via the API and performing at least one action based on the performance indicator. As shown, one or more computing devices 102 associated with the SON104 can be configured with a SON tool 106 that utilizes an API of a SON 108 that is common to multiple SON tools 106. The SON tool 106 receives, via the API108, a performance indicator 110 associated with the network information, the performance indicator 110 having been determined by the consolidation engine 112. The SON tool 106 performs at least one action based on the performance indicator 110, such as generating an updated network configuration based on the performance indicator 110 and providing the updated network configuration to the parameter configurator 114 via the API 108. The parameter configurator 114 then configures one or more network components 116 of the SON104 by, for example, updating parameters of the network components 116.

In various implementations, the computing devices 102 may each be or include a server or server farm, a plurality of distributed server farms, a host, a workstation, a Personal Computer (PC), a laptop computer, a tablet computer, an embedded system, or any other kind of device or devices. In one implementation, computing device 102 represents multiple computing devices operating in communication, such as a cloud computing network of nodes. The computing device 102 can belong to the SON104, or can be external to the SON104 but in communication with the SON 104. An exemplary computing device 102 is shown in fig. 3 and described in detail below with reference thereto.

The SON104 can be any kind of network that is configured by SON components to perform at least one of self-configuration, self-optimization, or self-repair. Such SON components are illustrated in fig. 1 by elements 106 and 114. For example, the SON104 may be a wireless access network, such as a telecommunications network, a smart grid, or a medical health network. The network component 116 of the SON104 can be a sub-network, device, or module that can be initialized or configured by the SON component 106 and 114. For example, when the SON104 is a telecommunications network, such as a 2G, 3G, 4G/LTE network or other cellular or wireless network, the network component 116 may be a base station (e.g., a Node B or eNodeB), a Radio Network Controller (RNC), an Operations Support System (OSS), a word order system, or other network element. Information regarding the SON104 (referred to herein as "network information"), such as measurements or parameters, may also be provided by the network component 116 or may be provided by other sources within the SON 104. For example, the network information may be returned by the fault billing system

(parent ticket system), wireless tracking, core network tracking, from the OSS or from one or more other network elements. Depending on the purpose of the SON104 (e.g., telecommunications, energy, medical health), the SON104 can include any number of different sub-networks, devices, and modules that are dedicated to the purpose of the SON104, and can communicate with any number of devices external to the SON 104.

In some implementations, the consolidation engine 112 may be a SON component whose purpose is to receive or retrieve network information and determine the performance indicators 110 based on the network information. The consolidation engine 112 may have ongoing, periodic, or event-driven connections to the network information sources of the SON104, and the consolidation engine 112 receives or retrieves the network information via those connections.

Upon receiving the network information, the consolidation engine 112 utilizes a repository (store) of performance indicators 110 (such as key performance indicators) associated with the API108 to determine new/updated performance indicators 110. The repository of performance indicators 110 may be any kind of database, file, or data structure. Further, the repository of performance indicators 110 may be associated with a mode (schema), and the mode may be extended with the API108 in response to the addition of a new SON tool 106. Based on the patterns, stored performance indicators 110, and received or retrieved network information, consolidation engine 112 determines new/updated performance indicators 110 and stores those new/updated performance indicators 110 in a repository of performance indicators 110. The new performance indicators 110 may be generated by the consolidation engine 112 in response to a request to generate the performance indicators 110, the performance indicators 110 being received by the consolidation engine 112 from the SON tool 106. In some implementations, this may involve filtering out redundant or non-utilized network information.

The consolidation engine 112 may then automatically provide the determined performance indicators 110 to the one or more SON tools 106 by calling the one or more SON tools 106 using the API 108. The called SON tool 106 may be a function of the performance indicators 110 that have been added or updated. In other implementations, rather than automatically invoking the SON tool 106, the SON tool 106 can query the consolidation engine 112 via the API108 for the performance metrics 110.

In various implementations, the API108 is an API for a SON that can be standardized and shared among multiple SONs. When normalized, the API108 may expose at least one of a normalization method/process or a normalization parameter, such as a performance indicator 110. In other implementations, the architecture utilizing the API108 can be standardized among multiple SONs, but the API108 can be SON104 specific, including methods/procedures specific to the SON tool 106 and parameters/performance metrics 110. For example, the SON tool 106 may have a method that calls the SON tool 106 to generate an updated network configuration, and the method may be associated with a particular performance indicator 110 to be provided when the method is called. Such methods may be part of the API 108. Likewise, the consolidation engine 112 may provide a query method for retrieving the performance indicators 110 with an identifier of the performance indicators 110 sought by the query as a parameter. Such query methods may also be part of the API 108. Additionally, the API108 can include methods for providing data to, receiving or retrieving data from, any of the SON components 106-114. In some implementations, the API108 can include methods for alarms or alerts that are utilized by the SON tool 106 to receive notifications (e.g., notifications that the performance indicator 110 exceeds a threshold). Further, while the API108 is shown as a separate SON component, it should be understood that the methods/processes associated with the API108 are those of the

other SON components

106 and 110 and 114, and that the API108 may simply be a logical representation rather than a separate module of code or hardware devices.

In some implementations, the SON tools 106 can each be responsible for performing certain tasks associated with self-configuration, self-optimization, or self-healing of the SON104, for example, in generating updated network configurations by the SON tool 106. SON tools 106 can also each call a SON component via API108 to perform an action based on performance indicator 110, call an engineering tool via API108 based on performance indicator 110, communicate information associated with performance indicator 110 to the SON component via API108, send a notification associated with performance indicator 110 via API108, or generate a report based on performance indicator 110.

The updated network configuration may simply be an update to a single parameter of a single network component 116 or may represent a more comprehensive configuration of multiple parameters of multiple network components 116. The SON tool 106 may be invoked by the consolidation engine 112 and receive the performance metrics 110, or may invoke a query method of the API108 associated with the consolidation engine 112 to receive or retrieve the performance metrics 110. The SON tool 106 can also be called by another SON tool 106 through the API108, and those SON tools 106 can cooperate.

Using the performance indicators 110, the SON tool 106 may generate an updated network configuration and call methods of the API108 associated with the parameter configurator 114 to provide the updated network configuration to the parameter configurator. For example, the SON tool 106 may be a cutover tool and may receive a performance indicator 110 informing the SON tool 106 that an RNC has been added for a geographic area. In response, the SON tool 106 can generate an updated network configuration that reallocates a plurality of base stations currently associated with one RNC to a new RNC.

Examples of the SON tools 106 may include any or all of an automatic report generation tool, a parameter consistency check tool, a real-time alarm tool, a mobility assessment tool, a coverage and interference management tool, a network outage tool, a network configuration tool, a load distribution tool, a spectral carving (spectrum carving) tool, or a special events tool. Additionally or alternatively, the SON tool 106 may include any or all of a performance management tool, a Radio Frequency (RF) planning tool, an automatic frequency planning tool, a cutover tool, an automatic cell planning tool, or a geographic positioning tool.

In some implementations, the SON tool 106 can perform the action regardless of the performance index 110. The SON tool 106 can be triggered by other SON components and can perform actions, such as resetting parameters, without receiving or retrieving the performance indicators 110.

In various implementations, the parameter configurator 114 may be invoked by the SON tool 106 and provided to the updated network configuration via the API 108. Alternatively, the parameter configurator 114 may invoke the SON tool 106 to retrieve an updated network configuration that is already ready or cause the SON tool 106 to generate and provide an updated network configuration. Upon retrieving or receiving the updated network configuration, the parameter configurator 114 configures the one or more network components 116 using the updated network configuration. As described above, this may involve adjusting one or more parameters or network components 116. Exemplary network components 116 are described in more detail above.

Exemplary Environment

Fig. 2 illustrates an exemplary environment that includes multiple SON components for a telecommunications network, the multiple SON components sharing a common API, and each SON component performing some aspect of planning, configuring, managing, optimizing, or repairing the telecommunications network in an automated manner. The API enables additional SON components to be added or modified. As shown, one or more computing devices 202 associated with the SON telecommunications network 204 can be configured with a SON tool 206, the SON tool 206 utilizing an API of a SON 208 that is common to a plurality of SON tools 206. The SON tool 206 receives, via the API 208, a performance indicator 210 associated with the network information, the performance indicator 210 having been determined by the consolidation engine 212. The SON automation engine 214 executes the SON tool 106 such that the SON tool 106 performs an action based on the performance indicator 210, such as generating an updated network configuration based on the performance indicator 210, and provides the updated network configuration to the parameter configurator 216 via the API 208. The parameter configurator 216 then configures one or more network components 216 of the SON telecommunications network 204 by, for example, updating parameters of the network components 218. Exemplary network components 218 may include a fail-back system 220, a wireless trace 222, a core network trace 224, an OSS226, a work order system 228, one or more other network elements 230, or an alarm system 240.

Additionally, the SON component shown in fig. 2 includes a visualization tool 232 for generating visualizations based on the performance indicators 210; a SON portal 234 for displaying visualizations to enable user collaboration on the SON telecommunications network 204 and to enable developer specifications of the SON tools 206, engineering tools 236, and reporting engine 238. The engineering tool 236 can be invoked by the SON tool 206 to participate in a self-configuring, self-optimizing, or self-repairing SON telecommunications network 204. The visualization tool 232, SON portal 234, and engineering tool 236 can communicate with each other and with other SON components via the API 208.

Computing device 202 may be similar to or the same as computing device 102. Similarly, the SON telecommunications network 204 can be similar to or the same as the SON104, except that the SON telecommunications network 204 is specifically identified as a telecommunications network. Network component 218 may be similar or identical to network component 116, except that a

particular network component

220 and 230 is shown and identified in fig. 2. Those network components 218-the fault receipt system 220, the wireless tracking 222, the core network tracking 224, the OSS226, the work order system 228, one or more other network elements 230, and the alarm system 240 are also mentioned above, with the network component 116 being an example of a network component 116 that may be associated with the SON104 when the SON104 is a telecommunications network. These network components 218 and other network information sources may provide network information to the consolidation engine 212 and receive updated network configurations from the parameter configurator 216.

In some implementations, the SON tool 206, the API 208, the performance index 210, the consolidation engine 212, and the parameter configurator 216 may be similar or identical to the SON tool 106, the API108, the performance index 110, the consolidation engine 112, and the parameter configurator 114, and the content written above with respect to these SON components 106 and 114 may also be applied to the

SON components

206 and 212 and 216, except for the distinctions depicted in FIG. 2.

In various implementations, visualization tool 232 may be called by consolidation engine 212 or may query consolidation engine 212 via API 208, and as a result of the call or query, visualization tool 232 may receive performance metrics 210. The visualization tool 232 may receive the performance indicators 210 periodically or on an event-driven basis as a result of, for example, the performance indicators satisfying a threshold or model specified by the rules of the visualization tool 232 or the consolidation engine. For example, the visualization tool 232 may have rules that specify that the visualization tool 232 will receive notifications when the performance metrics 210 exceed certain thresholds, and the consolidation engine 212 may disclose, via the API 208, the alarm or alert methods that the visualization tool 232 may use for registration. In this case, in response to registration of the visualization tool 232, the visualization tool 232 may be invoked to receive an alarm or alert when the performance metric 210 exceeds a threshold.

In some implementations, the visualization tool 232 generates visualizations based on the performance indicators 210, alarms, or alerts. These visualizations may convey information about the SON telecommunications network 204 in a graphical manner and may be displayed to a user. To provide the visualizations to the user, the visualization tool 232 may provide the visualizations to the SON portal 234, which may display the visualizations, or may provide them to another device for display, such as a server or end-user device. The SON portal 234 or device with which the visualization is shared may be a function of the visualization tool 232 configuration.

Moreover, in further implementations, the visualization tool 232 can invoke the SON automation engine 214 or a particular SON tool 206 executed by the SON automation engine 214 based on rules or user input. Such rules may instruct the visualization tool 232 to invoke the SON automation engine 214 or the SON tool 206 when the performance indicator 210 satisfies a threshold or model or when an alarm or alert is received. The user input received in response to providing the visualization may also cause the visualization tool 232 to invoke the SON automation engine 214 or the SON tool 206.

In various embodiments, the SON portal 234 may be a user-oriented component for displaying information, enabling user collaboration, and enabling specification by a user of the SON tool 206. The SON portal 234 may receive visualizations from the visualization tool 232 via the API and may provide those visualizations to the user device through, for example, a web page. The SON portal 234 may also receive other network information or performance indicators 210 via the API 208 from any SON component, such as the consolidation engine 212 or the visualization engine 232. In response, the SON portal 234 can also receive user input and can provide the user input to the SON tool 206 or visualization engine 232 for performing actions or further visualization.

The SON portal 234 may also include a collaboration engine or other social network component that enables users to communicate about the SON telecommunications network 204, including discussing issues of SON plans implemented by the SON telecommunications network 204 and suggestions for improving the plans. In some implementations, the SON portal 234 can even enable the user to vote for a plurality of suggested improvements of the SON plan, and the improvement having the highest plurality of votes can be implemented by a developer associated with the SON telecommunications network 204 that specifies the new SON tool 206.

In further implementations, the SON portal 234 enables specifications of the SON tool 206. The SON portal 234 can provide a user interface for text or graphic specification of the new SON tool 206. Such a user interface may simply accept text-specific code for the SON tool 206, or may even allow a user to select a graphical representation of a SON component (e.g., a graphical representation of the consolidation engine 212) to cause automatic specification of code for accessing the SON component through the API 208. Further, the SON portal 234 can automatically specify or update the SON tools 206 based on user comments. For example, the SON tool 206 may have a threshold at which the user equipment is reassigned to a different access network to avoid congestion. If there are sufficient complaints of congestion, the SON portal 234 can update the threshold to better avoid congestion.

In various implementations, the SON automation engine 214 can execute any one or more SON tools 206 in response to being called through the API 208 or in response to a SON tool 206 being called, receiving an alarm or alert, or the like. The SON automation engine 214 can handle a number of execution-related functions for the SON tool 206, such as memory allocation and release, calls to system components, and the like. Further, the SON automation engine 214 can receive specifications for the SON tools 206 from the SON portal 234, compile those specifications if compilation is required, and execute those SON tools 206.

The SON automation engine 214 may also provide an API 208 for the SON tools 206 such that the SON tools 206 utilize the API 208 of the SON automation engine 214 rather than extending the API 208 with their own methods/procedures. In such implementations, the API 208 may be relatively stable, with each of the consolidation engine 212, visualization tool 232, SON portal 234, engineering tool 236, reporting engine 238, parameter configurator 214, and SON automation engine 214 having their own methods/procedures and performance indicators/parameters. Such a relatively stable API 208 can significantly reduce the burden on the developer.

In further implementations, the engineering tool 236 can participate in a self-configuring, self-optimizing, or self-repairing SON telecommunications network 204 with the SON tool 206. The engineering tool 236 may even be a SON tool itself, operating independently and not necessarily executed by the SON automation engine 214. Like other SON components, the engineering tool 236 may receive or retrieve data through the API 208 and provide output to the API 208. Exemplary engineering tools 236 may include at least one of a performance management tool, an RF planning tool, an automatic frequency planning tool, a cutover tool, an automatic cell planning tool, or a geographic positioning tool. Each engineering tool 236 may provide output used by other engineering tools 236 or the SON tool 206.

The reporting engine 238 may participate in generating reports with the SON tool 206. The reporting engine 238 may even be the SON tool itself, operate independently and need not be executed by the SON automation engine 214. Like other SON components, the reporting engine 238 may receive or retrieve data through the API 208 and provide output to the API 208.

In some implementations, although the SON automation engine 214, visualization tool 232, SON portal 234, engineering tool 236, and reporting engine are illustrated in fig. 2 in connection with the SON telecommunications network 204, the SON automation engine 214, visualization tool 232, SON portal 234, engineering tool 236, and reporting engine 238 can also be associated with other types of SONs.

Exemplary Environment including SON mechanisms for energy conservation

FIG. 3 illustrates another example environment that includes a SON device that can include one or more SON tools. The SON device may be configured to receive information indicating that the access network device is experiencing a power outage and generate an updated configuration for the access network device. As shown, the one or more SON devices 302 can include one or more SON tools 304, a device characteristics/configuration data repository 306 (hereinafter "device data repository 306"), the API108, a data repository for performance indicators 110, the consolidation engine 112, and the parameter configurator 114. The SON tool 304 can receive SON alarms or performance indicators 110 associated with one or more access networks 308. The SON alarm or performance indicator 110 may indicate that the access network device 310 of the access network 308 is experiencing a power outage. For example, the power supply 312 or other resource 314 of the access network device 310 can exhibit a loss of power, and the loss can be retrieved or reported by the SON device 302 to the SON device 302.

In various implementations, the SON tools 304 can include one or more SON tools, such as one or more of the SON tools 106 or 206. The SON tool 304 can include a plurality of modules associated with different capabilities of the SON tool 304. For example, the SON tool 304 may include a module for receiving information indicating a power outage, a module for determining device and power outage data, such as time since the power outage, configuration, characteristics, performance indicators, and the like, a module for determining and generating an updated configuration for accessing network devices, and a module for providing the updated configuration. In some implementations, the SON tools 304 can interact with each other and other components of the SON device 302 through the API108, which is described in more detail above. In other implementations, the SON tool 304 and the SON device 302 may not utilize the API 108. Further, although not shown, the SON tool 304 can be executed by a SON automation engine (such as the SON automation engine 214).

The SON tool 304 executes on the SON device 302. The SON device 302 can be an example of the computing device 102, and as described above, the SON device 302 can include other SON tools 106, APIs for SON 108, performance metrics 110, an integration engine 112, and a parameter configurator 114. Alternatively, the SON device 302 may instead be an example of the computing device 202. In other implementations, the SON device 302 can instead be another one or more computing devices that can include the SON tools 304, the device data repository 306, and the performance metrics 110 without the API108, the consolidation engine 112, the parameter configurator 114, or other SON components.

In various implementations, the SON tool 304 can receive an alert from another component of the SON device 302 or from an OSS. Such a component or OSS may receive performance indicators or this information from an access network device 310 of the access network 308 by retrieving other information or by receiving reports generated by the access network device 310. Based on the received performance indicators or other information, the component or the OSS may generate an alert, and the SON tool 304 may receive the alert. The SON tool 304 can subscribe to such alerts, periodically poll the component or OSS for alerts (poll), or can otherwise cause such alerts to be sent to them by the component or OSS.

In alternative or additional implementations, the SON tool 304 may receive performance indicators, such as the performance indicators 110, through the API108 and the consolidation engine 112 or from the access network device 310 and any intermediate components. Examples of such performance indicators include a main power status, a battery level, a fuel level, a generator status, or a backup power status. The SON tool 304 may retrieve performance indicators or receive such performance indicators from the consolidation engine 112 or from the access network device 310. Upon retrieving or receiving the performance index, the SON tool 304 can determine the presence of a power outage at the access network device 310. The SON tool 304 may determine the presence of a power outage based on a comparison of the performance indicator to one or more thresholds or models.

Upon receiving the information indicating that a power outage occurred at the access network device 310, the SON tool 304 may determine device and power outage data. For example, the SON tool 304 may determine a time since the indication of receipt of the power down information. Alternatively, if the time at which the power outage occurred is received along with information indicating the power outage, the SON tool 304 may use the time. The SON tool 304 can then calculate an amount of time that has elapsed since the determined or received time. In some implementations, the SON tool 304 can run a timer that starts from the determined or received time.

In further implementations, determining the device data or the power outage data can include the SON tool 304 retrieving a current configuration of the access network device 310 experiencing the power outage or a characteristic of the access network device 310 experiencing the power outage. The current configuration may include thresholds or rules related to the number of carriers, the maximum bit rate, the available cellular technologies (e.g., 2G, 3G, 4G/Long Term Evolution (LTE) networks, or other cellular or wireless networks), and so on. The characteristic may be any backup power resource, supported cellular technology, etc. at the access network device 310. The SON tool 304 can retrieve the current configuration or characteristics from the access network device 310. Alternatively or additionally, the SON tool 304 may retrieve the current configuration or characteristics from the device data repository 306, which may be any kind of data repository, and may store one or both of the configurations and characteristics of the multiple instances of the access network device 310.

In some implementations, determining device or power down data can include the SON tool 304 receiving or retrieving a value of a performance indicator (also referred to herein as receiving or retrieving a performance indicator), such as the performance indicator 110. For example, the SON tool 304 may receive or retrieve the performance indicators 110 from the consolidation engine 112, which may be any of various KPIs. Additionally or alternatively, the SON tool 304 may retrieve the performance indicators from the access network device 310. As described above, examples of performance indicators may include a primary power status, a battery level, a fuel level, a generator status, or a backup power status. In some implementations, the performance indicators may have been previously received or retrieved as information indicative of a power outage.

In various implementations, the SON tool 304 may then determine one or more configuration changes to apply to the access network device 310 based on the determined device and power outage data, and may generate an updated configuration that reflects those configuration changes. Some examples of configuration changes that may be reflected in the updated configuration may cause access network device 310 to turn off air conditioning, turn off the primary power supply, adjust the voltage of the backup power supply, disconnect 2G, 3G, 4G/LTE or other cellular or wireless services, turn off one or more carriers, reduce the maximum transmit power, or adjust the maximum bit rate.

In some implementations, the SON tool 304 can determine the configuration change by applying one or more thresholds or models to the device and power outage data. The SON tool 304 can then select one or more configuration changes based on the association of those configuration changes with the threshold or model. For example, for a first pair of particular times since a power outage and a particular battery level, the SON tool 304 may determine a first configuration change, and for a second pair of another particular times since the power outage and another particular battery level, the SON tool 304 may determine a second configuration change. Such thresholds or models can be included in a policy of a telecommunication service provider associated with the SON device 302.

Additionally or alternatively, the SON tool 304 may determine the configuration change by selecting a configuration change template from a plurality of configuration change templates based at least in part on the determined device and the power outage data. Different thresholds may have different criteria, and the SON tool 304 may select the configuration change template having the criteria that best matches the device and outage data. For example, there may be templates specific to power outages lasting more than one day and battery levels below 50%.

Upon determining configuration changes, the SON tool 304 can generate updated configurations that reflect those configuration changes.

In various implementations, the SON tool 304 can then apply the updated configuration to the access network device 310. Further, in various implementations, the SON tool 304 may provide updated configurations through the parameter configurator 114 and may interact with the parameter configurator 114 through the API 108.

In some implementations, the SON tool 304 periodically determines whether the power down is still continuing. If the outage is still continuing, the SON tool 304 can again determine device and outage data, determine a configuration change based on the device and outage data, generate an updated configuration that reflects the configuration change, and provide the updated configuration. For each iteration, the SON tool 304 may disable or reduce more features of the access network device 310 to save additional power and extend the time the access network device 310 remains operational. In this manner, the SON tool 304 may gradually apply configuration changes over time, balancing service availability and service life.

After the power outage, in some implementations, the SON tool 304 can return the configuration of the access network device 310 to its state prior to the power outage. The configuration corresponding to the previous state may be obtained by the SON tool 304 from the device data store 306.

In various implementations, the access network 308 may be any kind of access network, such as a wireless access network utilizing licensed spectrum or a wireless network utilizing unlicensed spectrum. The access network 308 may be an access network of a telecommunications network, such as a macrocell, microcell, picocell, or femtocell. Each access network 308 may include an access network device 310, which access network device 310 may be a base station, a Node B, an eNode B, or a WiFi access point. Each access network 308 may also include additional devices such as Radio Network Controllers (RNCs) and the like.

The access network device 310 may include antennas and other communication devices that may be configured to provide a coverage area. For example, the access network device 310 may include a tower mounting an antenna and a communication device. Such antennas and communication devices may be examples of resources 314. Access network device 310 may also include a power source 312, such as a primary power source and a backup power source. The primary power source may be an a/C power source and the backup power source may include a battery or other backup power source. In some embodiments, power source 312 may also include a generator and a fuel source to recharge the backup power source. A U.S. patent No. 8,005,510 entitled Cell Site Power saving (Cell Site Power Conservation) granted on 10.7.2008; granted on day 10/2 of 2012, entitled "Battery Monitoring system, e.g., U.S. patent No. 8,279,074 For (Battery Monitoring system, Such As For Use In Monitoring Cell Site Power Systems)"; and an example of an access network device 310 with a power supply 312 is described in more detail in U.S. patent No. 8,729,732 entitled Cell site power Generation (Cell site power Generation), granted on day 5/20 2014.

In various implementations, the power source 312 and the resource 314 may expose or report performance metrics such as battery level, fuel level, generator status, backup power status, signal-to-noise ratio, bit error rate, frame error rate, number of carriers, number of connections, type of cellular technology connected, maximum transmit power, or maximum bit rate. These performance indicators can be periodically reported to the SON device 302 or can be retrieved by the SON device 302. In some implementations, access network device 310 may provide APIs to power supply 312 and resources 314 to enable querying the value of the performance metric.

In further implementations, the access network device 310 can receive updated configurations from the SON devices 302 and can apply configuration changes reflected by the updated configurations. The configuration change may, for example, cause access network device 310 to perform at least one of the following: turning off the air conditioner, turning off the main power supply, adjusting the voltage of the backup power supply, turning off 2G, 3G, 4G/LTE or other cellular or wireless services, turning off one or more carriers, reducing the maximum transmit power or adjusting the maximum bit rate.

Exemplary device

Fig. 4 illustrates a component-level view of a computing device configured to implement one or more SON components. As shown, the computing device 400 includes a system memory 402 that stores one or more SON components 404 and other modules and data 406. Further, computing device 400 includes processor 408, removable storage 410, non-removable storage 412, transceiver 414, output device 416, and input device 418.

In various implementations, the system memory 402 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The SON component 404 may be any one or more of the SON tools 106, APIs 108, performance indicator repository 110, consolidation engine 112, or parameter configurator 114 described in detail above with respect to fig. 1. The SON component 404 may also or alternatively be any one or more of the SON tool 206, API 208, performance indicator repository 210, consolidation engine 212, SON automation engine 214, parameter configurator 216, visualization tool 232, SON portal 234, or engineering tool 236 described in detail above with reference to fig. 2. Additionally, the SON component may also or alternatively be any one or more of the SON tools 304 or device characteristics/configurations 306 described in detail above with respect to fig. 3. Other modules or data 406 stored in system memory 402 may include any kind of application or platform component of computing device 400, as well as data associated with the application or platform component.

In some implementations, the processor 408 is a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or both a CPU and a GPU, or any other type of processing unit.

Non-transitory computer-readable media may include volatile and nonvolatile, removable and non-removable tangible physical media implemented in technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. System memory 402, removable storage 410, and non-removable storage 412 are all examples of non-transitory computer-readable media. Non-transitory computer-readable media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible physical medium which can be used to store the desired information and which can be accessed by computing device 400. Any such non-transitory computer readable media may be part of computing device 400.

In some implementations, the transceiver 414 includes any kind of transceiver known in the art. For example, the transceiver 414 may include a wireless transceiver that performs the function of transmitting and receiving radio frequency communications via an antenna. The transceiver 414 can facilitate wireless connectivity between the computing device 400 and the SON104, the SON telecommunications network 204, other SON devices 302, or different nodes of the access network 308. In addition, the transceiver 414 may also include a wireless communication transceiver and a near field antenna for communicating over unauthorized wireless IP networks such as local wireless data networks and personal area networks (e.g., bluetooth or Near Field Communication (NFC) networks). Further, the transceiver 414 can include a wired communication component, such as an ethernet port, that wiredly connects the computing device 400 to one or more nodes of the SON104, the SON telecommunications network 204, other SON devices 302, or the access network 308.

In some implementations, the output device 416 includes any kind of output device known in the art, such as a display (e.g., a liquid crystal display), a speaker, a vibrating mechanism, or a haptic feedback mechanism. The output device 416 also includes ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display.

In various implementations, the input device 418 includes any kind of input device known in the art. For example, input device 418 may include a camera, microphone, keyboard/keypad, or touch-sensitive display. The keyboard/keypad may be a push button numeric dial (such as on a typical telecommunications device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons or the like.

Exemplary procedure

Fig. 5 and 6 illustrate exemplary processes. The processes are illustrated as logical flow diagrams, each operation of which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the process.

Fig. 5 illustrates an exemplary process for receiving, by a SON tool, a performance indicator through an API for a SON and performing at least one action based on the performance indicator. In 502, the process includes invoking, by one or more of a visualization tool, another SON tool, an integration engine, or a SON portal, a SON tool. In other implementations, rather than being invoked, the SON tools may be executed continuously or periodically.

In 504, the SON tool receives one or more performance indicators associated with the network information, the performance indicators received via an API of a SON utilized by the plurality of SON tools. The network information and the one or more network components are associated with one of a telecommunications network, a smart grid, or a medical health system. In some implementations, the API provides one or more alarms and alerts that may be received or invoked by the SON tool.

At 506, the SON tool performs at least one action based at least in part on the one or more performance indicators, the at least one action being one of: in 506a, an updated network configuration is generated, in 506b, the SON component is called via the API to perform the action, in 506c, the engineering tool is called via the API to perform the action, in 506d, information is passed to the SON component via the API, in 506e, a notification is sent via the API, or in 506f, a report is generated.

In 508, the SON tool provides the updated network configuration via the API to configure the one or more network components. In some implementations, the updated network configuration includes an update to at least one of the one or more performance indicators.

Fig. 6 illustrates an exemplary process for receiving information indicating that an access network device is experiencing a power outage and generating an updated configuration for the access network device based on the power outage or access network device data. At 602, the example process includes receiving, by one or more SON tools of a SON, information indicating that an access network device is experiencing a power outage. The power outage may be a loss of main power to the access network device or a decrease in power to an available power source of the access network device below a threshold. In 604, the receiving may include receiving, by one or more SON tools, an alert indicating a power outage. Alternatively or additionally, in 606, the receiving may include receiving, by the one or more SON tools, a performance indicator indicative of the outage, and determining, by the one or more SON tools, the existence of the outage based on the received performance indicator.

In 608, the one or more SON tools may determine at least one of a time since the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator associated with the access network device in response to receiving the information. The characteristic may include a backup power source, a supported cellular technology, or a size of a cell served by the access network device. The performance indicator may be one of a battery level, a fuel level, a generator status, a backup power status, a signal to noise ratio, a bit error rate, a frame error rate, a number of carriers, a number of connections, a type of cellular technology connected, a maximum transmit power, or a maximum bit rate. In 610, the determining may include retrieving, by one or more SON tools, a value of a performance indicator from an access network device.

In 612, the one or more SON tools may generate an updated configuration of the access network device based at least in part on at least one of a time since the power outage, a current configuration of the access network device, a characteristic of the access network device, or a value of a performance indicator. The updated configuration may cause the access network device to perform at least one of turn off air conditioning, turn off main power, regulate voltage of backup power, turn off 2G, 3G, 4G/LTE or other cellular or wireless services, turn off one or more carriers, reduce maximum transmit power, or regulate maximum bit rate.

In 614, the one or more SON tools may provide the updated configuration to the access network device.

In some implementations, one or more SON tools can periodically repeat the determinations at 608, the generations at 612, and the provisions at 614 while gradually applying changes to the configuration of the access network device, which reduces the service capabilities and saves power of the access network device. Such repetition may occur after a threshold amount of time has elapsed since the last provision in 614 if the power outage is still continuing.

Further, in various implementations, one or more SON tools can receive information and provide updated configurations through an API of a SON connecting the one or more SON tools and other SON components.

Conclusion

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. A computer-implemented method, comprising:

receiving, by the self-organizing network (SON), information indicating that the access network device is experiencing a power outage while continuing to operate at least one of reduced power or backup power;

determining, by the SON, in response to receiving the information, at least one of a time since the power outage, a backup power resource of the access network device, a cellular technology supported by the access network device, a size of a cell served by the access network device, or a value of at least one performance indicator associated with the access network device, wherein the at least one performance indicator includes at least one of a battery level, a fuel level, a generator status, a backup power status;

generating, by the SON, an updated configuration of the access network device based at least in part on the determined time since the power outage, a backup power resource of the access network device, cellular technologies supported by the access network device, a size of a cell served by the access network device, or a value of the at least one performance indicator, wherein the updated configuration reduces a power requirement of the access network device during the power outage; and

providing, by the SON, the updated configuration to the access network device.

2. The computer-implemented method of claim 1, wherein receiving the information comprises receiving, by a SON tool of the SON, an alert indicating the power outage.

3. The computer-implemented method of claim 1, wherein receiving the information comprises receiving, by a SON tool of the SON, the performance indicator, and determining the existence of the outage based on the received performance indicator.

4. The computer-implemented method of claim 1, wherein the power outage is a loss of a primary power resource of the access network device or a reduction in power of an available power source of the access network device that decreases below a threshold.

5. The computer-implemented method of claim 1, wherein when the determining comprises determining a value of at least one performance metric associated with the access network device, the determining comprises retrieving the value of the at least one performance metric from the access network device.

6. The computer-implemented method of claim 1, wherein the at least one performance indicator further comprises one of: signal to noise ratio, bit error rate, frame error rate, number of carriers, number of connections, type of cellular technology connected, maximum transmission power or maximum bit rate.

7. The computer-implemented method of claim 1, wherein the updated configuration causes the access network device to perform at least one of: turning off the air conditioner, turning off the main power supply, adjusting the voltage of the standby power supply, disconnecting the second generation 2G, third generation 3G, fourth generation 4G, long term evolution LTE or other cellular or wireless services, turning off one or more carriers, reducing the maximum transmission power or adjusting the maximum bit rate.

8. The computer-implemented method of claim 1, further comprising periodically repeating the determining, the generating, and the providing while gradually applying changes to the configuration of the access network device that reduce service capabilities and conserve power of the access network device.

9. The computer-implemented method of claim 1, wherein the receiving, the determining, the generating, and the providing are performed by one or more SON tools of the SON.

10. The computer-implemented method of claim 9, wherein the one or more SON tools receive the information and provide the updated configuration through an Application Programming Interface (API) of the SON that connects the one or more SON tools and other SON components.

11. A non-transitory computer-readable medium having stored thereon programming instructions configured to program one or more computing devices of a self-organizing network (SON) to perform operations comprising:

receiving information indicating that the access network device is experiencing a power outage while continuing to operate at least one of reduced power or backup power;

in response to receiving the information, determining at least one of a time since the power outage, a backup power resource of the access network device, a cellular technology supported by the access network device, a size of a cell served by the access network device, or a value of at least one performance indicator associated with the access network device, wherein the at least one performance indicator includes at least one of a battery level, a fuel level, a generator status, a backup power status;

generating an updated configuration of the access network device based at least in part on at least one of the determined time since the power outage, a backup power resource of the access network device, cellular technologies supported by the access network device, a size of a cell served by the access network device, or a value of the at least one performance indicator, wherein the updated configuration reduces a power requirement of the access network device during the power outage; and

providing the updated configuration to the access network device.

12. The non-transitory computer-readable medium of claim 11, wherein receiving the information comprises:

receiving, by a SON tool of the SON, an alarm indicating the power outage, or

Receiving, by a SON tool of the SON, the performance indicator, and determining the existence of the outage based on the received performance indicator.

13. The non-transitory computer readable medium of claim 11, wherein the at least one performance indicator further comprises one of: signal to noise ratio, bit error rate, frame error rate, number of carriers, number of connections, type of cellular technology connected, maximum transmission power or maximum bit rate.

14. The non-transitory computer-readable medium of claim 11, wherein the updated configuration causes the access network device to perform at least one of: turning off the air conditioner, turning off the main power supply, adjusting the voltage of the standby power supply, disconnecting the second generation 2G, third generation 3G, fourth generation 4G, long term evolution LTE or other cellular or wireless services, turning off one or more carriers, reducing the maximum transmission power or adjusting the maximum bit rate.

15. The non-transitory computer-readable medium of claim 11, wherein the operations further comprise periodically repeating the determining, the generating, and the providing while gradually applying changes to the configuration of the access network device, the changes reducing service capabilities and saving power of the access network device.

16. A self-organizing network, SON, comprising:

one or more processors; and

one or more SON tools configured to be operated by the one or more processors to perform operations comprising:

in response to receiving the information, determining at least one of a time since the power outage, a backup power resource of the access network device, a cellular technology supported by the access network device, a size of a cell served by the access network device, or a value of at least one performance indicator associated with the access network device, wherein the at least one performance indicator includes at least one of a battery level, a fuel level, a generator status, a backup power status; and

generating an updated configuration of the access network device based at least in part on at least one of the determined time since the power outage, a backup power resource of the access network device, cellular technologies supported by the access network device, a size of a cell served by the access network device, or a value of the at least one performance indicator, wherein the updated configuration reduces a power requirement of the access network device during the power outage;

providing the updated configuration to the access network device; and

periodically repeating said determining, said generating and said providing while gradually applying changes to the configuration of the access network device, said changes reducing the service capabilities of the access network device and saving power of the access network device.

17. The SON of claim 16, wherein receiving the information comprises:

receiving, by a SON tool of the SON, an alarm indicating the power outage, or

18. The SON of claim 16, wherein the at least one performance indicator further comprises one of: signal to noise ratio, bit error rate, frame error rate, number of carriers, number of connections, type of cellular technology connected, maximum transmission power or maximum bit rate.

19. The SON of claim 16, wherein the updated configuration causes the access network device to perform at least one of: turning off the air conditioner, turning off the main power supply, adjusting the voltage of the standby power supply, disconnecting the second generation 2G, third generation 3G, fourth generation 4G, long term evolution LTE or other cellular or wireless services, turning off one or more carriers, reducing the maximum transmission power or adjusting the maximum bit rate.