System and method for managing base stations in a wireless system

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to the following applications:

U.S. application Ser. No. 09/128,553, filed on Aug. 3, 1998, by Lynn McKernan and entitled “A ‘Plug and Play’ Wireless Architecture Supporting Packet Data and IP Voice/Multimedia Services,” now abandoned;

U.S. application Ser. No. 09/219,539 filed on Dec. 23, 1998, by Lynn McKeman and entitled “Wireless Local Loop System Supporting Voice/IP,” now abandoned; and

U.S. application Ser. No. 09/675,796, filed on Sep. 29, 2000, by Stuart P. Kaler and entitled “System and Method for Managing Terminal Units in a Wireless System,” now U.S. Statutory Invention Registration No. H2059.

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to the field of communications, and more specifically to a system and method for managing base stations in a wireless system.

BACKGROUND OF THE INVENTION

Wireless networks typically allow terminal units to transmit and receive information over a wireless interface. Conventional terminal units include wireless telephones and computing devices connected to wireless modems. Base stations communicate with the terminal units over the wireless interface. The base stations establish, maintain, and release communications channels over the wireless interface, and the terminal units communicate with the base stations through the communications channels.

Typical wireless networks include an operations and maintenance center that manages the operations of the base stations. The operations and maintenance center usually manages the base stations by issuing management messages to one or more of the base stations. The base stations may also send responses and messages to the operations and maintenance center. In typical wireless networks, the management messages sent between the base stations and the operations and maintenance center travel through several intermediate network nodes, such as a base station controller.

Conventional wireless networks use a cascaded management scheme to manage the base stations. One or more intermediate nodes between the operations and maintenance center and the base stations perform mediation functions, translating the management messages from one format to another format that is understood by the intermediate node. For example, in conventional wireless networks, the base station controller receives management messages from the operations and maintenance center, translates the messages, and forwards the translated messages to the base stations.

A problem with this approach is that it increases the complexity of the wireless network. Components in the network typically need to include mediation functionality in order to communicate with other elements in the wireless network. The mediation functionality allows the network components to receive a management message, convert the message into a different protocol, and route the translated message to another element in the network. The mediation functionality makes the network elements more complex, which increases the development time and the expense of each element. This also increases the complexity and expense of the network.

Another problem with this approach is that it increases the load on the network components. The network components typically must receive and process the management messages, converting the messages from one format to another. The network components are unable to process other messages at this time. When a large number of management messages are being sent in the wireless network, elements in the network may spend an excessive amount of time translating the management messages, rather than performing other tasks in the network.

In addition, modularity typically cannot be maintained in the wireless network. The network components usually include proprietary management interfaces, which may prevent some of those components from properly communicating with one another. To properly transport management messages in the network, the components installed in the network need to understand the proprietary interfaces used by other components in the network. If a component cannot understand a proprietary interface in another component, the components may be unable to communicate effectively, and the network may be unable to transport management messages between the components. Because of the proprietary interfaces, a network operator is typically limited in the types of equipment that can be purchased and installed in the network.

SUMMARY OF THE INVENTION

In accordance with the present invention, a system and method for managing base stations in a wireless system are provided that substantially reduce or eliminate disadvantages and problems associated with previously developed systems and methods.

In one embodiment of the present invention, a communications system includes a base station operable to communicate with a terminal unit over a wireless interface, and a packet network coupled to the base station and operable to communicate with the base station. The communications system also includes a network management system coupled to the packet network. The network management system is operable to generate a management message to manage the base station. The network management system is also operable to transparently communicate the management message to the base station and to transparently receive a response to the management message from the base station.

In another embodiment of the present invention, a method for managing base stations in a wireless system includes generating a management message for the base station. The method also includes transparently communicating the management message from a network management system to the base station. The method further includes transparently receiving a response to the management message at the network management system from the base station.

Embodiments of the invention provide numerous technical advantages. For example, in one embodiment of the invention, a communications system is provided that uses less complex elements. In a particular embodiment, the system provides protocol layers for direct communications between a network management system and the base stations. The protocol layers allow management messages to be transported between the network management system and the base stations transparently. The network management system may manage the base stations in the system without other intermediate network components, such as base station controllers, performing mediation functions. The components in the system do not require mediation functionality, which reduces the complexity and expense of the components in the system. This also helps reduce the complexity and expense of the communications system.

Some embodiments of the invention also decrease the load on the components in the system. The network management system and the base stations may communicate transparently across the intermediate system components. These system components are not required to perform any mediation functions, so the components are able to perform other tasks. When a large number of management messages are being sent in the wireless network, the system components are not spending excessive amounts of time translating the management messages.

