HK1188070A - System, method, and device for providing communications using a distributed mobile architecture - Google Patents

Description

System, method and apparatus for providing communications using a distributed mobile architecture

The application is a divisional application of an invention patent application with the application date of 2005, month 10 and 4, and the application number of 200580033404.X, and the invention name of a system, a method and a device for providing communication by using a distributed mobile architecture.

Technical Field

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

Background

Access to basic telephony services is particularly important for rural and isolated communities. Telephone access allows small-scale businesses, co-workers and farmers to obtain accurate information about the market price of their products and to access regional and national markets. Access also reduces the cost of transportation and supports the local travel industry. By bringing the market to people via telecommunications, rather than forcing people to move around to search for the market, urban migrants are reduced and more income and employment potential is generated in rural areas.

Unfortunately, the rapid development of telecommunications in the last decade has not alleviated the imbalance between urban and rural communities. For example, asian regions have an average imbalance ratio of telephone penetration in excess of 10 to 1, typically as high as 20 to 1.2. This means that for countries in the urban market (e.g., india and pakistan) with a penetration of four (4) telephone lines per one hundred (100) residents, it has a country penetration of less than 0.2 telephone lines per one hundred (100) residents. This situation is more severe in most african countries and in some parts of latin america. By comparison, the average revenue level between urban and rural residents of the developing world is typically less than 4 to 1 unbalanced.

