CN103237361B - Distributed mobile architecture is used to provide system, the method and apparatus of communication - Google Patents

Abstract

The present invention relates to systems, methods and apparatus for providing communication using a distributed mobile architecture. An apparatus for providing a communication path between two or more wireless telephones via one or more wireless transceivers is disclosed. The apparatus includes a housing including a mobile switching center module and including a base station controller module. Furthermore, in another particular embodiment, the mobile switching center module includes a program for switching received telephone calls. In addition, the mobile switching center module includes a program for establishing a peer-to-peer connection with a remote distributed mobile architecture server. The mobile switching center module also includes programs for routing telephone calls to remote mobile infrastructure servers via one or more peer-to-peer internet protocol connections.

Description

Systems, methods and apparatus for providing communications using a distributed mobile architecture

This application is a divisional application of an invention patent application with an application date of October 4, 2005, an application number of 200580033404.X, and an invention title of "system, method and device for providing communication using a distributed mobile architecture".

technical field

The present invention generally relates to a distributed mobile communication system.

Background technique

Access to basic telephone services is especially important for rural and isolated communities. Telephone access allows small-scale enterprises, cooperatives and farmers to obtain accurate information on market prices for their products and to access regional and national markets. Access also reduces the cost of transportation and supports the local tourism industry. By bringing markets to people via telecommunications, rather than forcing people to go out and search for markets, urban migration is reduced and more income and employment potential is generated in rural areas.

Unfortunately, the rapid growth of telecommunications in the last decade has not alleviated the disparity between urban and rural communities. For example, the Asian region has an average imbalance in telephone penetration of more than 10 to 1, often as high as 20 to 1.2. This means that countries with an urban market penetration of four (4) telephone lines per one hundred (100) inhabitants (eg, India and Pakistan) have a rural penetration rate of less than one hundred (100) 0.2 telephone lines for residents. The situation is even more dire in most African countries and in some parts of Latin America. By way of comparison, the inequality in average income levels between urban and rural dwellers in the developing world is usually less than four to one.

Current telephone systems are expensive to deploy. For example, the cost of a typical cellular system including a Mobile Switching Center (MSC), Base Station Controller (BSC), and Home Location Register/Visitor Location Register (HLR/VLR) can exceed $2 million. Furthermore, to be economically viable, such a system would require a minimum of 10,000 users. In many rural areas, the population is not large enough to support the installation of such systems. Furthermore, in many cases, the conditions for operating equipment (eg, MSC, BSC and HLR/VLR) are extremely harsh and environmentally unacceptable. Alternatives to such cellular systems may include wired systems, but the costs associated with deploying and maintaining land lines are prohibitive for some rural areas.

Accordingly, there is a need for an improved communication system that is relatively inexpensive to deploy and operate.

Description of drawings

The invention is pointed out with particularity in the appended claims. However, other features are described in the following detailed description in conjunction with the accompanying drawings in which:

1 is a diagram of a distributed management architecture server having a first exemplary form factor;

Figure 2 is a diagram of an alternate embodiment of a distributed management architecture server having a second exemplary form factor;

Figure 3 is a diagram of another alternative embodiment of a distributed management architecture server having a third exemplary form factor;

Figure 4 is a diagram of a distributed associative communication system;

Fig. 5 is the block diagram of distributed management architecture server;

Figure 6 is a flowchart illustrating the operational logic of a distributed management architecture server;

Figure 7 is a flowchart illustrating the call switching logic of the distributed management architecture server;

Figure 8 is a flowchart illustrating the group call logic of the distributed management architecture server;

9 is a diagram of an example communication system that may incorporate a distributed management architecture server;

10 is a diagram of a wireless local loop communication system that may incorporate a distributed management architecture server;

11 is a diagram of multiple wireless local loop communication systems connected to the public switched telephone network via a single backhaul connection;

12 is a diagram of a communication system in which a distributed management architecture server may be deployed to extend an existing cellular network;

13 is a diagram of a communication system in which distributed management architecture servers may be deployed to cover urban fringes around existing networks;

14 is a diagram of a communication system that can connect a single distributed management architecture server to multiple base transceiver stations and can provide a single backhaul to the public switched telephone network;

Figure 15 is a diagram of a built-in communication system where a distributed management architecture server may be deployed;

16 is an illustration of a mobile field communication system in which multiple distributed management architecture servers may be deployed via multiple vehicles;

17 is a diagram of a communication system in which a distributed management architecture server can use a satellite connection as a backhaul connection;

18 is a diagram of a communication system in which a distributed management architecture server can receive multiple backhaul signals via multiple satellite signals;

19 is an illustration of a communication system in which a single distributed management architecture server can be connected to multiple base transceiver stations;

20 is a diagram of a mobile communication system in which a distributed management architecture server may be deployed via an aircraft;

21 is a diagram of a mobile communication system in which a distributed management architecture server can be deployed via a ship;

22 is a flowchart illustrating a method of deploying a distributed management architecture server; and

Figure 23 is a flowchart illustrating a method of replacing a distributed management architecture server.

detailed description

Referring to FIG. 1 , a Distributed Management Architecture (DMA) is shown and generally designated 100 . As shown in FIG. 1 , the DMA server 100 includes a base 102 and a cover 104 . As shown, the cover 104 is attached to the base by a first cover hinge 106 and a second cover hinge 108 . In certain embodiments, the cover 104 is rotatable about the first cover hinge 106 and the second cover between an open position shown in FIG. 1 and a closed position (not shown) in which the cover 104 covers the base 102, The shape of the DMB server 100 may basically resemble a box or a briefcase.

As shown in FIG. 1 , base 102 has length 110 , width 112 and height 114 . FIG. 1 shows that the DMA server 100 includes a keyboard input device 116 incorporated into the upper surface of the base 102 . Additionally, the DMA server 100 includes a mouse input device 118 which is also incorporated into the upper surface of the base 102 . In particular embodiments, the mouse input device 118 is a touch mouse input device 118 . In addition, the DMA server 100 includes a right button 120 and a left button 122 . In certain embodiments, the right button 120 may be used to perform a right-click function associated with the mouse input device 118 . Additionally, the left button 122 can be used to perform left-click functions associated with the mouse input device 118 .