In addition, some embodiments of the invention help maintain modularity in the network. The components in the system may not need to understand proprietary management interfaces to function properly. By providing protocol layers for communications between the network management system and the base stations, the management messages may be communicated transparently between those elements, even if proprietary interfaces are used in the network components. Other equipment in the network, like base station controllers, may be installed without determining whether they can perform mediation functions for the management messages. The base stations controllers may properly transport the management messages in the network without understanding the proprietary management interfaces used in other elements in the network.

Other technical advantages are readily apparent to one of skill in the art from the attached Figures, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and for further features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating an exemplary communications system;

FIG. 2 is a block diagram illustrating an exemplary network management architecture for the communications system of FIG. 1;

FIG. 3 is a block diagram illustrating an exemplary management protocol architecture for managing base stations in the communications system of FIG. 1;

FIG. 4 is a block diagram illustrating an exemplary management protocol architecture for managing terminal units in the communications system of FIG. 1;

FIG. 5 is a flow diagram illustrating an exemplary method for managing base stations at a network management system;

FIG. 6 is a flow diagram illustrating an exemplary method for responding to a management message at a base station;

FIG. 7 is a flow diagram illustrating an exemplary method for managing terminal units at a network management system; and

FIG. 8 is a flow diagram illustrating an exemplary method for responding to a management message at a terminal unit.

DETAILED DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention and its advantages are best understood by referring to FIGS. 1 through 8 of the drawings, like numerals being used for like and corresponding parts of the various drawings.

FIG. 1 is a block diagram illustrating an exemplary communications system <b>10</b>. In the illustrated embodiment, system <b>10</b> comprises a plurality of terminal units <b>12</b>, a base station (BTS) <b>14</b>, an access router <b>16</b>, a private packet network <b>18</b>, a network management system <b>20</b>, a circuit-switched gateway <b>22</b>, a gatekeeper <b>24</b>, and a packet-switched gateway <b>26</b>. Other embodiments of system <b>10</b> may be used without departing from the scope of the present invention.

Each terminal unit <b>12</b> communicates with base station <b>14</b> over a wireless interface <b>28</b>. Terminal unit <b>12</b> provides packet voice, fax, and/or data services to a subscriber of system <b>10</b> by exchanging packets of data with base station <b>14</b>. Each terminal unit <b>12</b> may be uniquely identified in system <b>10</b> by a network address, such as an Internet Protocol (IP) address. The network address may be statically or dynamically assigned. Terminal unit <b>12</b> may comprise any device capable of communicating with base station <b>14</b> over wireless interface <b>28</b>. Terminal unit <b>12</b> could, for example, comprise a computer <b>30</b> coupled to a wireless modem <b>32</b>. Computer <b>30</b> may support packet data, fax, and/or voice applications executed by the subscriber. A telephone <b>34</b> or a fax machine could also be coupled to computer <b>30</b>. Other embodiments of terminal unit <b>12</b> may be used without departing from the scope of the present invention. For example, terminal unit <b>12</b> could also comprise a mobile telephone, such as a Global System for Mobile communication (GSM) mobile station.

Wireless interface <b>28</b> communicatively couples terminal unit <b>12</b> and base station <b>14</b>. In this document, the term “wireless” designates the use of a radio or over-the-air interface to communicate with terminal unit <b>12</b>. Wireless interface <b>28</b> may comprise any suitable circuit-switched or packet-switched wireless interface. Wireless interface <b>28</b> may, for example, comprise a GSM Enhanced Data rates for GSM Evolution (GSM/EDGE) interface.

Base station <b>14</b> is coupled to access router <b>16</b>. In this document, the term “couple” refers to any direct or indirect connection between two or more elements in system <b>10</b>, whether or not those elements physically contact one another. Base station <b>14</b> provides bi-directional communication with one or more terminal units <b>12</b> in a specified geographic area. For example, base station <b>14</b> transmits and receives packet messages to and from terminal units <b>12</b> over wireless interface <b>28</b>. Base station <b>14</b> also transmits and receives packet messages to and from private network <b>18</b> through access router <b>16</b>. Each base station <b>14</b> may be uniquely identified in system <b>10</b> by a network address, such as an IP address. The network address may be statically or dynamically assigned. Base station <b>14</b> may comprise any suitable device operable to facilitate communication with terminal units <b>12</b>. Base station <b>14</b> may, for example, comprise one or more radio transceivers capable of transmitting packet-switched messages to and receiving messages from terminal unit <b>12</b> over wireless interface <b>28</b>.