Current telephone systems are expensive to deploy. For example, the cost of a typical cellular system including a Mobile Switching Center (MSC), a Base Station Controller (BSC), and a home location register/visitor location register (HLR/VLR) can exceed $ 2 million. Furthermore, such a system may require a minimum of 1 million users in order to be economically viable. 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 the devices (e.g., 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 landlines may be too high for certain rural areas.

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

Drawings

The invention is characterised by the features set forth in the appended claims. However, other features are described in the following detailed description, taken in conjunction with the accompanying drawings, in which:

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

FIG. 2 is a diagram of an alternative embodiment of a distributed management architecture server having a second exemplary form factor;

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

FIG. 4 is a diagram of a distributed association communications system;

FIG. 5 is a block diagram of a distributed management architecture server;

FIG. 6 is a flow diagram illustrating the operational logic of a distributed management architecture server;

FIG. 7 is a flow diagram illustrating call handoff logic for a distributed management architecture server;

FIG. 8 is a flow diagram illustrating group call logic for a distributed management architecture server;

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

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

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

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

FIG. 13 is a diagram of a communication system in which a distributed management architecture server may be deployed to cover the edges of a city around an existing network;

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

FIG. 15 is a diagram of a built-in communication system in which a distributed management architecture server may be deployed;

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

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

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

FIG. 19 is a diagram of a communication system in which a single distributed management architecture server may be connected to multiple base transceiver stations;

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

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

FIG. 22 is a flow diagram illustrating a method of deploying a distributed management architecture server; and

FIG. 23 is a flow chart illustrating a method of replacing a distributed management architecture server.

Detailed Description

Referring to FIG. 1, a Distributed Management Architecture (DMA) is shown and is generally designated 100. As shown in fig. 1, the DMA server 100 includes a base 102 and a lid 104. As shown, the lid 104 is attached to the base by a first lid hinge 106 and a second lid hinge 108. In a particular embodiment, 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 DMB server 100 may be substantially shaped like a box or briefcase.

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

Fig. 1 also indicates: the base 102 of the DMA server 100 is formed with vents 124 to allow air exchange with the interior of the base 102 of the DMA server 100 and to facilitate cooling of the electronic components of the DMA server 100 housed within the base 102. Further, the base 102 of the DMA server 100 includes a handle 126 attached to the base 102 via a first handle hinge 128 and a second handle hinge 130. The base 102 also includes a pair of latch engagement recesses 132.

As shown in fig. 1, the cover 104 includes a flat panel display 134 incorporated therein. When the cover 104 is closed, the display 134 is adjacent the keypad 116. Further, when the cover 104 is closed, the cover 104 and the base 102 cooperate to protect the display 134, the keyboard 116, the mouse 118, and the buttons 120, 122. Fig. 1 also shows a latch 136 incorporated into the lid 104. When the lid 104 is closed, the latch 136 may 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 cover 104. The antenna 138 may be extended during operation and retracted when the DMA server 100 is not operating.

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

In a particular embodiment, the DMA server 100 is relatively robust. Specifically, the DMA server 100 may operate in a temperature range from minus 20 degrees Celsius to plus 55 degrees Celsius (-20 ℃ to 55 ℃). Further, the DMA server 100 is sufficiently shock resistant and can withstand one meter drop. Further, the DMA server 100 is substantially resistant to inclement weather, substantially resistant to dust, and substantially resistant to sand. The DMA server 100 is portable and may be installed in a vehicle or carry the DMA server 100 like a briefcase. Further, multiple DMA servers 100 may be deployed as described herein.

Fig. 2 illustrates 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, the cover 204 being coupled to the base 202 via a plurality of fasteners 206 (e.g., a plurality of screws). In addition, the DMA server 200 has a length 208, a width 210, and a height 212. In addition, the base 202 of the DMA server 200 includes a first vent 214, a second vent 216, and a third vent 218. In certain embodiments, the vents 214, 216, 218 allow air exchange with the interior of the base 202 of the DMA server 200 and facilitate cooling of the electronic components of the DMA server 200 housed within the base 202. As shown in fig. 2, the DMA server 200 includes an access window 220. One or more interfaces 222 (e.g., cables) may be accessed via the access window 220 and the one or more interfaces 222 may be coupled to a Base Transceiver Station (BTS) during deployment of the DMA server 200. As shown in fig. 2, the DMA server 200 may be installed within a vehicle 224. Further, 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. Further, in a particular embodiment, the width 210 of the base 202 is 45.0 centimeters. Further, in a particular embodiment, the width 212 of the base 202 is 34.0 centimeters. Thus, the DMA server 200 has a total volume of about 140760 cubic centimeters and a coverage area of about 4140 square centimeters. Further, in a particular embodiment, the DMA server 200 weighs approximately 48 kilograms (kg). Thus, heavy in certain embodiments, the DMA server 100 has a total volume of less than 150000 cubic centimeters, a coverage area of less than 5000 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, the DMA server 300 includes a housing 302 having a length 304, a width 306, and a height 308. Further, the housing 302 is formed with a first vent hole 310 and a second vent hole 312. In a particular embodiment, the vents 310, 312 allow air exchange with the interior of the housing 302 of the DMA server 300 and facilitate cooling of the electronic components of the DMA server 300 within the housing 302.

As shown in fig. 3, at least one side of the housing 302 is formed with ribs 314 to allow the DMA server 300 to slide into a server rack (not shown). Further, the DMA server 300 includes a clip 316 that is coupled to the housing 302 via a fastener (e.g., a bolt). The clip 316 may be engaged with a server rack (not shown) to prevent the 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. Further, in a particular embodiment, the width 306 of the housing 302 is approximately 48.2 centimeters. Further, in a particular embodiment, the height 308 of the housing 302 is approximately 4.3 centimeters. Thus, the DMA server 300 has a total volume of about 15756.5 cubic centimeters and a coverage area of about 3672.9 square centimeters. Further, in a particular embodiment, the DMA server 300 weighs approximately 17.7 kilograms (kg). Further, in particular embodiments, the DMA server 300 is stackable in order to support various volume requirements. Thus, in a particular embodiment, the DMA server 100 has a total volume of less than 16000 cubic centimeters, a coverage area of less than 4000 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 is generally designated 400. As shown in fig. 4, the 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 the BTS is a 3-segment BTS. Fig. 4 also indicates: 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, for example, by a cable or cable 408. Further, in the illustrated embodiment, the 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. Thus, a peer-to-peer connection 412 exists between each DMA server 406 in the system 400. As described in detail below, the DMA server 406 may handle telephony traffic transmitted at each antenna 404. For example, the DMA server 406 may exchange and route calls received via each antenna 404. Further, the DMA servers 406 can hand off calls to each other as the communication devices move around the cellular coverage site 402 and between the cellular coverage sites 402. The DMA servers 406 may communicate with each other via the IP network 410 and may further send calls to each other via the IP network 410. It should be understood that: more than four cellular coverage sites 402 may be included in the system, and the inclusion of only four cellular coverage sites 402 in fig. 4 is merely for purposes of clarity and ease of explanation.

Within the distributed associative telecommunication system 400, the control logic may be distributed and decentralized. Moreover, 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 are powered down, fail, or otherwise inoperable, telephony traffic handled by the inoperable DMA server 406 may be rerouted to one of the remaining operable DMA servers 406. Further, user data stored in a database (e.g., a Home Locator Resource (HLR) or a Visitor Locator Resource (VLR)) may be distributed equally and thoroughly among all DMA servers 406. It can also be appreciated that: as the demand for users increases, new cellular coverage sites can be easily added to the system 400. In particular, the 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 (e.g., one of the DMA servers 406 described in conjunction with FIG. 4). Additionally, any of the DMA servers 100, 200, 300 shown in FIGS. 1, 2, and 3 may include the components shown in FIG. 5 and described in detail herein.

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

As shown in fig. 5, the DMA server 406 may include a Mobile Switching Center (MSC) module 506 and a Base Station Controller (BSC) module 508 embedded within the computer-readable medium 500. In an exemplary, non-limiting embodiment, the MSC module 506 may include a Gatekeeper (GK)510 connected to several gateways. For example, a Circuit Gateway (CGW)512 may be connected to the GK510, and the circuit gateway 512 may provide a connection to an integrated services digital network/public switched telephone network (ISDN/PSTN) interface 514. CGW512 may provide a circuit for switch to packet data conversion. In an exemplary, non-limiting embodiment, the PSTN portion of the ISDN/PSTN interface 514 may be an inter-office interface using the Bellcore industry standard ISDN user part (ISUP) that carries signaling over a 7 signaling system (SS7) link set. Furthermore, the voice trunks on the interface may be time slots on the 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) kingdom 518 may be connected to the GK 510. The PDSN gateway 516 and the SIP gateway 518 may provide connectivity to an Internet Protocol (IP) interface 520. In addition, the PDSN gateway 516 or the GGSN can use Generic Routing Encapsulation (GRE) to establish a reverse tunnel with the PDSN or GGSN gateway 516. 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 an SS7 gateway 522 that provides connectivity to ANSI-41 and GSM Mobile Application Part (MAP) interface 524. In particular embodiments, the ANSI-41 interface may be an SS7TCAP/SCCP interface on the same SS7 link set used for ISUP signaling. The SS7 point code may be used to identify the DMA server 406 in an ANSI-41 network. The ANSI-41 interface may be used for roaming registration. Further, in an exemplary, non-limiting embodiment, the GSM MAP interface may be an SS7TCAP/SCCP interface on the same SS7 link set used for ISUP signaling. It can be appreciated that: there are different MAP protocols from MAP/B to MAP/I, but in the illustrated embodiment, the different MAP/x protocols are not stacked-the protocols are used independently.