1 also indicates that the base 102 of the DMA server 100 is formed with ventilation holes 124 to allow air exchange with the interior of the base 102 of the DMA server 100 and to help cool the electronics of the DMA server 100 housed within the base 102. element. Additionally, the base 102 of the DMA server 100 includes a handle 126 attached to the base 102 via a first handle hub 128 and a second handle hub 130 . Base 102 also includes a pair of latch engaging grooves 132 .

As shown in FIG. 1 , the cover portion 104 includes a flat panel display 134 incorporated therein. When the lid 104 is closed, the display 134 is adjacent to the keyboard 116 . Additionally, the lid 104 and base 102 cooperate to protect the display 134, keyboard 116, mouse 118, and buttons 120, 122 when the lid 104 is closed. FIG. 1 also shows a latch 136 incorporated into the lid portion 104 . When the lid 104 is closed, the latch 136 can engage the latch engagement groove 132 to lock the lid in the closed position. As shown in FIG. 1 , an antenna 138 is incorporated into the lid portion 104 . The antenna 138 can be extended during operation and can be retracted when the DMA server 100 is not operating.

In a particular embodiment, the length 110 of the base 102 is 31.0 centimeters. Furthermore, in a particular embodiment, the width 112 of the base 102 is 25.5 centimeters. Additionally, in a particular embodiment, the height 114 of the base 102 to the lid 104 is 7.0 centimeters in the closed position. Thus, the DMA server 100 has a total volume of 5533.5 cm3 and a coverage area of 790.5 cm2. Furthermore, in a particular embodiment, DMA server 100 weighs approximately 5.8 kilograms (kg). Thus, in certain embodiments, DMA server 100 has a total volume of less than 6000 cm3, a footprint of less than 800 cm2, and a weight of less than 6.0 kg.

In certain embodiments, DMA server 100 is relatively rugged. Specifically, the DMA server 100 is operable in a temperature range from minus 20 degrees Celsius to plus 55 degrees Celsius (-20°C to 55°C). Furthermore, the DMA server 100 is sufficiently shock-resistant and can withstand a one-meter drop. Furthermore, the DMA server 100 is sufficiently weatherproof, sufficiently dustproof and sufficiently sandproof. The DMA server 100 is portable, and it can be installed in a vehicle, or carried like a briefcase. Additionally, multiple DMA servers 100 may be deployed as described herein.

FIG. 2 shows an alternative embodiment of a Distributed Management Architecture (DMA) server, generally designated 200 . As shown in FIG. 2 , the DMA server 200 includes a base 202 and a cover 204 that is coupled to the base 202 via a plurality of fasteners 206 (eg, a plurality of screws). Additionally, DMA server 200 has length 208 , width 210 and height 212 . In addition, the base 202 of the DMA server 200 includes a first ventilation hole 214 , a second ventilation hole 216 and a third ventilation hole 218 . In certain embodiments, the vents 214 , 216 , 218 allow air exchange with the interior of the chassis 202 of the DMA server 200 and help cool the electronics of the DMA server 200 housed within the chassis 202 . As shown in FIG. 2 , the DMA server 200 includes an access window 220 . One or more interfaces 222 (eg, cables) are accessible via access window 220 and can be coupled to a base transceiver station (BTS) during deployment of DMA server 200 . As shown in FIG. 2 , the DMA server 200 may be installed within a vehicle 224 . Additionally, multiple DMA servers 200 may be deployed as described herein.

In a particular embodiment, the length 208 of the base 202 is 92.0 centimeters. Furthermore, in a particular embodiment, the width 210 of the base 202 is 45.0 centimeters. Furthermore, in a particular embodiment, the width 212 of the base 202 is 34.0 centimeters. Accordingly, DMA server 200 has a total volume of approximately 140,760 cm3 and a footprint of approximately 4140 cm2. Additionally, in a particular embodiment, DMA server 200 weighs approximately 48 kilograms (kg). Thus, in certain embodiments, DMA server 100 has a total volume of less than 150,000 cubic centimeters, a footprint of less than 5,000 square centimeters, and a weight of less than 50.0 kilograms.

FIG. 3 illustrates another alternative embodiment of a distributed management architecture (DMA), generally designated 300 . As shown in FIG. 3 , DMA server 300 includes housing 302 having length 304 , width 306 and height 308 . Furthermore, the housing 302 is formed with the first ventilation hole 310 and the second ventilation hole 312 . In particular embodiments, the vents 310 , 312 allow air exchange with the interior of the housing 302 of the DMA server 300 and help cool the electronic components of the DMA server 300 within the housing 302 .

As shown in FIG. 3, at least one side of housing 302 is formed with ribs 314 to allow DMA server 300 to slide into a server rack (not shown). Additionally, DMA server 300 includes a clip 316 that is coupled to housing 302 via fasteners (eg, bolts). Clip 316 may be engaged with a server rack (not shown) to prevent DMA server 300 from inadvertently sliding out of the server rack (not shown).

In a particular embodiment, the length 304 of the housing 302 is approximately 76.2 centimeters. Furthermore, in a particular embodiment, the width 306 of the housing 302 is approximately 48.2 centimeters. Furthermore, in a particular embodiment, the height 308 of the housing 302 is approximately 4.3 centimeters. Accordingly, DMA server 300 has a total volume of approximately 15756.5 cm3 and a footprint of approximately 3672.9 cm2. Furthermore, in a particular embodiment, DMA server 300 weighs approximately 17.7 kilograms (kg). Furthermore, in certain embodiments, DMA server 300 is stackable to support various volume requirements. As such, in certain embodiments, DMA server 100 has a total volume of less than 16,000 cubic centimeters, a footprint of less than 4,000 square centimeters, and a weight of less than 20.0 kilograms.

Referring to FIG. 4 , a non-limiting exemplary embodiment of a distributed associative telecommunications system is shown and generally designated 400 . As shown in FIG. 4 , system 400 includes four cellular coverage sites 402 . Each coverage site 402 includes an antenna 404 . In one embodiment, the antenna 404 is connected to a transceiver belonging to a Base Transceiver Station (BTS), and said BTS is a 3 sector BTS. FIG. 4 also indicates that a Distributed Mobile Architecture (DMA) server 406 may be connected to each antenna 404 . In one embodiment, each DMA server 406 is physically connected directly to its respective antenna 404 by a wire or cable 408, for example. Furthermore, in the illustrated embodiment, DMA server 406 may be any of the DMA servers shown in FIGS. 1 , 2 and 3 .