Access router <b>16</b> is coupled to base station <b>14</b> and private network <b>18</b>. Access router <b>16</b> routes packets containing voice, fax, and/or data traffic in system <b>10</b>. Access router <b>16</b> receives packets from base station <b>14</b> and routes the packets over private network <b>18</b>. Access router <b>16</b> also receives packets from private network <b>18</b> for a terminal unit <b>12</b> served by base station <b>14</b>, and access router <b>16</b> routes the packets to base station <b>14</b>. Access router <b>16</b> may comprise any suitable device operable to route messages over private network <b>18</b>. Access router <b>16</b> could, for example, comprise a wireless router and concentrator.

Private network <b>18</b> is coupled to access router <b>16</b>, network management system <b>20</b>, circuit-switched gateway <b>22</b>, gatekeeper <b>24</b>, and packet-switched gateway <b>26</b>. Private network <b>18</b> facilitates communication between components in system <b>10</b> by transferring messages between the components. Private network <b>18</b> may comprise any suitable packet network, such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or any other communications system or systems at one or multiple locations.

Network management system <b>20</b> provides management functionality in system <b>10</b>. Network management system <b>20</b> may communicate with other components in system <b>10</b> over a management plane. The management plane carries management messages between network management system <b>20</b> and the components in system <b>10</b>. In the illustrated embodiment, network management system <b>20</b> comprises a subscriber management platform (SMP) <b>36</b> and an operations support system (OSS) <b>38</b>.

SMP <b>36</b> is coupled to private network <b>18</b>. SMP <b>36</b> provides subscriber management and billing functionality in system <b>10</b>. This may include, for example, authentication functionality to protect against fraud and customer registration functionality to collect customer data used in provisioning services and billing customers. This may also include rating functionality to create flexible pricing plans for subscribers, billing functionality to generate real-time or invoice customer bills, and customer management functionality to provide access to customer profiles, activities, and account balances. SMP <b>36</b> may comprise any suitable device operable to provide subscriber management functionality.

OSS <b>38</b> is coupled to private network <b>18</b>. OSS <b>38</b> provides network management functionality to manage the components in system <b>10</b>. This may include, for example, provisioning, administration, status, and performance monitoring functionality for the networks components in system <b>10</b>. This may also include configuration, fault, and security management. OSS <b>38</b> may comprise any suitable device operable to provide network management functionality. In one embodiment, OSS <b>38</b> may be identified by a network address, such as a statically or dynamically assigned IP address.

Circuit-switched gateway <b>22</b> is coupled to private network <b>18</b>, gatekeeper <b>24</b>, and a public switched circuit network (SCN) <b>40</b>. SCN <b>40</b> may comprise any suitable circuit-switched network, such as a public switched telephone network (PSTN) or an integrated services digital network (ISDN). Gateway <b>22</b> facilitates communication between system <b>10</b> and SCN <b>40</b> by transferring messages between private network <b>18</b> and SCN <b>40</b>. Gateway <b>22</b> also performs an interworking function to translate between the packet-switched transmission and signaling protocols used by private network <b>18</b> and the circuit-switched protocols used by SCN <b>40</b>. In one embodiment, system <b>10</b> uses the protocols defined by the International Telecommunications Union—Telecommunications (ITU-T) H.323 standard, and gateway <b>22</b> interworks the H.323 signaling protocols with the circuit switched protocols of SCN <b>40</b>. Gateway <b>22</b> may comprise any suitable device operable to facilitate communication between system <b>10</b> and SCN <b>40</b>. Gateway <b>22</b> may, for example, comprise an H.323 gateway.

Gatekeeper <b>24</b> is coupled to private network <b>18</b>, circuit-switched gateway <b>22</b>, and packet-switched gateway <b>26</b>. Gatekeeper <b>24</b> provides call control services in system <b>10</b>. This may include, for example, tracking the location of each terminal unit <b>12</b> and routing messages to and from the base station <b>14</b> currently serving a particular terminal unit <b>12</b>. This may also include address translation to map between the telephone number and current EP address of a terminal unit <b>12</b>. Gatekeeper <b>24</b> may comprise any suitable device operable to provide call control services in system <b>10</b>. In one embodiment, gatekeeper <b>24</b> comprises an H.323 gatekeeper.