As shown in fig. 5, a media gateway 526 may also be coupled to the GK 510. In an exemplary, non-limiting embodiment, the media gateway 526 may include: a cellular transcoder, one or more intranet gateways, a teleconferencing bridge, and a group call function. Further, an authentication, authorization, and accounting (AAA) module 528 may be coupled to the GK 510. In an exemplary, non-limiting embodiment, there are three authentication management levels. The highest level is for management, the middle level for operation, and the lowest level for general users. The functionality of the AAA module 528 may be included in the user level.

In an exemplary, non-limiting embodiment, the GK510 may act as an AAA server and a feather server to support advanced supplementary services, short message services, and the like. Further, GK510 may act as a call manager and may support ISUP and PSTN functionality calls. In addition, GK510 may serve as a signal gateway, e.g., IP to SS7 interworking, ISUP, GSM MAP or ANSI-41 to PSTN, and ANSI-42/GSM. The GK510 may also act 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 CPC534 may be connected to multiple Base Transceiver Stations (BTSs) 536. In particular, the DMA server 406 includes a BTS interface 538 at the CPC534, which may be physically connected directly to the BTS 536. The CRNC530 may provide cellular radio resource management and cellular call control. The CSDUs 532 may provide Fundamental Channel (FCH) soft handoff and allocation, Link Access Control (LAC) processing for in-band signaling, Multiplexer (MUX) functionality, and centralized power control. Further, the CPC534 may convert T1 or E1 messages or ATM interfaces into data packet messages. In particular embodiments, each BTS536 supports signals and traffic up to the front point of CPC534 (e.g., up to BTS interface 538). Further, in particular embodiments, CRNC530, CPC534, CSDU532, and OAMP540 may perform one or more functions of a legacy Base Station Controller (BSC).

In an exemplary, non-limiting embodiment, BTS interface 538 may be the E1 OR IS-95A OR IS-2000 interface over ATM, OR BTS interface 538 may be a GSM BTS interface using MAP OR customized applications for Mobile networks enhanced logic (CAMEL). In the illustrated embodiment, the CPC534 may be connected to one or more BTSs 536. Fig. 5 also shows: the BSC module 508 includes an operation, administration, maintenance and assignment (OAMP) module 540. In an exemplary, non-limiting embodiment, the 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. The OAMP module 540 may include a software agent assigned to each component within the DMA server 406. The agents independently monitor their respective components. Further, each agent may provision its respective component.

Referring to FIG. 6, an exemplary, non-limiting embodiment of a flow diagram is provided to illustrate the operating logic of the DMA server 406 (FIG. 4). The operating logic begins at block 600 with a functional loop in which, during operation, subsequent steps are performed. At step 602, a call is received, for example, at antenna 404 (FIG. 4) in communication with DMA server 406 (FIG. 4). Next, at decision step 604, a determination is made as to whether the call is local, i.e., 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 exchanged at a local DMA server (i.e., a DMA server within the cellular coverage site receiving the call). The call is then connected from the first mobile communication device originating the call to the second mobile communication device via the local DMA server at block 608. 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 where the call was received. Thereafter, at step 612, the 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 connecting the call 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 may be monitored, the location of the second mobile communication device receiving the call may be monitored, the DMA server handling the call may be monitored, other DMAs through which the call is connected may be monitored, and the connection through which the call is sent (such as a peer-to-peer IP network connection) may be monitored. Proceeding to decision step 616, a determination is made as to whether the first mobile device or the second mobile device involved in the call is roaming, i.e., moving between cellular coverage sites provided by the respective antennas. If so, the logic moves to block 618 where the call at the roaming mobile communication device is automatically handed off to the new DMA server and associated antenna at the new cellular coverage site. If no mobile communication device involved in the call is roaming, the logic flows to decision step 620.

At decision step 620, a determination is made as to 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 one or more different DMA servers that are still in operation. Thereafter, the logic flows to decision step 624. Decision step 624 may also be reached if it is determined at decision step 620 that no DMA servers have failed. At decision step 624, a determination is made whether the call has ended. If not, the logic moves to block 626 and the connection or connections through which the call is established are maintained. Otherwise, if the call has ended, the logic moves to block 628 and the peer-to-peer connection or connections through which the call is established are terminated and the logic ends at state 630.