As shown in FIG. 4 , each DMA server 406 is interconnected with other DMA servers 406 via an internet protocol network 410 . As such, there is a peer-to-peer connection 412 between each DMA server 406 in the system 400 . As described in detail below, DMA server 406 may handle telephony traffic transmitted at each antenna 404 . For example, DMA server 406 may switch and route calls received via each antenna 404 . Furthermore, the DMA server 406 can hand off calls to each other as the communication devices move around and between cellular coverage sites 402 . DMA servers 406 may communicate with each other via IP network 410 and may further send calls to each other via IP network 410 . It should be understood that more than four cellular coverage sites 402 may be included in the system, and that only four cellular coverage sites 402 are included in FIG. 4 for purposes of clarity and ease of explanation.

Within the distributed associated telecommunications system 400, the control logic may be distributed and decentralized. Furthermore, the wireless coverage provided by the disclosed system 400 is self-healing and redundant. In other words, due to the interconnection via the IP network 410, if one or more DMA servers 406 lose power, fail, or are otherwise inoperable, telephony traffic handled by the inoperative DMA server 406 can be rerouted to the remaining One of the DMA servers 406 is operable. Furthermore, user data stored in a database (eg, Home Locator Resource (HLR) or Visiting Locator Resource (VLR)) may be equally and thoroughly distributed among all DMA servers 406 . It can also be appreciated that new cellular coverage sites can be easily added to the system 400 as the needs for users increase. In particular, a DMA server may be deployed as described below, connected to an antenna, connected to an IP network, and activated to provide cellular coverage in a new area.

FIG. 5 illustrates an exemplary non-limiting detailed embodiment of a DMA server (eg, one of the DMA servers 406 described in connection with FIG. 4 ). In addition, any of the DMA servers 100, 200, 300 shown in Figures 1, 2 and 3 may include the components shown in Figure 5 and are described in detail herein.

In a particular embodiment, DMA server 406 is essentially a processor or computer having a housing and computer readable medium 500 disposed therein. A power supply 502 may also be placed within the housing of the DMA server 406 to provide power to the DMA server 406 . Power source 502 may be a rechargeable battery placed within DMA server 406, or it may be external to DMA server 406, eg, a standard power outlet. Additionally, a cooling system 504 (eg, a fan with a thermostat) may be placed within the DMA server 406 to prevent the DMA server 406 from overheating. In an alternate embodiment, DMA server 406 may be a single-board processor that does not require a fan.

As shown in FIG. 5 , DMA server 406 may include a mobile switching center (MSC) module 506 and a base station controller (BSC) module 508 embedded within a computer readable medium 500 . In an exemplary, non-limiting embodiment, MSC module 506 may include a gatekeeper (GK) 510 connected to several gateways. For example, a Circuit Gateway (CGW) 512 may be connected to GK 510 , and Circuit Gateway 512 may provide connectivity to Integrated Services Digital Network/Public Switched Telephone Network (ISDN/PSTN) interface 514 . CGW512 can provide switching to packet data conversion circuit. In an exemplary, non-limiting embodiment, the PSTN portion of ISDN/PSTN interface 514 may be an inter-office interface using a Bellcore industry standard ISDN User Part (ISUP) signaling over a Signaling System 7 (SS7) link set. Furthermore, the voice trunk on said interface may be a time slot on a T1 connection. Incoming and outgoing voice calls may be supported on the ISDN portion of the ISDN/PSTN interface 514 .

As further shown in FIG. 5, a packet data server node (PDSN) gateway 516 for CDMA, a gateway GPRS support node (GGSN) for Global System for Mobile communications (GSM) and a session initiation protocol (SIP) Wang Guoluo 518 can be used Connect to GK510. PDSN gateway 516 and SIP gateway 518 may provide connectivity to Internet Protocol (IP) interface 520 . Additionally, the PDSN Gateway 516 or GGSN may establish a reverse tunnel with the PDSN or GGSN Gateway 516 using Generic Routing Encapsulation (GRE). In addition, the PDSN gateway 516 or GGSN may implement the pseudo-random function (RRF)/foreign agent (FA) functionality of the DMA server 406 supporting Mobile IP functionality.

FIG. 5 also shows SS7 gateway 522 , which provides connectivity to ANSI-41 and GSM Mobile Application Part (MAP) interfaces 524 . In a particular embodiment, the ANSI-41 interface may be an SS7 TCAP/SCCP interface on the same set of SS7 links used for ISUP signaling. The SS7 point code can be used to identify the DMA server 406 in an ANSI-41 network. The ANSI-41 interface can be used for roaming registration. Also, in an exemplary, non-limiting embodiment, the GSMMAP interface may be an SS7 TCAP/SCCP interface on the same set of SS7 links used for ISUP signaling. It can be appreciated that there are different MAP protocols from MAP/B to MAP/I, but in the embodiment shown, the different MAP/x protocols do not stack - the protocols are used independently.

As shown in FIG. 5 , a media gateway 526 may also be coupled to GK 510 . In an exemplary, non-limiting embodiment, media gateway 526 may include: a cellular transcoder, one or more intranet gateways, a conference bridge, and group calling functionality. Additionally, an Authentication, Authorization and Accounting (AAA) module 528 may be coupled to GK 510 . In an exemplary, non-limiting embodiment, there are three levels of authentication management. The highest level is for administration, the middle level is for operations, and the lowest level is for normal users. The functionality of the AAA module 528 may be included at the user level.

In an exemplary non-limiting embodiment, the GK 510 may act as an AAA server and a feather server to support advanced supplementary services, short message services, and the like. In addition, GK510 can act as a call manager and can support ISUP and PSTN feature calls. In addition, GK510 can act as a signal gateway, such as IP to SS7 interworking, ISUP, GSMMAP or ANSI-41 to PSTN and ANSI-42/GSM. GK510 can also be used as a data call server.