Packet-switched gateway <b>26</b> is coupled to private network <b>18</b>, gatekeeper <b>24</b>, and a public packet-switched network <b>42</b>. Public packet-switched network <b>42</b> may comprise any suitable packet-switched network, such as the Internet, a LAN, a MAN, a WAN, or any other communications system or systems in one or multiple locations. Packet-switched gateway <b>26</b> facilitates communication between system <b>10</b> and public network <b>42</b> by transferring messages between private network <b>18</b> and public network <b>42</b>. Gateway <b>26</b> may comprise any suitable device operable to facilitate communication between system <b>10</b> and public network <b>42</b>. Gateway <b>26</b> may, for example, comprise an access router that supports routing and firewalling functionality.

In operation, network management system <b>20</b> manages base stations <b>14</b> by transmitting management messages to base stations <b>14</b> over private network <b>18</b>. Network management system <b>20</b> also manages terminal units <b>12</b> by transmitting management messages to terminal units <b>12</b> over private network <b>18</b> and wireless interface <b>28</b>. In one embodiment, network management system <b>20</b> communicates the management messages to terminal units <b>12</b> and/or base stations <b>14</b> transparently in system <b>10</b>. In this document, the term “transparently” refers to a communication between two elements in system <b>10</b>, where components in system <b>10</b> that link the two elements do not perform a mediation function to translate the management messages. Network management system <b>20</b> and base station <b>14</b> may communicate transparently across private network <b>18</b>. Network management system <b>20</b> and terminal unit <b>12</b> may also communicate transparently over private network <b>18</b> and wireless interface <b>28</b>. The components in system <b>10</b> that link network management system <b>20</b>, terminal units <b>12</b>, and base stations <b>14</b> do not perform a mediation function to translate the management messages.

FIG. 2 is a block diagram illustrating an exemplary network management architecture <b>50</b> for communications system <b>10</b> of FIG. <b>1</b>. In the illustrated embodiment, network management architecture <b>50</b> comprises SMP 36, a network node management (NNM) platform <b>60</b>, a gateway management platform <b>62</b>, a router management platform <b>64</b>, a wireless access network management platform <b>66</b>, a local area network (LAN) <b>68</b>, and a router <b>70</b>. Other embodiments of network management architecture <b>50</b> may be used without departing from the scope of the present invention.

NNM platform <b>60</b> is coupled to LAN <b>68</b>. NNM platform <b>60</b> provides an integrated management platform for the various components in system <b>10</b>, such as terminal units <b>12</b>, base stations <b>14</b>, routers <b>16</b>, and gateways <b>22</b> and <b>26</b>. NNM platform <b>60</b> provides network management functionality such as configuration, fault, performance monitoring, event management, database control, general security, trouble management, and asset management functionality. In addition, NNM platform <b>60</b> may provide application programming interfaces (APIs) that allow additional applications to be executed on NNM platform <b>60</b>. These additional applications could include, for example, analysis tools used in system <b>10</b>. NNM platform <b>60</b> may comprise any suitable device operable to provide integrated network management in system <b>10</b>.

Gateway management platform <b>62</b> is coupled to LAN <b>68</b>. Gateway management platform <b>62</b> provides management functionality to control circuit-switched gateway <b>22</b>. Gateway management platform <b>62</b> may provide provisioning, administration, status, and performance monitoring functionality for gateway <b>22</b>. Gateway management platform <b>62</b> may comprise any suitable device operable to provide management functionality for gateway <b>22</b>. Gateway management platform <b>62</b> could, for example, comprise an H.323 gateway management platform.

Router management platform <b>64</b> is coupled to LAN <b>68</b>. Router management platform <b>64</b> provides management functionality to control access routers <b>16</b>, packet-switched gateway <b>26</b>, and router <b>70</b> in system <b>10</b>. Router management platform <b>64</b> may provide provisioning, administration, status, and performance monitoring functionality for routers <b>16</b> and <b>70</b> and gateway <b>26</b>. Router management platform <b>64</b> may comprise any suitable device operable to provide management functionality for routers <b>16</b> and <b>70</b> and gateway <b>26</b>.

Wireless access network management platform <b>66</b>, also called a wireless management platform, is coupled to LAN <b>68</b>. Wireless management platform <b>66</b> provides management functionality to control terminal units <b>12</b> and base stations <b>14</b> in system <b>10</b>. Wireless management platform <b>66</b> may comprise any suitable device operable to provide management functionality for terminal units <b>12</b> and base stations <b>14</b> in system <b>10</b>.