Fig. 7 shows a flowchart illustrating call handoff logic that may be performed by the DMA server 406 (fig. 4) in order to handoff a call or subscriber service connection between a first BTS and a second BTS as the mobile communication device moves between cellular coverage zones. The logic begins in block 700 with a loop in which, when a 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, a determination is made as to whether the mobile communication device is about to move from a first cellular coverage site provided by a first BTS to a second cellular coverage site provided by a second BTS. If not, the logic flows to decision step 706, where a determination is made as to whether the call has terminated. If the call is terminated, the logic ends at state 708. Conversely, if the call is not terminated, the logic returns to block 702 and continues as described above.

Returning to decision step 704, if the user is about to move from a first cellular coverage site provided by a first BTS to a second cellular coverage site provided by a second BTS, the logic proceeds to decision step 710. At decision step 710, it is determined whether the second BTS is connected locally, i.e., to the same DMA server as the first BTS. If so, the logic moves to block 712 and the DMA server hands off the call (soft handoff) or user service connection from a first BTS connected to the DMA server to a second BTS connected to the same DMA server. Otherwise, if the second BTS is not local, the logic continues to block 714 where the DMA server hands off 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 described above.

Fig. 8 shows an exemplary, non-limiting embodiment of a method for illustrating group call logic that may be executed at the DMA server 406 (fig. 4) to provide a group call between several mobile communication devices and PSTN/ISDN users. At block 800, a loop is entered in which, during operation, the following steps are performed. At decision step 802, a determination is made 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 allows ordinary calls, e.g., two-way calls, three-way conference calls, etc. The logic then ends at state 806.

At 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), the logic moves to block 808 and a group call is allowed between all participants with full duplex communication capabilities. Next, at decision step 810, a determination is made as to whether one or more participants are disconnected. If so, at decision block 812, the disconnected participant or participants exit the group call. At block 814, the full duplex call is maintained among the remaining group call participants. Returning to decision step 810, if no participants are disconnected, the logic proceeds to decision step 816, where a determination is made as to whether a new participant is connected to the group call. Decision step 816 is also reached from block 814 above.

At decision step 816, if a new participant enters the group call, the new participant is allowed to connect to the group call and may 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 enter the group call. At decision step 820, a determination is made whether all participants have disconnected from the group call. If not, the logic returns to block 808 and continues as described above. Conversely, if all participants have disconnected from the group call, the logic moves to block 822, where the group call is terminated, and the logic then ends at state 806.

Referring now to fig. 9, an exemplary, non-limiting embodiment of a telecommunications system is shown and is generally designated 900. As shown, the system includes one or more DMA servers 902 connected to a central MSC904 of a wireless carrier (carrier). The DMA server 902 may be connected to the MSC904 via an E1CCS (g.703, G732) connection or any other application connection. Instead, the MSC904 is connected to a Code Division Multiple Access (CDMA) network 906. Fig. 9 also shows: the DMA server 902 may be connected to an independent carrier's Switch Transfer Point (STP) 908. As shown, DMA server 902 may be connected to STP908 via an IS-41+ IS-880(DS0) connection or an ISUP ITU U N7 connection.

As further shown in fig. 9, STP908 can be coupled to a Short Message Service (SMS) server 910 to provide text messaging capability to mobile communication devices using system 900 shown in fig. 9. In addition, STP908 may be coupled to Home Location Register (HLR)912, prepaid wireless server 914, and international roaming network 916 to provide prepaid service and roaming between countries. FIG. 9 shows: the DMA server 902 may be connected to the PTSN918 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 is generally designated 1000. As shown in fig. 10, the system 1000 includes a DMA server 1002 that is connected to a BTS 1004. BTS1004, in turn, is connected to an antenna 1006. Antenna 1006 provides cellular coverage for one or more users 1008 within transmission range of antenna 1006. Fig. 10 shows: the system 1000 may also include a data network connection 1010 from the DMA server 1002. The data network connection 1010 may connect the DMA server 1002 to the PSTN via an ISUP/ISDN signaling connection over a set of SS7 links or a T1/E1 wireless connection. Further, 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. The DMA server 1002 may advantageously employ existing architectures for cellular and SMS data services.

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

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

Fig. 13 illustrates another telecommunications system, generally designated 1300. As shown, system 1300 includes: urban area coverage site 1302 and urban fringe/nearby village coverage site 1304. In an exemplary, non-limiting embodiment, the urban area coverage site 1302 includes a first MSC/BSC center 1306 that is connected to a second MSC/BSC center 1308. Further, a first representative BTS1310 and a second representative BTS1312 are connected to the first MSC/BSC center 1306. The particular deployment of the apparatus is configured to provide sufficient cellular coverage to mobile communication devices within the urban area coverage site 1302.