As shown in FIG. 5 , the BSC module 508 includes a cellular radio network controller (CRNC) 530 and a cellular selection/distribution unit (CSDU) 532 , which are connected to a call protocol controller (CPC) 534 . Conversely, the CPC 534 may be connected to a plurality of Base Transceiver Stations (BTS) 536 . In particular, DMA server 406 includes a BTS interface 538 at CPC 534 that is physically directly connectable to BTS 536 . The CRNC530 provides cellular radio resource management and cellular call control. The CSDU 532 may provide Foundation Channel (FCH) soft handover and allocation, Link Access Control (LAC) processing for in-band signaling, multiplexer (MUX) functions, and centralized power control. Additionally, the CPC534 can convert T1 or E1 messages or ATM interfaces into data packet messages. In a particular embodiment, each BTS 536 supports signals and traffic up to the previous point of the CPC 534 (eg, up to the BTS interface 538). Additionally, in certain embodiments, CRNC 530, CPC 534, CSDU 532, and OAMP 540 may perform one or more functions of a legacy base station controller (BSC).

In an exemplary, non-limiting embodiment, the BTS interface 538 may be an IS-95AORIS-2000 interface over El or ATM, or the BTS interface 538 may be a GSMBTS interface using MAP or Custom Application Logic for Mobile Network Enhancement (CAMEL). In the illustrated embodiment, the CPC 534 may be connected to one or more BTS 536 . FIG. 5 also shows that the BSC module 508 includes an operations, administration, maintenance and provisioning (OAMP) module 540 . In an exemplary, non-limiting embodiment, OAMP module 540 may operate the interface using Simple Network Management Protocol (SNMP). In addition, the OAMP module 540 may include a JAVA user interface. OAMP module 540 may include software agents assigned to each component within DMA server 406 . The agents independently monitor their respective components. Additionally, each agent can supply its own components.

Referring to FIG. 6, an exemplary, non-limiting embodiment of a flowchart is provided to illustrate the operational logic of the DMA server 406 (FIG. 4). The operational logic begins at block 600 with a functional loop wherein, during operation, subsequent steps are performed. At step 602, a call is received, eg, at antenna 404 (FIG. 4) in communication with DMA server 406 (FIG. 4). Next, at decision step 604, it is determined whether the call is local, ie, whether the call is between two mobile communication devices within the same cellular coverage site. If the call is local, the logic moves to block 606 and the call is switched at a local DMA server (ie, a DMA server within the cellular coverage site that received the call). Then, at block 608, the call is connected from the first mobile communication device originating the call to the second mobile communication device via the local DMA server. Returning to decision step 604, if the call is not local, the logic proceeds to block 610 and the call is switched at the DMA server connected to the antenna 404 from which the call was received. Thereafter, at step 612, a call is connected from the first mobile communication device originating the call to the second mobile communication device via a peer-to-peer connection between the first DMA server and the second DMA server.

After the call is connected at block 608 or block 612, the logic continues to block 614 where the call is monitored. For example, the location of the first mobile communication device originating the call can be monitored, the location of the second mobile communication device receiving the call can be monitored, the DMA server handling the call can be monitored, the call through which the call is connected can be monitored Other DMAs in the DMA may monitor the connection (such as a peer-to-peer IP network connection) over which the call is sent. Proceeding to decision step 616, it is determined whether the first mobile device or the second mobile device involved in the call is roaming, ie, moving between sites of cellular coverage provided by the respective antennas. If so, the logic moves to block 618 where calls at the roaming mobile communication device are automatically handed over to the new DMA server and associated antenna at the new cellular coverage site. If no mobile communication devices involved in the call are roaming, the logic proceeds to decision step 620 .

At decision step 620, it is determined whether there is a failed DMA server. If so, the call is rerouted around the failed DMA by establishing one or more different peer-to-peer connections between the one or more different DMA servers that are still in operation. Thereafter, the logic moves to decision step 624 . If at decision step 620 it is determined that no DMA server has failed, then decision step 624 may also be reached. In decision step 624, it is determined whether the call has ended. If not, the logic proceeds to block 626 and maintains the one or more connections through which the call was established. Otherwise, if the call has ended, the logic goes to block 628 and the peer-to-peer connection or multi-connection over which the call was established is terminated, and the logic ends in state 630.

FIG. 7 shows a call that may be performed by the DMA server 406 ( FIG. 4 ) to illustrate handover of a call or subscriber service connection between a first BTS and a second BTS as the mobile communication device moves between zones of cellular coverage. switch logic. The logic begins at block 700 with a loop wherein, when the mobile communication device is activated, the following steps are performed. At block 702, the location of the mobile communication device is monitored at the local DMA server. Continuing to decision step 704, it is determined whether the mobile communication device is to move from a first cellular coverage site provided by the first BTS to a second cellular coverage site provided by the second BTS. If not, the logic passes to decision step 706, where it is determined whether the call has been terminated. The logic ends at state 708 if the call is terminated. Conversely, if the call is not terminated, the logic returns to block 702 and continues to operate as above.

Returning to decision step 704, the logic proceeds to decision step 710 if the user is to move from a first cellular coverage site provided by a first BTS to a second cellular coverage site provided by a second BTS. In decision step 710, it is determined whether the second BTS is locally connected, ie connected to the same DMA server as the first BTS. If so, the logic goes to block 712 and the DMA server switches the call (soft handoff) or user service connection from the first BTS connected to the DMA server to a second BTS connected to the same DMA server. Conversely, if the second BTS is not local, the logic continues to block 714 where the DMA server switches the call from the first BTS connected to the DMA server to the second BTS connected to the second DMA server. From block 712 or block 714, the logic proceeds to decision step 706 and continues as above.

FIG. 8 shows an exemplary non-limiting embodiment of a method for illustrating group call logic that can be implemented at the DMA server 406 (FIG. 4) to communicate between several mobile communication devices with PSTN/ISDN Group calling is provided between users. At block 800, a loop is entered wherein, during operation, the following steps are performed. In decision step 802, it is determined whether more than three (3) callers are participating in a telephone call being processed via one or more DMA servers 406 (FIG. 4). If not, the logic continues to block 804 and normal calls are allowed, eg, two-way calls, three-way conference calls, etc. The logic then ends at state 806 .

In decision step 802, if more than three (3) callers are participating in a telephone call handled via one or more DMA servers 406 (FIG. 4), then the logic proceeds to block 808 and allows full-duplex communication capability Make a group call between all participants of the . Next, at decision step 810, it is determined whether one or more participants disconnected. If so, then at determination block 812, the disconnected one or more participants exit the group call. At block 814, the full-duplex call is then maintained between the remaining group call participants. Returning to decision step 810, if no participants disconnected, then the logic proceeds to decision step 816, where it is determined whether a new participant is connected to the group call. Decision step 816 is also reached from block 814 above.