LAN <b>68</b> couples NNM platform <b>60</b>, gateway management platform <b>62</b>, router management platform <b>64</b>, and wireless management platform <b>66</b> to router <b>70</b>. LAN <b>68</b> facilitates communication between components in network management architecture <b>50</b> and system <b>10</b>. LAN <b>68</b> may, for example, transfer management messages between components in network management architecture <b>50</b> and router <b>70</b>. LAN <b>68</b> may comprise any suitable packet network.

Router <b>70</b> is coupled to LAN <b>68</b> and private packet network <b>18</b>. Router <b>70</b> facilitates communication between network management architecture <b>50</b> and system <b>10</b>. Router <b>70</b> may, for example, transfer management messages between LAN <b>68</b> and components of system <b>10</b> coupled to private network <b>18</b>. Router <b>70</b> may comprise any suitable device operable to route management messages over private network <b>18</b>. Router <b>70</b> may, for example, comprise a unicast router or a multicast router.

In operation, router <b>70</b> receives management messages for terminal units <b>12</b> and/or base stations <b>14</b> from wireless management platform <b>66</b>, and router <b>70</b> routes the messages over private network <b>18</b>. Router <b>70</b> also receives responses and messages from terminal units <b>12</b> and/or base stations <b>14</b>, and router <b>70</b> routes the messages to wireless management platform <b>66</b> over LAN <b>68</b>.

Router <b>70</b> routes management messages to base stations <b>14</b> using the network address of base stations <b>14</b>. In one embodiment, router <b>70</b> comprises a unicast router, and router <b>70</b> routes management messages to a base station <b>14</b> using the network address of that base station <b>14</b>. In another embodiment, router <b>70</b> comprises a multicast router, and router <b>70</b> may route a management message to one base station <b>14</b> or groups of base stations <b>14</b>. Multicast router <b>70</b> may also broadcast the message to all base stations <b>14</b>. In a particular embodiment, each base station <b>14</b> supports the Internet Group Membership Protocol, which allows base stations <b>14</b> to inform multicast router <b>70</b> of the group membership of each base station <b>14</b>.

Similarly, router <b>70</b> routes management messages to terminal units <b>12</b> using the network address of terminal units <b>12</b>. In one embodiment, router <b>70</b> comprises a unicast router, and router <b>70</b> routes management messages to a terminal unit <b>12</b> using the network address of that terminal unit <b>12</b>. In another embodiment, router <b>70</b> comprises a multicast router, and router <b>70</b> may route a management message to one terminal unit <b>12</b>, groups of terminal units <b>12</b>, or all terminal units <b>12</b>. In a particular embodiment, each terminal unit <b>12</b> supports the Internet Group Membership Protocol, which allows terminal units <b>12</b> to inform multicast router <b>70</b> of the group membership of each terminal unit <b>12</b>.

FIG. 3 is a block diagram illustrating an exemplary management protocol architecture <b>100</b> for managing base stations <b>14</b> in communications system <b>10</b> of FIG. <b>1</b>. In the illustrated embodiment, management protocol architecture <b>100</b> comprises a wireless access management protocol stack <b>120</b>, a router protocol stack <b>140</b>, an access router protocol stack <b>150</b>, and a base station protocol stack <b>160</b>. Other embodiments of management protocol architecture <b>100</b> may be used without departing from the scope of the present invention.

Wireless access management protocol stack <b>120</b> comprises an application layer <b>121</b>, a User Datagram Protocol (UDP) layer <b>128</b>, a Transmission Control Protocol (TCP) layer <b>130</b>, an Internet Protocol (IP) layer <b>132</b>, and an Ethernet layer <b>134</b>. Application layer <b>121</b> comprises a manager application <b>122</b>, a Simple Network Management Protocol (SNMP) entity <b>124</b>, and a File Transfer Protocol/Multicast File Transfer Protocol (FTP/MFTP) entity <b>126</b>.

Router protocol stack <b>140</b> comprises an Ethernet layer <b>142</b>, an IP layer <b>144</b>, and a frame relay layer <b>146</b>. Access router protocol stack <b>150</b> comprises a frame relay layer <b>152</b>, an IP layer <b>154</b>, and a frame relay layer <b>156</b>. Base station protocol stack <b>160</b> comprises an application layer <b>161</b>, a UDP layer <b>168</b>, a TCP layer <b>170</b>, an IP layer <b>172</b>, and a frame relay layer <b>174</b>. Application layer <b>161</b> comprises an agent application <b>162</b>, a SNMP entity <b>164</b>, and a FTP/MFTP entity <b>166</b>.