As shown in fig. 13, a city edge/nearby village coverage site 1304 includes a DMA server 1314 having a plurality of connected BTSs 1316. The DMA server 1314 may provide for call handoffs between BTSs 1316 and may locally switch calls made between BTSs 1316. However, the DMA server 1314 within the urban fringe/nearby village coverage site 1304 can also connect telephone traffic to the first MSC/BSC center 1306 within the urban area coverage site 1302 via a data network connection 1318. In an 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. The deployment of the DAM server 1314 in a location such as that described above (i.e., at the edge of a city or nearby village) and the connection of the DMA server 1314 to the MSC/BSC center 1306 in the urban area can serve potential wireless customers who typically will not receive cellular coverage from the urban area cellular coverage site 1302. Thus, new users receive access to wireless communication services and may further communicate with wireless customers within the metropolitan area cellular coverage site 1302.

Referring to fig. 14, another telecommunications system is shown, designated 1400. As shown in fig. 14, the system 1400 includes a DMA server 1402 that can be connected to a plurality of BTSs 1404. Each BTS1404 may provide cellular coverage for one or more mobile communication devices 1406. Fig. 14 also shows: 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 T1 connection, a cable connection, a microwave connection, or a satellite connection. Further, the system 1400 shown in FIG. 14 can be deployed using CDMA, IS-95, CDMA1X, GSM/GPRS, W-CDMA, or other industry standard techniques.

The use of a single backhaul connection greatly reduces the costs associated with a wireless communication network. Further, the system 1400 depicted in FIG. 14 can be deployed relatively quickly and can be maintained remotely. Further, by including the OAMP module 540 (fig. 5) and the AAA module 528 (fig. 5), user accounts can be managed locally and accounting can be performed locally, i.e., within the DMA server 1402. Furthermore, as the number of users increases, the size of the system is increased, e.g., scalably, by adding DMA servers, corresponding BTSs, and appropriate connections.

Fig. 15 illustrates a built-in telecommunications network, generally designated 1500. Fig. 15 shows a building 1502, e.g., an office building, a commercial building, a house, etc. Within bye-owner 1502 is installed an enterprise Local Area Network (LAN) 1504. The micro-BTS 1506 is connected to the enterprise LAN 1504. Further, 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: dynamic Host Configuration Protocol (DHCP) servers, radius servers, Domain Name Servers (DNS), and the like. As shown in fig. 15, multiple phones 1512 (e.g., IP desktop phones) may be connected to the enterprise LAN 1504.

Fig. 15 also shows: an office DMA server 1514 may be connected to the enterprise LAN 1504. An office DMA server 1514 may also be connected to the PSTN1516, which in turn may be connected to a cellular voice and data network 1518. The enterprise LAN1504 may also be connected to a cellular voice and data network 1518 via an Internet Protocol (IP) network 1520. The 7 signaling system (SS7) network 1522 may be connected to a cellular voice and data network 1518 and an IP network 1520. Fig. 15 also shows: a gateway 1524 between the SS7 network 1522 and the IP network 1520, and a firewall 1526 between the enterprise LAN1504 and the IP network 1520. Fig. 15 shows a wireless communication device 1528 in communication with a cellular voice and data network 1518 and a micro-BTS 1506.

Referring to fig. 16, a mobile field (in-field) telecommunications system is shown, generally designated 1600. As shown, the system 1600 includes a plurality of mobile cellular coverage sites 1602. Each mobile cellular coverage site 1602 includes a vehicle 1604 in which a field DMA server 1606 is located. Further, a BTS1608 is disposed within each vehicle 1604, and the BTS1608 can be physically connected directly (e.g., connected by a cable or cable therebetween) to the on-site DMA server 1606. The onsite DMA server 1606 and BTS1608 can be removably installed within the vehicle 1604 or the onsite DMA server 1606 and BTS1608 can be permanently affixed in the vehicle 1604. Fig. 16 also indicates that: each BTS1608 may include an antenna 1610 designed to communicate with mobile communication devices. In addition, each field DMA server 1606 includes an antenna 1612. In an exemplary, non-limiting embodiment, the field DMA servers 1606 can communicate with each other via the antenna 1612 wirelessly (e.g., via 802.11a, 802.11b, microwave, or other wireless link).

The mobile cellular coverage site 1602 may be deployed as a temporary web that provides cellular coverage to a plurality of mobile communication devices, such as devices carried by soldiers during a war. The mobile field communication system 1600 can be eliminated, moved, and redeployed as necessary. Further, the system may include a wireless connection (e.g., 802.11a, 802.11b, microwave) to the PSTN 1614.

Referring to fig. 17, another telecommunications system is shown and is generally designated 1700. As shown in fig. 17, the system 1700 includes a DMA server 1702 that is connected to a BTS 1704. The BTS1704 is then connected to an antenna 1706. Fig. 17 also shows: a first satellite transceiver 1708 is also connected to the DMA server 1702. The first satellite transceiver 1708 communicates with a second satellite transceiver 1710 via a satellite 1712. In addition, the second satellite transceiver 1710 includes a data network connection 1714, for example, a T1 connection or an E1 connection. The satellite transceivers 1708, 1710 and the satellite 1712 can provide backhaul connections to the DMA server 1702. Alternatively, the satellite transceivers 1708, 1710 and the satellite 1712 may connect the DMA server 1702 to another DMA server (not shown).