In decision step 816, if the new participant enters the group call, the new participant is allowed to connect to the group call and can communicate with any one or more of the other participants with full-duplex communication capabilities. The logic then moves to decision step 820 . Decision step 820 is also reached from decision step 816 if no new participants have entered the group call. In decision step 820, it is determined whether all participants are disconnected from the group call. If not, the logic returns to block 808 and continues as above. Conversely, if all participants have disconnected from the group call, the logic proceeds to block 822, where the group call is terminated, and the logic then ends in state 806.

Referring now to FIG. 9 , an exemplary non-limiting embodiment of a telecommunications system is shown and generally designated 900 . As shown, the system includes one or more DMA servers 902 connected to a central MSC 904 of a wireless carrier. The DMA server 902 can be connected to the MSC 904 via an E1CCS (G.703, G732) connection or any other application connection. Instead, the MSC 904 is connected to a Code Division Multiple Access (CDMA) network 906 . Figure 9 also shows that the DMA server 902 can be connected to an independent carrier's switch transfer point (STP) 908. As shown, the DMA server 902 can be connected to the STP 908 via an IS-41+IS-880 (DS0) connection or an ISUPIT TUN7 connection.

As further shown in FIG. 9, the STP 908 may be connected to a short message service (SMS) server 910 to provide text messaging capabilities to mobile communication devices using the system 900 shown in FIG. Additionally, the STP 908 may be connected to a Home Location Register (HLR) 912, a prepaid wireless server 914, and an international roaming network 916 to provide prepaid service and roaming between multiple countries. Figure 9 shows that the DMA server 902 can be connected to the PTSN 918 via an E1CCS (G.703, G732) connection or any other suitable connection.

Referring to FIG. 10 , a wireless local loop (WLL) system is shown and generally designated 1000 . As shown in FIG. 10 , system 1000 includes DMA server 1002 connected to BTS 1004 . Instead, connect the BTS 1004 to the antenna 1006 . Antenna 1006 provides cellular coverage to one or more users 1008 within transmission distance of antenna 1006 . FIG. 10 shows that the system 1000 may also include a data network connection 1010 from the DMA server 1002 . Data network connection 1010 may connect DMA server 1002 to the PSTN via an ISUP/ISDN signaling connection over an SS7 link set or a T1/E1 wireless connection. In addition, the data network connection 1010 may be an IEEE802.11 connection between the DMA server 1002 shown in FIG. 10 and other DMA servers not shown. Advantageously, the DMA server 1002 can employ existing architectures for cellular and SMS data services.

FIG. 11 shows a multiple WLL system, generally designated 1100 . As shown, system 1100 includes multiple WLLs 1102 . Each WLL 1102 may include a DMA server 1104 and an antenna 1106 connected to the DMA server 1104 to provide a cellular coverage site around the antenna 1106 . As shown in Figure 11, WLLs 1102 may be interconnected via a wireless local area network (WLAN) or a wide area network such as a microwave connection. Additionally, a DMA server 1104 within one of the WLLs 1102 may provide a backhaul connection 1108 to the PSTN 1110 . This type of deployment can greatly reduce the costs associated with wireless systems. Since the DMA servers 1104 are connected to each other via WLAN or microwave connections, relatively expensive inter-site backhaul components are eliminated. In addition, using handoff logic, DMA server 1104 can enable roaming between WLLs 1102 and can further provide roaming to external wireless networks or other networks.

Referring to Figure 12, a telecommunications system, generally designated 1200, is shown. As shown in FIG. 12 , system 1200 includes a DMA server 1202 that can be connected to a plurality of BTSs 1204 . Each BTS 1204 may provide cellular coverage to one or more mobile communication devices 1206 (eg, one or more mobile handsets configured to communicate via the DMA server 1202). Figure 12 also shows that the DMA server 1202 may be connected to an MSC 1208 such as that of an existing cellular system. The DMA server 1202 may be connected to the MSC via an IS-41 subset or a MAP subset over a wireless E1/T1 connection. With this implementation, the DMA server 1202, when connected to an existing cellular system MSC 1208, can extend an existing cellular network.

FIG. 13 shows another telecommunications system, generally designated 1300 . As shown, the system 1300 includes: an urban area coverage site 1302 and an urban fringe/near village coverage site 1304 . In an exemplary, non-limiting embodiment, a metropolitan area coverage site 1302 includes a first MSC/BSC center 1306 connected to a second MSC/BSC center 1308 . Additionally, a first representative BTS 1310 and a second representative BTS 1312 are connected to the first MSC/BSC center 1306 . A particular deployment of the device is configured to provide sufficient cellular coverage to mobile communication devices within a metropolitan area coverage site 1302 .

As shown in FIG. 13 , an urban fringe/near village coverage site 1304 includes a DMA server 1314 with multiple BTSs 1316 connected thereto. The DMA server 1314 may provide call switching between BTS 1316 and may locally switch calls made between BTS 1316. However, the DMA server 1314 within the urban fringe/nearby village coverage site 1304 can also connect telephony traffic to the first MSC/BSC center 1306 within the urban area coverage site 1302 via a data network connection 1318 . In one embodiment, the data network connection may be an E1 connection, a T1 connection, a microwave connection, or an 802.11 connection established via an IS-41 subset or a MAP subset. Deployment of DAM servers 1314 in locations such as those described above (i.e., on the edge of cities or nearby villages) and connections of DMA servers 1314 to MSC/BSC centers 1306 in urban areas can provide service to potential wireless customers, so Such customers will typically not receive cellular coverage from metropolitan area cellular coverage sites 1302. Accordingly, the new subscriber receives access to the wireless communication service and can further communicate with wireless customers within the metropolitan area cellular coverage site 1302 .

Referring to Figure 14, another telecommunication system, generally designated 1400, is shown. As shown in FIG. 14 , system 1400 includes a DMA server 1402 that can be connected to a plurality of BTSs 1404 . Each BTS 1404 may provide cellular coverage for one or more mobile communication devices 1406 . FIG. 14 also shows that the DMA server 1402 may include a data network connection 1408 that provides a backhaul connection to the PSTN 1410. In an embodiment, the data network connection may be an E1 connection, a TI connection, a cable connection, a microwave connection, or a satellite connection. Furthermore, the system 1400 shown in FIG. 14 may be deployed using CDMA, IS-95, CDMA1X, GSM/GPRS, W-CDMA, or other industry standard technologies.

