The application is a divisional application of a PCT application with an international application date of 2006, 3 and 9, an international application number of PCT/US2006/008795, and an invention name of a method and equipment for automatic configuration of a wireless communication network, which enters a patent application with a national phase application number of 200680014896.2 in China.
Detailed Description
Before explaining several embodiments in detail, it is to be understood that the scope of the invention should not be limited to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.
Fig. 1A illustrates a first wireless communication network topology 100 for constructing one embodiment. Communication network 100 illustrates an infrastructure topology in which one BSC supports several BTSs and one MSC also supports several BSCs.
The network planning of such a network topology may comprise the following steps:
the topographic map of the coverage area is analyzed,
considering the terrain and capacity requirements as a function of location, selecting candidate site locations and other network parameters,
simulation software was run to analyze system performance and capacity,
adjusting the parameters and the positions, and then running the simulation,
after network construction, drive tests are performed to confirm network coverage, capacity and performance, an
The drive test data is analyzed. The above process is repeated.
The topology shown in FIG. 1A may remain unchanged in terms of its infrastructure component availability, location, capabilities, and so forth. However, changes such as infrastructure component relocation, addition, deletion, loss of function, and/or external factors may dynamically change the topology of the network. In such cases, the network may be re-planned and reconfigured manually, for example, when a new BTS is added to or removed from the network. This is partly caused by the fact that: a BTS cannot detect or sense ("listen or see") other BTSs in the same way it can detect or sense mobile devices. That is, the BTS detects reverse link wireless communications (signaling, voice and data communications from the mobile device to the wireless infrastructure) from nearby mobile devices, but the BTS cannot detect uplink wireless communications (signaling, voice and data communications from the wireless infrastructure to the mobile device) from other BTSs. For example, in a CDMA system, a newly added node (e.g., BTS) must be assigned a unique PN offset, but before assigning a unique PN offset to the added node, the network planner must first figure out which PN offsets have already been assigned to other nodes that are present. In such cases, it is not practical to perform the network planning routine described above.
Fig. 1B illustrates a network topology according to one embodiment, where nodes 102, 104, 106 have some kind of sensor receiver or sensor/transmitter capability 110, 112, 114 to enable the nodes to communicate with each other. In this manner, the nodes 102, 104, 106 receive uplink communications from some or all of the nodes 102, 104, 106, 108 in the network, determine or calculate some network parameters and communicate the parameters to other nodes, e.g., via the backhaul 116 or otherwise. The node receiving the parameters may adjust, reconfigure, or set its operating conditions according to the received parameters or feedback from other nodes. Such information exchange includes declaring changes in topology (e.g., relocation, addition, deletion, and/or loss of functionality of nodes), resource availability, capability, presence, absence, and/or changes in data as measured by the sensor receivers. Such exchange of information may allow the network infrastructure to automatically determine the network status and, if desired, reconfigure itself and/or other network components when changes occur.
In one embodiment, the sensors provided on the nodes may comprise mobile phones with backhaul connections (e.g., IP backhaul connections) that may receive and send information from and to existing other nodes. For example, the node 106 may contain only one sensor receiver (e.g., a mobile device) that may be carried by a user, mounted on a vehicle, or held at a fixed location. In this manner, the nodes may communicate with each other and exchange parameters measured across the entire or local network (e.g., handoff parameters, neighbor lists for each node, operating frequencies and codes, power transmission levels, power levels received from other nodes, PN offset measurements of signals broadcast by other nodes, antenna configurations), and other information needed for wireless infrastructure operation, including detection of other wireless infrastructures.
In one embodiment, the smart sensor enabled node communicates with other nodes and exchanges information about its operating conditions (e.g., its power level), and multicasts/broadcasts this information, e.g., via the backhaul, to other nodes that can monitor and/or adjust their operating conditions (e.g., power level, coverage, and antenna pattern and orientation). Adaptive algorithms based on sensor data may be employed to adjust operating conditions, such as varying transmission power and antenna pattern characteristics. These algorithms adaptively maximize coverage and may cause certain nodes in the network to disable themselves or some of their capabilities in favor of other nodes; thus, over-allocation of resources or degradation of network performance (e.g., prevention of "pilot pollution" problems) may be prevented.
Messages transmitted among the nodes may be appropriately encrypted and authenticated to protect the network from hostile denial of service (DOS) attacks. Without such security measures, untrusted parties may compromise the correct operation of the mobile network by sending invalid or malicious sensor measurement data or resource availability data.
Fig. 2 illustrates a wireless communication network topology 200 for constructing one embodiment. Communication network 200 illustrates a dynamic infrastructure topology in which each node may be completely self-contained, i.e., each node may have complete BTS, BSC, and/or MSC functionality.
In one embodiment, the nodes may operate in isolation from each other. For example, a vehicle-mounted BTS may provide wireless communication coverage for a team entirely by itself (autonomously). In this case, each isolated node is completely self-contained, having completely autonomous wireless network functionality including, for example, BTSs, BSCs, MSCs, and/or other functionality to support autonomous operation. This situation may occur in sparsely populated or rural areas (where only a single node may be installed) or when the vehicle is traveling in a desert-like area with no network nearby.
In one embodiment, the nodes 202, 204, 206, 208, which may be fixed or mobile, dynamically cooperate to provide continuous wireless communication coverage over a wide area, similar to commercial cellular systems in urban areas, but with a dynamically changing topology. In this case, there may be more of certain types of resources than needed, as each node may have full functionality. Thus, to properly and/or efficiently use the available infrastructure resources, the network needs to automatically configure/reconfigure itself. Typically, one BSC is required for each BTS group. However, when all nodes have individual BSC capabilities, one node may be automatically selected to provide or share BSC functionality for a group of BTSs. In one embodiment, as shown in fig. 2, nodes 202, 204 and 206 may be in close proximity to each other, and thus one node may be automatically selected to provide MSC and/or BSC capabilities, as well as other functions required for the operation of the wireless network, with the other nodes acting as simple BTSs.
In one embodiment, as shown in fig. 2, mobile node 208 (e.g., which is mounted on a moving object and is operationally isolated from other nodes in a self-contained mode) enters the coverage area of nodes 202, 204, and 206. However, after the nodes 202, 204, 206, 208 disseminate their resource availability and/or capabilities among each other (e.g., by broadcast and/or multicast) and the mobile node 208 determines that it has entered an area covered by other nodes, the mobile node 208 may automatically turn off its MSC and/or BSC capabilities and act as a BTS; thus, initially covered by BSC and/or MSC capabilities provided by one or more of the other nodes 202, 204, and 206. However, when the mobile node 208 leaves the coverage area of the nodes 202, 204, and 206 and its movement causes it to be isolated from other nodes, the node 208 may use its full resource capabilities. When the mobile node 208 again comes within the vicinity of other nodes, the mobile node 208 may negotiate with nearby nodes and automatically reconfigure itself to be in coordination therewith.
In another embodiment, the mobile node 208 may enter the coverage areas of the nodes 202, 204, and 206 and determine that its location has been adequately covered by the received signal strengths of the nodes 202, 204, and 206, and may even decide not to act as a BTS at this time.
In another embodiment, certain nodes may provide connectivity to external networks and/or resources. In this case, such nodes may advertise their special capabilities to other nodes to have the nodes automatically reconfigure themselves to take advantage of the newly advertised resource capabilities. The advertised resources may include connectivity to: the particular circuit or data network switched; a communication processor, e.g., an asynchronous communication interworking function (IWF, modem bank); a packet data serving node; a media gateway, an email or voicemail server, etc.
Many techniques are available to automatically configure the network after communicating resource availability and sensor data information. This information may be communicated to a central processor that evaluates the information, calculates a new network configuration, and then communicates this new configuration to the affected nodes. In one embodiment, a distributed auto-configuration scheme may be used. The sensor and resource availability information may be broadcast or multicast to other nodes using techniques such as IP multicast. Nodes capable of providing a service may broadcast their willingness to do so and may resolve conflicts between multiple nodes capable of providing the same service by repeating the process based on random variable generation and voting. Such services may include not only those services necessary to perform wireless network operations (e.g., BSC, MSC, PDSN, etc.), but may also include central processor functionality for evaluating network information gathered by various nodes. For example, in protocols such as IPv6, similar procedures are used to automatically assign IP addresses to IP devices. The transfer of this information may be triggered by a number of criteria including based on a timer, exceeding a predetermined or dynamic operational or detection threshold, or upon request. After configuring the network, the new configuration may be updated in a DNS or similar database for the nodes to discover the configuration between reconfiguration events. For example, DNS may be used to provision any network services and configuration information by using Service (SRV) records or protocols such as DHCP. A node may independently adjust certain of its operating parameters, such as its transmission power level, according to sensor data broadcast by other nodes that indicates its signal level received by such other nodes. Dissemination of these operating parameter adjustments to other nodes may be automatic or based on predetermined criteria, such as assigned thresholds, timers, or system configurations.
In one embodiment, dynamic resource recovery also adaptively compensates for dynamic load changes and/or node failures. In one embodiment, when an existing resource is overloaded, it may broadcast a request for additional help. The help request may include the following requests: additional wireless call processing resources (e.g., BSC resources), interfaces to external networks, additional RF wireless coverage to support additional wireless users, etc. The existing node automatically reassigns resources among themselves based on location changes, load changes, and the like. Detecting failure and/or lack of such resources and initiating resource recovery and/or network parameter reconfiguration using nodes located at other nodes (which may have left the coverage area or failed to function properly); there is therefore the ability to add additional resources to reassign existing resources on an as needed basis as the network topology changes dynamically. Resource allocation may include releasing BSC call processing resources that were allocated while supporting other nodes, backhaul services to nodes that are no longer in the vicinity, RF assignments that have been superseded by other nodes, and so on.
Fig. 3 is a simplified block diagram of an embodiment of an infrastructure node 304 and a communication device 306 capable of implementing various disclosed embodiments. For a particular media communication, voice, data, packet data, and/or alert messages may be exchanged between infrastructure node 304 and communication device 306 over air interface 308. Various types of messages may be transmitted, such as messages used to establish a communication session between the node and a communication device, registration and paging messages, and messages used to control data transmission (e.g., power control, data rate information, acknowledgment, and so on). Some of these message types are described in further detail below.
For the reverse link, at communication device 306, voice and/or packet data (e.g., from a data source 310) and messages (e.g., from a controller 330) are provided to a Transmit (TX) data processor 312, which formats and encodes the data and messages using one or more coding schemes to generate coded data. Each coding scheme may include any combination of Cyclic Redundancy Check (CRC), convolutional, turbo, block, and other coding, or no coding at all. Voice, packet data, and messages may be encoded using different schemes, and different types of messages may be encoded differently.
The encoded data is then provided to a Modulator (MOD)314 and further processed (e.g., covered, spread with short PN sequences, and scrambled with a long PN sequence assigned to the communication device). The modulated data is then provided to a transmitter unit (TMTR)316 and conditioned (e.g., converted to one or more analog signals, amplified, filtered, and quadrature modulated) to generate a reverse link signal. The reverse link signal is routed through duplexer (D)318 and transmitted via antenna 320 to infrastructure node 304.
At infrastructure node 304, the reverse link signal is received by an antenna 350, routed through a duplexer 352, and provided to a receiver unit (RCVR) 354. Alternatively, the antenna may be part of a wireless carrier network and the connection between the antenna and the BS/BSC may be routed through the internet. Infrastructure node 304 may receive media information and alert messages from communication device 306. Receiver unit 354 conditions (e.g., filters, amplifies, frequency downconverts, and digitizes) the received signal and provides samples. A demodulator (DEMOD)356 receives and processes (e.g., despreads, decovers, and pilot demodulates) the samples to provide recovered symbols. Demodulator 356 may implement a rake receiver that processes multiple instances of the received signal and generates combined symbols. A Receive (RX) data processor 358 then decodes the symbols to recover the data and messages transmitted on the reverse link. The recovered voice/packet data is provided to a data receiver 360 and the recovered messages are provided to a controller 370. Controller 370 may include instructions for: receiving and sending information; receiving and sending a response to the message; identifying availability, capability, location, and/or presence of infrastructure resources; locating an infrastructure node; determining a type of infrastructure resource; reconfiguring network parameters; determining network parameters from forward link communications received from other nodes; adjusting the operating condition based on the network parameters received from the other nodes; and restoring infrastructure resources. The processing by demodulator 356 and RX data processor 358 are complementary to that performed at remote access device 306. Demodulator 356 and RX data processor 358 may further be operated to process multiple transmissions received via multiple channels, e.g., a reverse fundamental channel (R-FCH) and a reverse supplemental channel (R-SCH). Likewise, transmissions may come from multiple communication devices at the same time, each of which may be transmitting on a reverse fundamental channel, a reverse supplemental channel, or both.
On the forward link, at infrastructure node 304, voice and/or packet data (e.g., from a data source 362) and messages (e.g., from controller 370) are processed (e.g., formatted and encoded) by a Transmit (TX) data processor 364, further processed (e.g., covered and spread) by a Modulator (MOD)366, and conditioned (e.g., converted to analog signals, amplified, filtered, and quadrature modulated) by a transmitter unit (TMTR)368 to generate a forward link signal. The forward link signal is routed through duplexer 352 and transmitted via antenna 350 to remote access device 306. The forward link signal comprises a paging signal.
At communication device 306, the forward link signal is received by antenna 320, routed through duplexer 318, and provided to a receiver unit 322. Receiver unit 322 conditions (e.g., downconverts, filters, amplifies, quadrature modulates, and digitizes) the received signal and provides samples. The samples are processed (e.g., despreaded, decovered, and pilot demodulated) by a demodulator 324 to provide symbols, and the symbols are further processed (e.g., decoded and checked) by a receive data processor 326 to recover the data and messages transmitted on the forward link. The recovered data is provided to a data sink 328 and the recovered messages may be provided to a controller 330. Controller 330 may include instructions for: receiving and sending information; receiving and sending a response to the message; identifying availability, capability, location, and/or presence of infrastructure resources; locating an infrastructure node; determining a type of infrastructure resource; reconfiguring network parameters; determining network parameters from forward link communications received from other nodes; adjusting the operating condition based on the network parameters received from the other nodes; and restoring infrastructure resources. Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and protocols. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with the following means: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described above. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. While the ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments, e.g., in an instant messaging service or any general wireless data communication applications, without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.