Application layers <b>121</b> and <b>161</b> support the execution of management applications <b>122</b> and <b>162</b> to manage base stations <b>14</b> in system <b>10</b>. In one embodiment, system <b>10</b> uses a Telecommunications Management Network (TMN) architecture. In this embodiment, communications between application layers <b>121</b> and <b>161</b> occur across TMN interfaces that use a manager-agent relationship. In a particular embodiment, system <b>10</b> adheres to the TMN principles in the International Telegraph and Telephone Consultative Committee (CCITT) Recommendation M.3010, entitled “Principles of a Telecommunications Management Network.”

Applications <b>122</b> and <b>162</b> use SNMP entities <b>124</b> and <b>164</b> and FTP/MFTP entities <b>126</b> and <b>166</b> to manage base stations <b>14</b>. SNMP entities <b>124</b> and <b>164</b> support network management operations, and FTP/MFTP entities <b>126</b> and <b>166</b> support file transfer operations in system <b>10</b>. Applications <b>122</b> and <b>162</b> may use SNMP entities <b>124</b> and <b>164</b> and FTP/MFTP entities <b>126</b> and <b>166</b> to construct complex management operations.

UDP layers <b>128</b> and <b>168</b>, along with IP layers <b>132</b>, <b>144</b>, <b>154</b>, and <b>172</b>, support the use of UDP/IP connections between wireless management platform <b>66</b> and base stations <b>14</b>. TCP layers <b>130</b> and <b>170</b>, along with IP layers <b>132</b>, <b>144</b>, <b>154</b>, and <b>172</b>, support the use of TCP/IP connections between wireless management platform <b>66</b> and base stations <b>14</b>. SNMP entities <b>124</b> and <b>164</b> use the UDP/IP connections to transport SNMP messages in system <b>10</b>. FTP/MFTP entities <b>126</b> and <b>166</b> also use the UDP/IP connections to perform multicasting operations, while FTP/MFTP entities <b>126</b> and <b>166</b> use the TCP/IP connections to transport negative acknowledgement signals from base stations <b>14</b>.

Ethernet layers <b>134</b> and <b>142</b> support the physical communications link between wireless management platform <b>66</b> and router <b>70</b>. Frame relay layers <b>146</b> and <b>152</b> support the physical communications link between router <b>70</b> and access router <b>16</b>. Frame relay layers <b>156</b> and <b>174</b> support the physical communications link between access router <b>16</b> and base station <b>14</b>. In one embodiment, frame relay layers <b>146</b>, <b>152</b>, <b>156</b>, and <b>174</b> may not support multicast operations, and point-to-multipoint routing is performed in IP layers <b>144</b>, <b>154</b>, and <b>172</b> using a separate virtual circuit for each base station <b>14</b>.

As illustrated in FIG. 3, router <b>70</b> and access router <b>16</b> transport management messages between wireless management platform <b>66</b> and base station <b>14</b> without performing any mediation functions. The management messages pass transparently between wireless management platform <b>66</b> and base station <b>14</b>. This allows system <b>10</b> to use less complex components since the components do not require mediation functionality. It also decreases the load on router <b>70</b> and access router <b>16</b> because they are not required to perform mediation functions, so router <b>70</b> and access router <b>16</b> are able to perform other tasks. Further, router <b>70</b> and access router <b>16</b> may not need to understand proprietary management interfaces used by other components to properly transport the management messages in system <b>10</b>.

FIG. 4 is a block diagram illustrating an exemplary management protocol architecture <b>200</b> for managing terminal units <b>12</b> in communications system <b>10</b> of FIG. <b>1</b>. In the illustrated embodiment, management protocol architecture <b>200</b> comprises wireless access management protocol stack <b>120</b>, router protocol stack <b>140</b>, access router protocol stack <b>150</b>, base station protocol stack <b>160</b>, and a terminal unit protocol stack <b>220</b>. Other embodiments of management protocol architecture <b>200</b> may be used without departing from the scope of the present invention.

Management protocol architecture <b>200</b> uses several protocol layers in wireless access management protocol stack <b>120</b>, router protocol stack <b>140</b>, access router protocol stack <b>150</b>, and base station protocol stack <b>160</b> from management protocol architecture <b>100</b>. In addition, wireless access management protocol stack <b>120</b> comprises another application manager application <b>136</b>. Base station protocol stack <b>160</b> further comprises a radio interface layer <b>176</b>, a Radio Link Control / Medium Access Control (RLC/MAC) layer <b>178</b>, a Logical Link Control (LLC) layer <b>180</b>, and a Subnetwork Dependent Convergence Protocol (SNDCP) layer <b>182</b>. Terminal unit protocol stack <b>220</b> comprises an application layer <b>221</b>, a UDP layer <b>228</b>, a TCP layer <b>230</b>, an IP layer <b>232</b>, a SNDCP layer <b>234</b>, a LLC layer <b>236</b>, a RLC/MAC layer <b>238</b>, and a radio interface layer <b>240</b>. Application layer <b>221</b> comprises an agent application <b>222</b>, a SNMP entity <b>224</b>, and a FTP/MFTP entity <b>226</b>.