Using a single backhaul connection greatly reduces the costs associated with wireless communication networks. Furthermore, the system 1400 described in Figure 14 can be deployed relatively quickly and maintained remotely. Furthermore, by including OAMP module 540 ( FIG. 5 ) and AAA module 528 ( FIG. 5 ), user accounts may be managed locally and billing performed locally, ie, within DMA server 1402 . Furthermore, as the number of users increases, the scale of the system is adaptively increased, for example, by adding DMA servers, corresponding BTSs and appropriate connections.

Figure 15 shows the built-in telecommunication network, generally designated 1500. Figure 15 shows a building 1502, eg, an office building, a commercial building, a house, or the like. Goodbye installation of a corporate local area network (LAN) 1504 within the host 1502 . Connect Micro BTS1506 to corporate LAN1504. Additionally, a voicemail server 1508 and a plurality of enterprise service servers 1510 are connected to the enterprise LAN 1504 . In an exemplary non-limiting embodiment, the enterprise service server 1510 may include: a dynamic host configuration protocol (DHCP) server, a radius server, a domain name server (DNS), and the like. As shown in FIG. 15 , multiple phones 1512 (eg, IP desk phones) may be connected to corporate LAN 1504 .

Figure 15 also shows that an office DMA server 1514 can be connected to the corporate LAN 1504. An office DMA server 1514 may also be connected to PSTN 1516 , which in turn may be connected to cellular voice and data network 1518 . Enterprise LAN 1504 may also be connected to cellular voice and data network 1518 via Internet Protocol (IP) network 1520 . Signaling System 7 (SS7) network 1522 may be connected to cellular voice and data network 1518 and IP network 1520 . FIG. 15 also shows: gateway 1524 between SS7 network 1522 and IP network 1520 and firewall 1526 between enterprise LAN 1504 and IP network 1520 . FIG. 15 shows wireless communication device 1528 in communication with cellular voice and data network 1518 and micro BTS 1506 .

Referring to Figure 16, a mobile in-field telecommunications system, generally designated 1600, is shown. As shown, system 1600 includes a plurality of mobile cellular coverage sites 1602 . Each mobile cellular coverage site 1602 includes a vehicle 1604 housing an on-site DMA server 1606 . In addition, a BTS 1608 is located within each vehicle 1604, and the BTS 1608 may be directly physically connected to the on-site DMA server 1606 (eg, via a wire or cables therebetween). On-site DMA server 1606 and BTS 1608 may be removably installed within vehicle 1604 , or on-site DMA server 1606 and BTS 1608 may be permanently affixed in vehicle 1604 . Figure 16 also notes that each BTS 1608 may include an antenna 1610 designed to communicate with a mobile communication device. Additionally, each live DMA server 1606 includes an antenna 1612 . In an exemplary, non-limiting embodiment, on-site DMA servers 1606 may communicate with each other via antennas 1612 wirelessly (eg, via 802.11a, 802.11b, microwave, or other wireless links).

Mobile cellular coverage sites 1602 may be deployed as temporary webs that provide cellular coverage to multiple mobile communication devices, such as those carried by soldiers during warfare. The mobile on-site communication system 1600 can be canceled, moved and redeployed as necessary. Additionally, the system may include a wireless connection (eg, 802.11a, 802.11b, microwave) to the PSTN 1614.

Referring to FIG. 17 , another telecommunications system is shown and generally designated 1700 . As shown in FIG. 17 , system 1700 includes DMA server 1702 connected to BTS 1704 . Next, connect the BTS 1704 to the antenna 1706 . FIG. 17 also shows that the first satellite transceiver 1708 is also connected to the DMA server 1702 . The first satellite transceiver 1708 communicates with the second satellite transceiver 1710 via a satellite 1712 . Additionally, the second satellite transceiver 1710 includes a data network connection 1714, eg, a T1 connection or an E1 connection. Satellite transceivers 1708 , 1710 and satellite 1712 may provide a backhaul connection to DMA server 1702 . Alternatively, satellite transceivers 1708, 1710 and satellite 1712 may connect DMA server 1702 to additional DMA servers (not shown).

FIG. 18 shows another telecommunications system, generally designated 1800 . As shown in FIG. 18 , the system includes a DMA 1802 connected to a first satellite transceiver 1804 . Additionally, DMA 1802 includes a primary network connection 1806 (eg, a T1 connection or an E1 connection) and a secondary network connection 1808 (eg, an IP connection). FIG. 18 shows that a first satellite transceiver 1804 communicates with a second satellite transceiver 1810 and a third satellite transceiver 1812 via a satellite 1814 . Each of the second satellite transceiver 1810 and the third satellite transceiver 1812 is connected to an interworking unit (IWU) 1816 via a data network connection 1818 (eg, an IP connection). Each IWU 1816 is connected to a BTS 1820 which in turn is connected to an antenna 1822 . Satellite transceivers 1804 , 1810 , 1812 provide IP network extension to DMA server 1802 . Additionally, in the deployment shown in FIG. 18 , DMA server 1802 may act as a centralized microswitch for handling calls received at antenna 1822 and transmitted via second satellite transceiver 1810 and third satellite transceiver 1812 .

Referring to Fig. 19, another telecommunication system, generally designated 1900, is shown. As shown, system 1900 includes a DMA server 1902 having multiple network connections 1904 . Additionally, a DMA server 1902 may be connected to multiple IWUs 1906 . In an exemplary, non-limiting embodiment, the DMA server 1902 may be connected to each IWU 1906 via a secondary network connection 1908 such as a Category 5 (Cat5) cable connection, a microwave connection, or a WLAN connection. Additionally, each IWU 1906 is connected to a BTS 1910 , which in turn connects each BTS 1910 to an antenna 1912 . Each BTS 1910 may be a 3-sector BTS. In the deployment shown in FIG. 19 , DMA server 1902 may act as a centralized microswitch that may be used to handle telephony traffic received at antenna 1912 .

FIG. 20 shows another embodiment of a communication system, labeled 2000 . As shown, system 2000 includes an aircraft 2002 with a DMA server 2004 installed therein. DMA server 2004 is coupled to BTS 2006 and first satellite transceiver 2008 as shown. FIG. 20 also shows a mobile communication device 2010 within the aircraft 2002 . Mobile communication device 2010 may be wireless communication within BTS 2006 .