Fig. 18 shows another telecommunications system, generally designated 1800. As shown in fig. 18, the system includes a DMA1802 that is connected to a first satellite transceiver 1804. In addition, the DMA1802 includes a primary network connection 1806 (e.g., a T1 connection or an E1 connection) and a secondary network connection 1808 (e.g., an IP connection). Fig. 18 shows: the 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 and third satellite transceivers 1810, 1812 is connected to an interworking unit (IWU)1816 via a data network connection 1818 (e.g., an IP connection). Each IWU1816 is connected to a BTS1820, which in turn is connected to an antenna 1822. The satellite transceivers 1804, 1810, 1812 provide IP network extensions to the DMA server 1802. Further, in the deployment shown in fig. 18, the DMA server 1802 can act as a centralized micro-switch for handling calls received at the antenna 1822 and transmitted via the second and third satellite transceivers 1810, 1812.

Referring to fig. 19, another telecommunications system is shown, which is designated 1900. As shown, the system 1900 includes a DMA server 1902 having a plurality of network connections 1904. Further, the 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 1WU1906 via a secondary network connection 1908, such as a category 5(Cat5) cable connection, a microwave connection, or a WLAN connection. Further, each 1WU1906 is connected to a BTS1910, and then, each BTS1910 is connected to an antenna 1912. Each BTS1910 may be a 3-segment BTS. In the deployment shown in fig. 19, the DMA server 1902 can act as a centralized micro-switch that can be used to handle telephony traffic received at the antenna 1912.

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

In a particular embodiment, the first satellite transceiver 2008 can communicate with the second satellite transceiver 2012 via a satellite 2014. As shown, the second satellite transceiver 2012 can be connected to a ground server network 2016 (e.g., a DMA server gateway) that can provide connectivity to an Operations and Management Platform (OMP)2018, a Call Detail Record (CDR)2020, and a visitor location register gateway (VLR-GW) 2022. OMP2018, CDR2020, and VLR-GW2022 may be separate from or incorporated into server gateway 2016. Fig. 20 also shows: the server gateway 2016 may 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 for use in an aircraft 2002 for communicating with ground-based telephones. For example, the mobile communication device 2010 may communicate with the BTS2006, which may then communicate with the first satellite transceiver 2008 via the DMA server 2004. Further, the first satellite transceiver 2008 can send the call to the ground-based communication system via the second satellite transceiver 2012 and the satellite 2014.

FIG. 20 illustrates a single airplane, however, multiple airplanes can be configured as described herein to provide communication from the multiple airplanes to the ground-based phone. Further, aircraft-to-aircraft communication may be provided, and further, system 2000 may include other aerial vehicles, such as small aircraft.

Fig. 21 shows another embodiment of a communication system, designated 2100. As shown, the system 2100 includes a ship 2102 having a DMA server 2104 installed. As shown, the DMA server 2104 is coupled to a BTS2106 and a first satellite transceiver 2108. Fig. 21 also shows a mobile communication device 2110 within the ship 2102. The mobile communication device 2110 may be a wireless communication within the 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 terrestrial server network 2116 (e.g., a DMA server gateway), which can provide connectivity to an Operations and Management Platform (OMP)2118, a Call Detail Record (CDR)2120, and a visitor location register gateway (VLR-GW) 2122. OMP2118, CDR2120, and VLR-GW2122 may be separate from or incorporated into server gateway 2116. Fig. 21 also shows: the server gateway 2116 may be connected to a first Mobile Switching Center (MSC)2124 that is coupled to a second MSC 2106.

Thus, the system shown in FIG. 21 may allow for communication with ground-based phones within the ship 2102. For example, the mobile communication device 2110 may communicate with the BTS2106, which may then communicate with the first satellite transceiver 2108 via the DMA server 2104. Further, the first satellite transceiver 2108 may send the call to a ground-based communication system via the second satellite transceiver 2112 and the satellite 2114

Fig. 21 shows a single ship, however, multiple ships may be configured as described herein to provide communication from multiple ships to a ground-based telephone. Furthermore, ship to goldenrain communication may be provided, and further, the system 2100 may include other water borne vehicles.

Referring to FIG. 22, a method of deploying a distributed management architecture server is shown and begins at block 2200 where subsequent steps are performed during deployment. At block 2202, the DMA server is moved to a desired location near the BTS. Turning to block 2204, the DMA server is turned on. For example, if the DMA server is the DMA server shown in fig. 1, the latch is unlocked and the lid is rotated about the hinge to an open position. Proceeding to block 2206, a physical connection is established between the DMA server and the BTS, e.g., the BTS is coupled to the DMA server via a cable.