Application layers <b>121</b> and <b>221</b> support the execution of management applications <b>136</b> and <b>222</b> to manage terminal units <b>12</b>. SNMP entities <b>124</b> and <b>224</b> support network management operations, and FTP/MFTP entities <b>126</b> and <b>226</b> support file transfers in system <b>10</b>. Applications <b>136</b> and <b>222</b> may use SNMP entities <b>124</b> and <b>224</b> and FTP/MFTP entities <b>126</b> and <b>226</b> to construct complex management operations to provide broad management capabilities over terminal units <b>12</b>.

UDP layers <b>128</b> and <b>228</b>, along with IP layers <b>132</b>, <b>144</b>, <b>154</b>, and <b>232</b>, support the use of UDPIIP connections between wireless management platform <b>66</b> and terminal units <b>12</b>. TCP layers <b>130</b> and <b>230</b>, along with IP layers <b>132</b>, <b>144</b>, <b>154</b>, and <b>232</b>, support the use of TCP/IP connections between wireless management platform <b>66</b> and terminal units <b>12</b>. SNMP entities <b>124</b> and <b>224</b> use the UDP/IP connections to transport SNMP messages in system <b>10</b>. FTP/MFTP entities <b>126</b> and <b>226</b> also use the UDP/IP connections to perform multicasting operations, while FTP/MFTP entities <b>126</b> and <b>226</b> use the TCP/IP connections to transport negative acknowledgement signals from terminal units <b>12</b>. Frame relay layers <b>146</b>, <b>152</b>, <b>156</b>, and <b>162</b> may not support multicast operations, so point-to-multipoint routing may be performed in IP layers <b>144</b> and <b>154</b> using a separate virtual circuit for each base station <b>14</b>. Base station <b>14</b> then forwards the messages to the appropriate terminal unit <b>12</b>.

Radio interface layers <b>176</b> and <b>240</b> manage wireless interface <b>28</b> between terminal unit <b>12</b> and base station <b>14</b>. RLC/MAC layers <b>178</b> and <b>238</b> support the transfer of information over radio interface layers <b>176</b> and <b>240</b>. RLC/MAC layers <b>178</b> and <b>238</b> may, for example, map LLC frames from LLC layers <b>180</b> and <b>236</b> onto RLC frames transmitted over wireless interface <b>28</b>. LLC layers <b>180</b> and <b>236</b> provide a reliable ciphered logical link between terminal unit <b>12</b> and base station <b>14</b>, and messages are transferred between LLC layers <b>180</b> and <b>236</b> in LLC frames. SNDCP layers <b>182</b> and <b>234</b> map messages having a network-level protocol, such as an IP protocol, onto LLC frames for transport between terminal unit <b>12</b> and base station <b>14</b>. SNDCP layers <b>182</b> and <b>234</b> also perform encryption, header compression, and data compression of network-layer messages.

As illustrated in FIG. 4, base station <b>14</b>, access router <b>16</b>, and router <b>70</b> transport management messages between wireless management platform <b>66</b> and terminal units <b>12</b> without performing any mediation functions. The management messages pass transparently between wireless management platform <b>66</b> and terminal units <b>12</b>. This also allows system <b>10</b> to use less complex components and to decrease the load on base stations <b>14</b>, access router <b>16</b>, and router <b>70</b>. It also allows base stations <b>14</b>, access router <b>16</b>, and router <b>70</b> to transport management messages in system <b>10</b> without understanding proprietary interfaces used by the components in system <b>10</b>.