In a particular embodiment, the first satellite transceiver 2008 can communicate with the second satellite transceiver 2012 via the satellite 2014 . As shown, a second satellite transceiver 2012 can be connected to a ground server network 2016 (e.g., a DMA server gateway), which can provide access to an operations and management platform (OMP) 2018, a call detail record (CDR) 2020, and a visited location Connection of Register Gateway (VLR-GW) 2022. OMP2018, CDR2020 and VLR-GW2022 can be separated from or incorporated into server gateway 2016. FIG. 20 also shows that the server gateway 2016 can be connected to a first mobile switching center (MSC) 2024 , which is coupled to a second MSC 2006 .

Thus, the system 2000 shown in FIG. 20 may allow a device in an aircraft 2002 to communicate with a ground-based phone. For example, mobile communication device 2010 may communicate with BTS 2006 , which in turn may communicate with first satellite transceiver 2008 via DMA server 2004 . Additionally, the first satellite transceiver 2008 can transmit the call via the second satellite transceiver 2012 and the satellite 2014 to a ground-based communication system.

Figure 20 shows a single aircraft, however, multiple aircraft may be configured as described herein to provide communication from multiple aircraft to ground-based phones. Additionally, aircraft-to-aircraft communications may be provided, and furthermore, system 2000 may include other air vehicles, such as small aircraft.

Another embodiment of a communication system is shown in FIG. 21 , labeled 2100 . As shown, the system 2100 includes a ship 2102 on which a DMA server 2104 is installed. DMA server 2104 is coupled to BTS 2106 and first satellite transceiver 2108 as shown. FIG. 21 also shows a mobile communication device 2110 within the ship 2102 . Mobile communication device 2110 may be wireless communication within BTS 2106 .

In a particular embodiment, the first satellite transceiver 2108 can communicate with the second satellite transceiver 2112 via a satellite 2114 . As shown, a second satellite transceiver 2112 can be connected to a ground server network 2116 (e.g., a DMA server gateway), which can provide access to an operations and management platform (OMP) 2118, a call detail record (CDR) 2120, and a visited location Connection of Register Gateway (VLR-GW) 2122. OMP 2118, CDR 2120 and VLR-GW 2122 may be separate from or incorporated into server gateway 2116. FIG. 21 also shows that a server gateway 2116 can be connected to a first mobile switching center (MSC) 2124 , which is coupled to a second MSC 2106 .

Thus, the system shown in FIG. 21 may allow for communication within the ship 2102 with ground-based phones. For example, mobile communication device 2110 may communicate with BTS 2106 , which in turn may communicate with first satellite transceiver 2108 via DMA server 2104 . In addition, the first satellite transceiver 2108 can transmit the call to a ground-based communication system via the second satellite transceiver 2112 and the satellite 2114

Figure 21 shows a single ship, however, multiple ships may be configured as described herein to provide communication from multiple ships to ground-based phones. Additionally, ship to Luanchuan communications may be provided, and system 2100 may include other waterborne vehicles.

Referring to Figure 22, there is shown a method of deploying a distributed management architecture server, beginning at block 2200, wherein, during deployment, subsequent steps are performed. At block 2202, the DMA server is moved to a desired location close to the BTS. Going to block 2204, the DMA server is turned on. For example, if the DMA server is that shown in Figure 1, the latch is unlocked and the cover is pivoted to the open position. Proceeding to block 2206, a physical connection is established between the DMA server and the BTS, eg, coupling the BTS to the DMA server via a cable.

Continuing to block 2208, the DMA server is activated, eg, powered. At block 2210, a network connection is established with another remote DMA server. In a particular embodiment, the network connection is a peer-to-peer connection between DMA servers. Going to block 2212, the DMA server software within the DMA server is activated. Thereafter, at decision step 2214, it is determined whether the system is operational. The determination may be performed by the DMA server (eg, through a self-diagnostic program or module within the DMA server). Alternatively, the decision step may be determined manually by a skilled person. If the system is not operational, then at block 2216 a system check is performed. In certain embodiments, the system check performed at block 2216 is performed by a self-diagnostic program or module within the DMA server. On the other hand, a technician can perform a system check. After the system check, the logic then returns to decision step 2214 and continues to operate as above. In decision step 2214, if the system is operational, the method proceeds to block 2218 and call transfer is allowed. The method then stops at state 2220.

Referring to FIG. 23, a method of deploying a distributed management architecture server is shown, beginning at block 2300, wherein the direct physical connection between the first DMA server and the base transceiver station is broken. At block 2302, the first DMA server is removed. Proceeding to block 2304, the second DMA server is moved to a location substantially closer to the base transceiver station. At block 2306, a second DMA server is turned on. For example, if the DMA server is that shown in Figure 1, the latch is unlocked and the cover is pivoted to the open position. Next, at block 2308, a direct physical connection is established between the second DMA server and the base transceiver station.

Continuing to block 2310, a second DMA server is activated. At block 2312, a network connection is established between the second DMA server and another remote DMA server. In a particular embodiment, the network connection is a peer-to-peer connection between DMA servers. Furthermore, in certain embodiments, the peer-to-peer connection is established via a private IP network. At block 2314, the DMA server software within the second DMA server is activated.

Proceeding to step 2316, it is determined whether the system is operational. The determination may be performed by the DMA server (eg, through a self-diagnostic program or module within the second DMA server). Alternatively, the decision step may be determined manually by a skilled person. If the system is not operational, then at block 2318 a system check is performed. In certain embodiments, the system check performed at block 2318 is performed by a self-diagnostic program or module within the second DMA server. On the other hand, a technician can perform a system check. After the system check, the logic then returns to decision step 2316 and continues to operate as above. At decision step 2316, if the system is operational, the method proceeds to block 2320 and call transfer via the second server is allowed. The method then stops at state 2322.

With the configuration of the above structures, the present invention discloses a flexible telecommunications device (i.e., DMA server 406 (FIG. 4)) that is distributed-associated, i.e., it can be deployed between existing cellular or other networks. operate independently and seamlessly. Furthermore, the DMA server 406 can be integrated with any third-party base station in a virtual fashion. DMA server 406 is operable over a variety of air interfaces, including CDMAIS-95, CDMA1X, CDMAEVDO, GSM, GPRS, W-CDMA, 802.11 (Wi-fi), 802.16 (Wi-fi), and the like. In addition, DMA server 406 may provide integrated prepaid billing, OAMP, network management, and AAA functions. Additionally, DMA server 406 may include a Java-based user interface and feature configuration system. Additionally, the DMA server 406 can provide real-time call metering, call detail record (CDR) generation, and real-time call provisioning. DMA server 406 can be implemented in a relatively small footprint and has relatively low power requirements. Furthermore, DMA server 406 can be implemented using less expensive and widely available computer equipment.