Continuing to block 2208, the DMA server is activated, e.g., powered on. At block 2210, a network connection is established with another remote DMA server. In particular embodiments, the network connection is a peer-to-peer connection between the DMA servers. Turning to block 2212, DMA server software within the DMA server is activated. Thereafter, at decision step 2214, a determination is made as to whether the system is operational. The determination may be performed by the DMA server (e.g., by a self-diagnostic program or module within the DMA server). Alternatively, the decision step may be determined manually by a technician. If the system is not operational, a system check is performed at block 2216. 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, the technician may perform a system check. After system check, the logic then returns to decision step 2214 and continues as described above. At decision step 2214, if the system is operational, the method proceeds to block 2218 and the call transmission 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 a direct physical connection between a first DMA server and a 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 proximate to the base transceiver station. At block 2306, a second DMA server is turned on. For example, if the DMA server is the DMA server shown in fig. 1, the latch is unlocked and the lid is rotated about the hinge to an 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 particular embodiments, the network connection is a peer-to-peer connection between the DMA servers. Further, in particular embodiments, the peer-to-peer connection is established via a private IP network. At block 2314, DMA server software within the second DMA server is activated.

Proceeding to step 2316, a determination is made as to whether the system is operational. The determination may be performed by the DMA server (e.g., by a self-diagnostic program or module within the second DMA server). Alternatively, the decision step may be determined manually by a technician. If the system is not operational, a system check is performed at block 2318. 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, the technician may perform a system check. After system check, the logic then returns to decision step 2316 and continues as described above. At decision step 2316, if the system is operational, the method proceeds to block 2320 and call transmission via the second server is allowed. The method then stops at state 2322.

With the above configuration of the architecture, the present invention discloses a flexible telecommunications device (i.e., DMA server 406 (fig. 4)) that is distributively associated, i.e., it can operate independently and seamlessly within an existing cellular or other network. Further, the DMA server 406 can be integrated with any third party base station in a virtual manner. The DMA server 406 may operate with a variety of air interfaces including CDMA IS-95, CDMA1X, CDMA EVDO, GSM, GPRS, W-CDMA, 802.11(Wi-fi), 802.16(Wi-fi), and the like. Further, the DMA server 406 may provide integrated prepaid accounting, OAMP, network management, and AAA functions. In addition, the DMA server 406 may include a Java-based user interface and feature configuration system. In addition, the DMA server 406 may provide real-time call metering, Call Detail Record (CDR) generation, and real-time call provisioning. The DMA server 406 may be implemented in a relatively small footprint and has relatively low power requirements. Further, the DMA server 406 may be implemented using less expensive and widely available computer equipment.

With one or more of the above-configured deployments, the system provides mobile-to-landline calls from mobile handsets within the DMA server cellular coverage area. In addition, mobile-to-landline calls can be made from mobile handsets roaming into DMA coverage areas. A mobile-to-mobile call may be made from a home/roaming handset to a DMA handset and vice versa. In addition, mobile-to-IP calls and IP-to-mobile calls may be implemented from within the DMA server coverage area. An IP-to-IP call 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, an on-line-to-mobile call may be made to the DMA handset.

The system as described above may support call forwarding, call waiting, 3-way caller ID, voicemail, and mobile-to-mobile SMS services, i.e., text messaging. Further, the system as described above may support a broadcast SMS service, a high speed IP data (1X or GPRS) service for mobile-to-land, and a high speed IP data (1X or GPRS) service for mobile-to-mobile. In addition, the system as described above may provide IP-PBX capability.

Further, one or more of the illustrated systems may provide for IP transport between distributed components, such as the DMA server 406 (fig. 4). Packet backhaul from the BTS to the RAN may be provided. Further, the control logic within the DMA server 406 (FIG. 4) may be distributed and associated. The associated system may be redundant, self-healing, self-organizing, and scalable. The distributed system may be "snap-together," i.e., the DMA server 406 (fig. 4) may be linked to a previously deployed DMA server 406 (fig. 4) in order to broaden or otherwise extend the cellular coverage. Furthermore, the distributed system may be decentralized to avoid single points of failure.

One or more of the systems described above may also provide for soft or softer call handoffs over the same frequency interface. In addition, soft call handoff may be provided on a different system. Further, the DMA based system may operate independently of the billing system and CDR generation provided by the DMA server. Alternatively, the system may use the SS7 network to deliver CDRs to a central switch for integrated billing and operations over existing networks.

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

Claims (18)

1. A method, comprising:

receiving, at a communication apparatus, a request to establish a group call between four or more mobile communication devices, wherein the communication apparatus comprises:

a wireless transceiver;

a computer-readable storage medium;

a Home Location Register (HLR) module embedded in the computer-readable storage medium;

a Visitor Location Register (VLR) module embedded in the computer-readable storage medium;

a Mobile Switching Center (MSC) module embedded in the computer-readable storage medium, wherein the MSC module comprises an authentication, authorization, and accounting (AAA) module configured to support generation of a first set of call detail records at the communication device;

a Base Station Controller (BSC) module embedded in the computer-readable storage medium; and

a group call program embedded in the computer readable storage medium; and

providing a group call between four or more mobile communication devices through a group call program embedded in a computer readable storage medium of the communication apparatus, wherein the communication apparatus communicates telephony data associated with the group call to at least one of the four or more mobile communication devices through a second communication apparatus, wherein the second communication apparatus comprises:

a second wireless transceiver;

