The present invention relates to antenna control systems, and more particularly to a network management system to monitor and control a network of base station antennas and related equipment at cell sites.
Cellular networks utilize network parameters to control communications throughout the network. Such parameters are to typically optimized based on dynamic communications and network conditions, such as traffic load and balancing conditions and/or changing interference conditions. Typically, network parameters are fixed at the time the network is deployed. The network parameters selected are adjusted to achieve an acceptable compromise between conditions from all the varying traffic conditions that may be experienced in the network. As such, the selected parameters involve trade offs in performance and are not optimized for each geographic area or every given time of day or traffic load condition that may exist. This approach yields a static type of network plan and network optimization which does not take into account varying traffic conditions and varying interference conditions that the network will be subject to on a daily or hourly basis.
Cellular networks are subject to highly time variable traffic loads. The performance of code division multiple access networks, where users share the same frequency, is very sensitive to traffic density as a function of geographic location as well as the amount of interference that is present in the network. Accordingly, system operators typically notice increases in the drop call rate in specific locations or network performance problems in specific locations, as the traffic flow changes based on time of day, day of week, or specific traffic hot spots associated with, for example, sporting events or traffic jams. Therefore, the localized traffic handling ability of the network should be changed based on how the users are distributed.
Therefore, a need exists for a network management system for controlling antenna operating parameters such as, for example, beam elevation, azimuth beam width, elevation beam width, and azimuth beam pointing which can be controlled in real time or on a dynamic basis as traffic patterns or interference patterns change. There exists a need for a system and method for dynamically adjusting network antenna operating parameters as well as for adjusting network parameters for a particular portion of a network based on localized conditions.
In accordance with one aspect of the present invention, a network management system for controlling a network of antennas including multiple antennas located at multiple sites is provided. The system includes a controller remotely located from the network of antennas for generating an internet protocol address and establishing an internet protocol connection to a data network in communication with the network of antennas. The controller provides control signals for controlling antenna operating parameters for each of the antennas at each of the multiple sites. The system further includes a user interface coupled to the controller for selecting ones of the antennas and establishing selected antenna operating parameters based upon the creation of a group of antennas and a created schedule.
For a more complete understanding of the present invention and for further advantages thereof, reference is now made to the following Description of the Preferred Embodiments taken in conjunction with the accompanying Drawings in which:
Referring to
System 10 may be implemented as illustrated in
As will subsequently be described, client process 20 includes a graphical user interface (GUI) to allow multiple users to view multi-level map displays 24 for displaying local, regional, and countrywide network display and management of sites 12. Instantaneous and continuous feedback of network status is displayed on display 24. Additionally, the GUI includes a display 26 for displaying individual site 12 status, control and antenna 14 configurations. Group create display 28 allows the user to create and manipulate groups of antennas within a site 12 or multiple sites 12 for schedule processes and movement of numerous antennas 14 simultaneously.
Process create 30 is a user interface display to allow for the automated monitoring and positioning of groups of antennas for radiation pattern control by selecting elevation beam tilt, azimuth beam width, azimuth beam pointing, elevation beam width, azimuth beam shape and elevation beam shape. As used herein, these processes shall be collectively referred to as “antenna operating parameters”. Antenna operating parameters also include error conditions for access and movement, antenna power (input and reflected) and other parameters, such as, for example temperature. Schedule create display 32 allows a user to create and manipulate schedules which consists of processes and the time of day to execute a specific process created using display 30. A schedule consists of processes and the time of day to execute a specific process as well as the periodic nature of the process, such as a specific day of the week, or a one-time only configuration of a site 12 or multiple sites 12. Client process 20 accesses a configuration file 34 containing a database of predefined antenna operating parameter configurations for sites 12. Client process 20 also acts with a database 36 which includes data relating to specific sites 12.
Server process 22 provides for an interface between client processes 20 and data network 16 and includes a server dialog 40. Server dialog 40 represents software within server process 22. Dialog server 40 communicates with database 36 via a database thread 42 representing a series of computing instructions that comprise software within server process 22. Server dialog 40 also interfaces to a configuration file 44, customer database 46 and optimization input/output database 48. Configuration file 44 includes a database representing site 12 configurations. Customer database 46
Communication between client process 20 and server process 22 is established using a protocol over IP socket 52 which provides an input to server process 22 via a port or client socket 54. Server process 22 communicates with multiple clients 20 at any given time. At start up, server process 22 will issue an IP socket listen command. After successful operator login, client process 20 will direct a connect command to server process 22. Server process 22 will then perform an accept command, and add the client socket 54 to its list of logged-in client processes 20. Thus, a socket connection will be in place via local area network 23.
Communication across IP socket 52 will be performed, for example, using a private class-oriented protocol. The originator's computer name, message type and data will be passed with each message between client process 20 and server process 22. On receipt, the socket message is time-stamped. When a socket or port is closed from one side of local area network 23, the application on the other side will receive a “socket closed” notification, at which time the socket interface will be closed. When a client process 20 socket closes, server process 22 will remove that client from its list of logged-in clients. Client process 22 will no longer send messages to that client, nor will process 22 accept communication that indicates that it is from that client. When a client process 20 receives notification that the server socket has closed, client process 20 will provide feedback to the user. The status window of client process 20 will no longer accurately reflect network status, and no further configurations will be allowed.
Server process 22 functions as an interface and controller between sites 12 and users 20. Server process 22 controls activities at sites 12 including the control of antenna operating parameters as well as the control and monitoring of parameters associated with RF path devices such as, for example, low noise and power amplifiers, and site equipment 58 located at each site 12. Amplifier parameters include, such as, for example, gain, temperature and output power. Site equipment 58 may include, for example, power supplies, security devices, monitors, air conditioners, radios, weather instrumentation GSM devices, TI-interfaces, microwave backhaul systems, repeaters and pico cells. Server process 22 also is the access point through which users 20 travel in order to write to database 36 and access and edit configuration file 44.
For each instance of a point of communication between server process 22 of system 10 and a site 12 there is a dedicated thread 62 connected to dialog 40 to establish communication to and from a site 12. A site communication thread 62 exists for each site 12. A communication link in the form of an IP socket 64 is established to data network 16 from each thread 62. Server process 22, upon start up, will create a dedicated thread 62 with an IP socket 64 for each defined site 12.
Each site 12 includes a modem 70 which establishes a communication link via an IP socket 72 with data network 16. Modem 70 communicates serially or via an IP connection 90 to antennas 14 and site equipment 58 as well as a local controller 74. Connection 90 may include, for example, RS 232, RS 485, RS 422 or Ethernet connections which connection is device controlled and protocol independent. Once a site modem 70 has connected via data network 16 to server process 22, the server application authenticates the modem 70 to determine which site 12 has been connected. This process allows for simultaneous control and status of numerous sites 12.
Server process 22 has the capability to initiate communication between modem 70 at each site 12 and the server application. This process involves the service application utilizing a dial-up analog telephone line within data network 16 to call a modem 70. Anytime a modem 70 at any of the control sites 12 receives a telephone call, modem 70 will disconnect the analog telephone line and initiate the IP connection to server process 22. This process to force a connection to any particular site 12 can be generated by a user, or automatically done when server process 22 determines communication is necessary to a particular site 12.
Once a communication thread 62 has been created, and an IP socket connection 64 exists between server process 22 and a particular site 12 modem 70, the server application will begin to status and control all of the antennas 14 associated with that site 12, as well as other site equipment 58. All commands, designated for a specific antenna 14 or site equipment 58 are buffered for each individual site 12. After the site 12 has connected, the server process application will automatically status each antenna 14, and execute any commands that have been qued for each antenna 14. These commands include any antenna 14 position changes requested by the user or commands automatically entered from a scheduled process stored in schedule time process 78 and scheduled execution process 80. Server process 22 communicates with each antenna 14, and any other serial device at a site 12 through IP socket 64 initiated by modem 70. All alarms and status information are logged by server process 22 at threads 82 and 84, respectively. Server process 22 continuously tracks each and every IP socket 64 connection to determine which sites 12 have active connections. Any commands or requests of statistical information designated for a site 12 will automatically be processed if that site 12 has an active connection. If the designated site 12 is not active, the commands and/or requests will be buffered and await an active connection, at which time they will be automatically processed. When necessary, server process 22 will automatically dial-up a site 12 modem 70 to initiate the connection.
Server process 22 maintains a record of current and last time of communication with each site 12. This information is utilized to alarm sites 12 that have not initiated communication with server process 22 within a set period of time.
Schedule time process 78 maintains the date and time the next scheduled process is to be executed. Any changes to the databases 36, 46 and 48 will force server process 22 to reset the date and time of the next scheduled process. Server process 22 will interrupt at the date and time associated with the next scheduled process. This interrupt will force the server application to execute the specific process at schedule execute process 80. This process includes a group of antennas and the desired antenna positioning for each antenna which the user created at client process 20 via displays 28, 30 and 32. Server process 22 determines which sites have active connections, and begins positioning antennas 14 at the requested site 12. Those sites which do not have active connections, will have their new positions buffered and wait for their next connection. When necessary, as previously stated, server process 22 will initiate the connection through a dial-up analog line via data network 16 forcing the site 12 modem 70 to initiate an IP socket 72 connection.
Server process 22 allows for real-time network optimization. When placed in this mode, server process 22 will save all pertinent site 12 and antenna 14 information in a comma-delimited file. Optimization input/output database 48 determines the optimal position for an antenna based upon previously calculated network conditions. Server process 22 will in turn read a comma-delimited file, as prepared by optimization input/output database 48 detailing the optimal antenna positions. Server process 22 is configured to automatically implement the changes dictated by this optimization process or to implement the changes after a user confirmation. After positioning the antennas 14 to new angles, the user will have the capability to reset the network to a default configuration, or return to previous antenna 14 positions.
Network 10 will generate alarms as system events occur that require reporting via alarm process thread 84. Possible alarms are databased and configured with a security level. Generated alarms are sent to the system log and to all logged-in users. If the alarm is configured with a major or minor severity, the alarm will be added to the current alarm's database table as well. Alarm processing includes the following steps: (a) a system event occurs that requires an alarm to be generated; (b) the alarm is created and passed to the alarm type identification code, its source, the current time, and overriding alarm text; (c) a look up is performed into the alarm definition table to obtain the severity level of the alarm code and its default text; (d) the alarm is formatted and added to the system log; (e) the alarm is forwarded to all logged-in users; and (f) if the severity justifies, the alarm is added to the current alarm table.
A clear alarm is created through the following process: (a) an error situation clears that had caused an alarm to be generated; (b) a clear alarm is created and passed the original alarm type ID code, its source, the current time, and overriding alarm text if necessary; (c) a look up is performed in the alarm definition table to obtain the security level of the alarm code and its default text; (d) the clear alarm is formatted and added to the system log; (e) the clear alarm is forwarded to all logged-in users; and (f) if the severity of the original alarm justifies, the original alarm is removed from the current alarm table. The user at client process 20 can view current alarms and manually clear alarms. A window in site display 26 will display alarms. Severity levels or alarm definitions will be modified by changing database 36.
Event log thread 82 is a time-stamped history of alarms and events that have taken place within system 10. Each entry will include a date and time, the source of the event, and a description of the event. The types of events that will be logged include values, outside bounds and operator actions. The system log is archived on a periodic basis and when the log reaches a file size limit. Archived logs may be viewed. Both current and archived logs may be searched, filtered and printed. Event log thread 82 maintains a comma-delimited text file. At user initiation, when a system log is open, the log is initialized from this file. Thereafter, it is updated in real time as system log messages are received from server process 22.
Client process 20 provides the user with a graphical user interface for network 10.
In addition to the connection status, site display 26 includes a table with antenna information. This information include antenna type, last time of communication, current position, and any outstanding positioning requests. If any antenna is in alarm condition, this information will also be displayed on site display 26. The user may select a specific antenna 14 within a site 12 or a specific sector of sites 12 for position movement. Once an antenna 14, or sector, has been commanded to a new position, the requested position will be displayed until the antenna 14 has been moved to that position, at which time the requested position field is cleared, and the current position field is updated to the new position.
System 10 allows for the creation of a group of antennas 14 for controlling numerous antennas automatically.
System 10 allows for a user to schedule a group process using process create display 30 as shown in
Once the group has been created by display 28 and the process created by display 30, a schedule may be created via display 32 as illustrated in
Antenna parameter control for antennas 14 is performed utilizing an antenna control system such as described in U.S. Pat. No. 6,198,458 entitled “Antenna Control System” which description and drawings are hereby incorporated by reference. Such an antenna control system enables the control of antenna beam tilt and other antenna operating parameters as described herein.
Referring now to
Other alteration and modification of the invention will likewise become apparent to those of ordinary skill in the art upon reading the present disclosure, and it is intended that the scope of the invention disclosed herein be limited only by the broadest interpretation of the appended claims to which the inventor is legally entitled.
This application claims the benefit of U.S. Provisional Application Ser. No. 60/507,102, filed Oct. 1, 2003 and entitled “Antenna Network Management System”.
Number | Date | Country | |
---|---|---|---|
60507102 | Oct 2003 | US |