With the deployment of one or more of the above configurations, the system provides mobile-to-landline calls from mobile handsets within the cellular coverage area of a DMA server. In addition, mobile-to-landline calls can be made from mobile handsets roaming into DMA coverage areas. Mobile-to-mobile calls can be made from local/roaming handsets to DMA handsets and vice versa. In addition, mobile-to-IP calls and IP-to-mobile calls can be implemented from within the DMA server coverage area. IP-to-IP calls can be made from any DMA handset to any IP phone. In addition, IP-to-landline calls and landline-to-IP calls can be made from any DMA handset to any phone. In addition, landline-to-mobile calls can be made to DMA handsets.

A system as described above may support call forwarding, call waiting, 3-way calling caller ID, voice mail and mobile-to-mobile SMS services, ie, text messaging. In addition, the system as described above can support broadcast SMS service, mobile-to-road high-speed IP data (1X or GPRS) service, and mobile-to-mobile high-speed IP data (1X or GPRS) service. Additionally, a system as described above may provide IP-PBX capabilities.

Additionally, one or more of the illustrated systems can provide IP transfers between distributed components (eg, DMA server 406 (FIG. 4)). Packet backhaul from BTS to RAN may be provided. Furthermore, the control logic within DMA server 406 (FIG. 4) may be distributed and associative. Linked systems can be redundant, self-healing, self-organizing, and upgradeable. The distributed system can be "snap-together," i.e., a DMA server 406 (FIG. 4) can be linked to a previously deployed DMA server 406 (FIG. 4) in order to widen or otherwise extend cellular coverage . Also, distributed systems can be decentralized to avoid single points of failure.

One or more of the systems described above may also provide soft call handover or softer call handover on the same frequency interface. Additionally, soft call handover may be provided on different systems. Furthermore, the DMA based system can operate independently from the billing system and CDR generation provided by the DMA server. Alternatively, the system can use the SS7 network to pass the CDRs to a central switch for integrated billing and operations over the existing network.

The above-disclosed subject matter is to be considered illustrative rather than restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the invention. Accordingly, to the maximum extent permitted by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the appended claims and their equivalents, rather than being restricted or limited by the foregoing detailed description.

Claims (16)

1. A communication system comprising: A first distributed mobile architecture server comprising: a first computer-readable medium; a first mobile switching center module embedding said first computer readable medium; a first base station controller module embedded in said first computer readable medium; and a first call detail record (CDR) generating module embedded in the first computer-readable medium; wherein said first distributed mobility architecture server is directly physically connected to the first wireless transceiver; and A second distributed mobile architecture server comprising: a second computer readable medium; a second mobile switching center module embedded in said second computer readable medium; a second base station controller module embedded in said second computer readable medium; a second call detail record (CDR) generation module embedded in said second computer-readable medium; and a module allowing group calls between four or more mobile communication devices, wherein said module is embedded in said second computer readable medium, wherein the second distributed mobile architecture server is directly physically connected to the second wireless transceiver; Wherein said first distributed mobile architecture server is operable to transmit telephony traffic received at the first wireless transceiver to said second distributed mobile architecture server over a peer-to-peer connection. 2. The system of claim 1, wherein the first distributed mobility architecture server is operable to, when the first distributed mobility architecture server moves from a first location to a second location, Telephony traffic received at a wireless transceiver is transmitted to said second distributed mobile architecture server over a peer-to-peer connection. 3. The system of claim 2, wherein the first distributed mobility architecture server is operable to, when the second distributed mobility architecture server moves from a third location to a fourth location, Telephony traffic received at a wireless transceiver is transmitted to said second distributed mobile architecture server over a peer-to-peer connection. 4. The system of claim 1, wherein the first distributed mobility architecture server stores data from a first home locator resource and data from a first visited locator resource. 5. The system of claim 4, wherein the first distributed mobility architecture server further comprises: a first operations, administration, maintenance and provisioning (OAMP) module embedded in said first computer readable medium, a first authentication, authorization, and accounting (AAA) module embedded in said first computer-readable medium; a first packet data server node (PDSN) gateway embedded in said first computer readable medium; and A first Gateway General Packet Radio Service (GPRS) Support Node (GGSN) embedded in the first computer-readable medium. 6. The system of claim 1, wherein the second distributed mobility architecture server stores data from a second home locator resource and data from a second visited locator resource. 7. The system of claim 6, wherein the second distributed mobility architecture server further comprises: a second operations, administration, maintenance and provisioning (OAMP) module embedded in said second computer readable medium, a second authentication, authorization, and accounting (AAA) module embedded in said second computer-readable medium; a second packet data server node (PDSN) gateway embedded in said second computer-readable medium; and A second Gateway General Packet Radio Service (GPRS) Support Node (GGSN) embedded in the second computer-readable medium. 8. The system of claim 1, wherein the first distributed mobility architecture server further comprises a first gateway to a public switched telephone network. 9. The system of claim 8, wherein the first distributed mobility architecture server further comprises a first media gateway. 10. The system of claim 9, wherein the first distributed mobility architecture server further comprises a first packet data server node gateway and a first gateway GPRS node. 11. The system of claim 10, wherein the first distributed mobility architecture server further comprises a first Signaling System 7 (SS7) gateway. 12. The system of claim 11, wherein the first distributed mobility architecture server further comprises a first session initiation protocol gateway. 13. The system of claim 1 , wherein said first base station controller module embedded in said first computer readable medium of said first distributed mobility architecture server comprises a first cellular radio network controller . 14. The system of claim 13, wherein said first base station controller module embedded in said first computer readable medium of said first distributed mobility architecture server further comprises a first cellular selection/distribution unit. 15. The system of claim 14, wherein the first base station controller module embedded in the first computer readable medium of the first distributed mobility architecture server further comprises a first call protocol controller. 16. The system of claim 15, wherein the first call protocol controller is in communication with a first wireless transceiver of the first distributed mobility architecture server.