a second computer-readable storage medium;

a second HLR module embedded in said second computer readable storage medium;

a second VLR module embedded in said second computer readable storage medium;

a second MSC module embedded in the second computer-readable storage medium, wherein the second MSC module comprises a second AAA module configured to support generation of a second group call detail record at the second communication device; and

a second BSC module embedded in the second computer-readable storage medium.

2. The method of claim 1, further comprising providing full duplex call capability between each of the four or more mobile communication devices through the group call procedure.

3. The method of claim 2, further comprising allowing a first set of mobile communication devices to disconnect from the group call without affecting a second set of mobile communication devices remaining on the group call.

4. The method of claim 3, further comprising providing full duplex call capability between each of a second set of mobile communication devices remaining on the group call through the group call procedure.

5. The method of claim 4, further comprising:

receiving, at the communication device, telephony data from an additional mobile communication device; and

connecting the additional mobile communication device to the group call through the group call procedure.

6. The method of claim 5, further comprising providing full duplex call capability between the additional mobile communication device and each of a second set of mobile communication devices remaining on the group call through the group call procedure.

7. The method of claim 1, further comprising:

receiving, at the communication device, telephony data from a plurality of additional mobile communication devices; and

connecting the plurality of additional mobile communication devices to the group call through the group call program.

8. A communication device, comprising:

a wireless transceiver;

a computer-readable storage medium;

a Home Location Register (HLR) module embedded in the computer-readable storage medium;

a Visitor Location Register (VLR) module embedded in the computer-readable storage medium;

a Mobile Switching Center (MSC) module embedded in the computer-readable storage medium, wherein the MSC module comprises an authentication, authorization, and accounting (AAA) module configured to support generation of a first set of call detail records at the communication device;

a Base Station Controller (BSC) module embedded in the computer-readable storage medium; and

a group call program embedded in the computer readable storage medium, the group call program providing a group call between four or more mobile communication devices in response to receiving a request to establish a group call, wherein telephony data associated with the group call is communicated to at least one of the four or more mobile communication devices by a second communication apparatus, wherein the second communication apparatus comprises:

a second wireless transceiver;

a second computer-readable storage medium;

a second HLR module embedded in said second computer readable storage medium;

a second VLR module embedded in said second computer readable storage medium;

a second MSC module embedded in the second computer-readable storage medium, wherein the second MSC module comprises a second AAA module configured to support generation of a second group call detail record at the second communication device; and

a second BSC module embedded in the second computer-readable storage medium.

9. The communication apparatus of claim 8, wherein the group call procedure provides full duplex call capability between each of the four or more mobile communication devices.

10. The communication apparatus of claim 9, wherein the set of procedures allows a first set of mobile communication devices to disconnect from the group call without affecting a second set of mobile communication devices remaining on the group call.

11. The communication apparatus of claim 10, wherein the group call procedure provides full duplex call capability between each of the second set of mobile communication devices remaining on the group call.

12. The communication device of claim 8, wherein the wireless transceiver comprises at least one Base Transceiver Station (BTS).

13. A communication system, comprising:

a first communication device comprising:

a first wireless transceiver;

a first computer-readable storage medium;

a first Home Location Register (HLR) module embedded in the first computer-readable storage medium;

a first Visitor Location Register (VLR) module embedded in the first computer readable storage medium;

a first Mobile Switching Center (MSC) module embedded in the first computer-readable storage medium, wherein the first MSC module comprises a first authentication, authorization, and accounting (AAA) module configured to support generation of a first set of call detail records at the first communication device;

a first Base Station Controller (BSC) module embedded in the first computer-readable storage medium; and

a first group call program embedded in the first computer readable storage medium, the first group call program providing a first group call between a first set of four or more mobile communication devices; and

a second communication device comprising:

a second wireless transceiver;

a second computer-readable storage medium;

a second HLR module embedded in said second computer readable storage medium;

a second VLR module embedded in said second computer readable storage medium;

a second MSC module embedded in the second computer-readable storage medium, wherein the second MSC module comprises a second AAA module configured to support generation of a second group call detail record at the second communication device;

a second BSC module embedded in the second computer-readable storage medium; and

a second group call program embedded in the second computer readable storage medium, the second group call program providing a second group call between a second set of four or more mobile communication devices.

14. The communication system of claim 13, wherein Internet Protocol (IP) packet data is communicated between the first communication device and the second communication device over a peer-to-peer IP connection.

15. The communication system of claim 13, wherein the first communication device is portable.

16. The communication system of claim 15, wherein the first communication device is adapted to send Internet Protocol (IP) packet data to the second communication device over a peer-to-peer IP connection when the first communication device is moving.

17. The communication system of claim 13, wherein the second communication device is portable, and wherein the second communication device is adapted to send Internet Protocol (IP) packet data to the first communication device over a peer-to-peer IP connection when the first communication device is moving.

18. The communication system of claim 13, wherein the first communication device and the second communication device are portable, and wherein Internet Protocol (IP) packet data is communicated between the first communication device and the second communication device over a peer-to-peer IP connection when both the first communication device and the second communication device are mobile.