FIG. 5 is a flow diagram illustrating an exemplary method for managing base stations <b>14</b> at network management system <b>20</b>. Network management system <b>20</b> generates a management message for one or more base stations <b>14</b> at a step <b>400</b>. This may include, for example, wireless management platform <b>66</b> generating the message. Wireless management platform <b>66</b> communicates the management message to router <b>70</b> at a step <b>402</b>. Router <b>70</b> transparently routes the management message to one or more of the base stations <b>14</b> at a step <b>404</b>. This may include, for example, router <b>70</b> routing the message over packet network <b>18</b> to access routers <b>16</b> coupled to base stations <b>14</b>. Router <b>70</b> may use the network addresses of the base stations <b>14</b> to route the message to base stations <b>14</b>. Router <b>70</b> may also use Internet Group Messaging Protocol messages received from base stations <b>14</b> to multicast the management message to base stations <b>14</b>. Router <b>70</b> receives a response to the management message at a step <b>406</b>. The response may be communicated transparently from base station <b>14</b>. Router <b>70</b> communicates the response to wireless management platform <b>66</b> at a step <b>408</b>. This may include, for example, router <b>70</b> communicating the response over LAN <b>68</b> to wireless management platform <b>66</b>.

FIG. 6 is a flow diagram illustrating an exemplary method for responding to a management message at base station <b>14</b>. Base station <b>14</b> receives a management message from network management system <b>20</b> at a step <b>440</b>. This may include, for example, access router <b>16</b> receiving the management message over private network <b>18</b> and forwarding the message to base station <b>14</b>. Base station <b>14</b> performs a function requested by the management message at a step <b>442</b>. The function may comprise any suitable management function capable of execution by base station <b>14</b>. This may include, for example, base station <b>14</b> determining a current status of each transceiver in base station <b>14</b>.

Base station <b>14</b> generates a response to the management message at a step <b>444</b>. The response may indicate that base station <b>14</b> performed some action, or the response may include information requested by network management system <b>20</b>. Base station <b>14</b> transparently communicates the response to network management system <b>20</b>. Base station <b>14</b> communicates the response to access router <b>16</b> at a step <b>446</b>, and access router <b>16</b> routes the response to network management system <b>20</b> at a step <b>448</b>. This may include, for example, access router <b>16</b> routing the response to network management system <b>20</b> using the network address of OSS <b>38</b>.

FIG. 7 is a flow diagram illustrating an exemplary method for managing terminal units <b>12</b> at network management system <b>20</b>. Network management system <b>20</b> generates a management message for one or more terminal units <b>12</b> at a step <b>480</b>. This may include, for example, wireless management platform <b>66</b> generating the message. Wireless management platform <b>66</b> communicates the management message to router <b>70</b> at a step <b>482</b>. Router <b>70</b> routes the management message to one or more of the terminal units <b>12</b> at a step <b>484</b>. This may include, for example, router <b>70</b> routing the message to base stations <b>14</b> that are currently serving terminal units <b>12</b>. Router <b>70</b> may use the network addresses of the terminal units <b>12</b> to route the message to terminal units <b>12</b>. Router <b>70</b> may also use Internet Group Messaging Protocol messages received from terminal units <b>12</b> to multicast the management message to terminal units <b>12</b>. Router <b>70</b> receives a response to the management message at a step <b>486</b>. The response may be communicated transparently from base station <b>14</b>. Router <b>70</b> communicates the response to wireless management platform <b>66</b> at a step <b>488</b>. This may include, for example, router <b>70</b> communicating the response over LAN <b>68</b> to wireless management platform <b>66</b>.

FIG. 8 is a flow diagram illustrating an exemplary method for responding to a management message at terminal unit <b>12</b>. Terminal unit <b>12</b> receives a management message from network management system <b>20</b> at a step <b>520</b>. This may include, for example, access router <b>16</b> receiving the management message over private network <b>18</b> and communicating the message to base station <b>14</b> serving terminal unit <b>12</b>, and base station <b>14</b> communicating the message to terminal unit <b>12</b> over wireless interface <b>28</b>. Terminal unit <b>12</b> performs a function requested by the management message at a step <b>522</b>. The function may comprise any suitable management function capable of execution by terminal unit <b>12</b>. This may include, for example, determining a current status of terminal unit <b>12</b>.

Terminal unit <b>12</b> generates a response to the management message at a step <b>524</b>. The response may indicate that terminal unit <b>12</b> performed some action, or the response may include information requested by network management system <b>20</b>. Terminal unit <b>12</b> transparently communicates the response to network management system <b>20</b>. Terminal unit <b>12</b> communicates the response to access router <b>16</b> through base station <b>14</b> at a step <b>526</b>, and access router <b>16</b> routes the response to network management system <b>20</b> at a step <b>528</b>. This may include, for example, access router <b>16</b> routing the response to network management system <b>20</b> using the network address of OSS <b>38</b>.

Although the present invention has been described in several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes, variations, alterations, transformations, and modifications as fall within the spirit and scope of the appended claims.