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

An authentication, authorization, and accounting module of a first distributed mobile architecture system is disclosed and includes a destination preference register. The destination preference register includes a preferred call path for calls to be routed outside of a distributed mobile architecture network that is accessible to the first distributed mobile architecture system. The preferred call path can be selected from a group comprising a voice over Internet protocol (VoIP) call path, a mobile switching center (MSC) call path, and an integrated services digital network (ISDN) call path. Further, calls that are placed outside of the distributed mobile architecture network from the first distributed mobile architecture system can be established via the preferred call path. Additionally, calls that are routed outside of the distributed mobile architecture network from a mobile subscriber in communication with the first distributed mobile architecture system can be established via the preferred call path.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to the distributed mobile communication systems.

BACKGROUND

Access to basic telephony service is particularly important for rural and isolated communities. Telephony access allows small-scale enterprises, cooperatives, and farmers to obtain accurate information on fair prices for their products and to access regional and national markets. Access also reduces the cost of transportation and supports the local tourist industry. By bringing markets to people via telecommunications, rather than forcing people to leave in search of markets, urban migration is reduced and greater income and employment potential are generated in rural areas.

Unfortunately, the last decade of the telecommunications boom has not alleviated the disparities between urban and rural communities. The average imbalance, in terms of telephone penetration, in Asia, for example, is over ten to one and is often as high as twenty to 1.2. This means that a country whose urban markets have a penetration of four (4) telephone lines per one-hundred (100) inhabitants, e.g., India and Pakistan, has a rural penetration of less than 0.2 per one-hundred (100). The situation is more acute in most African countries and in some parts of Latin America. By comparison, the disparity in average income level between urban and rural residents in the developing world is usually less than 4 to 1.

Current telephone systems are expensive to deploy. For example, a typical cellular system that includes a mobile switching center (MSC), a base station controller (BSC), and a home location register/visitor location register (HLR/VLR) can cost over $2.0 million. Moreover, such a system may require a minimum of ten thousand users in order to be economically viable. In many rural areas, the population is not large enough to support the installation of such a system. Further, in many cases, the conditions in which the equipment, e.g., the MSC, BSC, and HLR/VLR, are to be operated are extremely harsh and environmentally challenging. An alternative to such a cellular system can include a wired system, but the costs associated with deploying and maintaining land lines are too high for certain rural areas.

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

DETAILED DESCRIPTION OF THE DRAWINGS

An authentication, authorization, and accounting module of a first distributed mobile architecture system is disclosed and includes a destination preference register. The destination preference register includes a preferred call path for calls to be routed outside of a distributed mobile architecture network that is accessible to the first distributed mobile architecture system.

In a particular embodiment, the preferred call path is selected from a group comprising a voice over Internet protocol (VoIP) call path, a mobile switching center (MSC) call path, and an integrated services digital network (ISDN) call path. Further, in a particular embodiment, calls that are placed outside of the distributed mobile architecture network from the first distributed mobile architecture system are established via the preferred call path. Additionally, in another particular embodiment, calls that are routed outside of the distributed mobile architecture network from a mobile subscriber in communication with the first distributed mobile architecture system are established via the preferred call path.

In a particular embodiment, the destination preference register includes a first preferred call path, a second preferred call path, and a third preferred call path. Some calls that are routed outside of the distributed mobile architecture network are made via a first available preferred call path. In a particular embodiment, the module also includes a home location register that includes information associated with one or more mobile subscribers registered with the first distributed mobile architecture system, and wherein the home location register provides information related to a first community location register at a second distributed mobile architecture system.

In a particular embodiment, the module also includes a second community location register that includes information associated with one or more mobile subscribers registered with the second distributed mobile architecture system. Also, the module can includes a third community location register that includes information associated with one or more mobile subscribers registered with a third distributed mobile architecture system.

In another particular embodiment, the module includes a visitor location register that includes information associated with one or more roaming mobile subscribers that are temporarily registered with the first distributed mobile architecture system.

In another embodiment, a method of communication is disclosed and includes receiving a call directed to a destination mobile directory number that is not available within a community location register within a distribute mobile architecture and matching a prefix of the mobile directory number to a mobile directory number prefix within a destination preference register.

In yet another embodiment, a distributed mobile architecture device is provided and includes a processor and a computer readable medium that is accessible to the processor. An authentication, authorization, and accounting module is embedded within the computer readable medium and includes a destination preference register. The destination preference register includes at least one preferred call path associated with calls to be placed outside a distributed mobile architecture network that is accessible from one or more distributed mobile architecture devices.

In still another embodiment, a system is disclosed and includes a distributed mobile architecture network that includes a first distributed mobile architecture device, a second distributed mobile architecture that is coupled to the first distributed mobile architecture, and a third distributed mobile architecture that is coupled to the first distributed mobile architecture and to the second distributed mobile architecture. Further, a voice over Internet protocol (VoIP) interface can be coupled to the first distributed mobile architecture, the second distributed mobile architecture, or the third distributed mobile architecture. An integrated services digital network (ISDN) interface can be coupled to the first distributed mobile architecture, the second distributed mobile architecture, or the third distributed mobile architecture. Also, a mobile switching center (MSC) interface can be coupled to the first distributed mobile architecture, the second distributed mobile architecture, or the third distributed mobile architecture. In this embodiment, the first distributed mobile architecture, the second distributed mobile architecture, and the third distributed mobile architecture can each include a destination preference register that includes at least one preferred interface supporting calls to be placed outside the distributed mobile architecture network.

Referring toFIG. 1, a non-limiting, exemplary embodiment of a distributed and associative telecommunications system is illustrated and is generally designated100. As depicted inFIG. 1, the system100includes four cellular coverage sites102. Each coverage site102includes an antenna104. In one embodiment, the antenna104is connected to a transceiver belonging to a base transceiver station (BTS) and the BTS is a 3-sector BTS.FIG. 1also indicates that a distributed mobile architecture (DMA)106can be connected to each antenna104. In one embodiment, each DMA106is physically and directly connected to its respective antenna104, e.g., by a wire or cable108. Further, in an illustrative embodiment, each DMA106can include the components described herein in conjunction withFIG. 3.

As illustrated inFIG. 1, each DMA106is interconnected with the other DMAs106via an Internet protocol network110. As such, there exists a peer-to-peer connection112between each DMA106in the system100. The DMAs106can handle telephony traffic that is communicated at each antenna104. For example, the DMAs106can switch and route calls received via each antenna104. Additionally, the DMAs106can hand-off calls to each other as mobile communication devices move around and between the cellular coverage sites102. The DMAs106can communicate with each other via the IP network110and can further transmit calls to each other via the IP network110. It should be understood that more than four cellular coverage sites102can be included in the system and that the inclusion of only four cellular coverage sites102inFIG. 1is merely for clarity and explanation purposes.

Within the distributed and associative communications system100, the controlling logic can be distributed and de-centralized. Moreover, the wireless coverage provided by the disclosed system100is self-healing and redundant. In other words, due to the interconnectivity via the IP network110, if one or more of the DMAs106loses power, fails, or is otherwise inoperable, telephony traffic handled by the inoperable DMA106can re-routed to one of the remaining operable DMAs106. Additionally, user data stored in a database, e.g., a home locator resource (HLR) or a visitor locator resource (VLR), can be distributed equally and fully among all of the DMAs106. It can also be appreciated that new cellular coverage sites can be easily added to the system100as the demand for users increases. Specifically, a DMA can be deployed, connected to an antenna, connected to the IP network, and activated to provide cellular coverage in a new area.

FIG. 2shows an exemplary, non-limiting embodiment of a network system, generally designated200, that includes a plurality of DMAs. As illustrated inFIG. 2, the system200can include an Internet protocol (IP) peer-to-peer network that includes a first distributed mobile architecture202that is coupled to a second distributed mobile architecture204and to a third distributed mobile architecture206. Further, the second distributed mobile architecture204is coupled to the third distributed mobile architecture206.

As shown inFIG. 2, a first mobile subscriber208and a second mobile subscriber210are wirelessly coupled to the first distributed mobile architecture202. A first mobile subscriber212and a second mobile subscriber214are wirelessly coupled to the second distributed mobile architecture204. Additionally, a first mobile subscriber216and a second mobile subscriber218are wirelessly coupled to the third distributed mobile architecture206.FIG. 3further indicates that a mobile switching center (MSC) interface220can be coupled to the first distributed mobile architecture202to provide access to a mobile telephone network, such as a cellular telephone network. Further, a voice over Internet protocol (VoIP) interface222is coupled to the second distributed mobile architecture204to provide access to a VoIP network.FIG. 3also shows that an integrated services digital network (ISDN) interface224can be coupled to the third distributed mobile architecture206to provide connectivity to an ISDN.

In a particular embodiment, as described in detail herein, a mobile subscriber can communicate with another mobile subscriber via the first distributed mobile architecture202, the second distributed mobile architecture204, or the third distributed mobile architecture206. Further, in a particular embodiment, a mobile subscriber can communicate with another mobile subscriber via the first distributed mobile architecture202and the second distributed mobile architecture204, the first distributed mobile architecture202and the third distributed mobile architecture206, and the second distributed mobile architecture204and the third distributed mobile architecture206. Additionally, in a particular embodiment, a mobile subscriber can communicate with another mobile subscriber via the first distributed mobile architecture202, the second distributed mobile architecture204, or the third distributed mobile architecture206.

Further, in a particular embodiment, the first mobile subscriber210of the first DMA202can be connected locally to the second mobile subscriber210of the first DMA202after locating the second mobile subscriber210within the a home location register (HLR) within the first DMA202. Additionally, the first or second mobile subscriber210,212of the first DMA202can be connected to the first or second mobile subscriber212,214of the second DMA204after locating the first or second mobile subscriber212,214of the second DMA204within a second community location register (CLR) associated with the second DMA202that is stored within the first DMA202. Moreover, the first or second mobile subscriber210,212of the first DMA202can be connected to the first or second mobile subscriber216,218of the third DMA206after locating the first or second mobile subscriber216,218of the third DMA206within a third community location register (CLR) associated with the third DMA206that is stored within the first DMA202.

As a mobile subscriber roams into a coverage area that is not provided by the DMA to which the mobile subscriber is registered, the mobile subscriber can be temporarily registered with a new DMA while the mobile subscriber is roaming. CLR information concerning the roaming mobile subscriber can be obtained from the new DMA in order to complete a call to the roaming mobile subscriber.

In another particular embodiment, calls can be made from a mobile subscriber to an external destination, i.e., external to the DMA network, vie the MSC interface220, the VoIP interface222, or the ISDN interface224. A user can create a preferred hierarchy of interfaces to make calls external to the DMA network. As such, a user can indicate that all calls made from a mobile subscriber to an external device are to be established via the VoIP interface222. If the VoIP interface222is unavailable, a second preferred interface can be used to establish the external call.

FIG. 3shows an exemplary, non-limiting, embodiment of a DMA, e.g., one of the DMAs106described in conjunction withFIG. 1or one of the DMAs202,204,206shown inFIG. 2. In a particular embodiment, the DMA106includes a processor, or computer, having a housing and a computer readable medium300that is disposed therein. A power supply302can also be disposed within the housing of the DMA106in order to provide power to the DMA106. The power supply302can be a rechargeable battery disposed within the DMA106or it can be external to the DMA106, i.e., a standard power outlet. Moreover, a cooling system304, e.g., a fan with a thermostat, can be within the DMA106in order to keep the DMA106from overheating. In an alternative embodiment, the DMA106can be a single board processor that does not require a fan.

As depicted inFIG. 3, the DMA106can include a mobile switching center (MSC) module306and a base station controller (BSC) module308embedded within the computer readable medium300. In an exemplary, non-limiting embodiment, the MSC module306can include a gatekeeper (GK)310that is connected to several gateways. For example, a circuit gateway (CGW)312can be connected to the GK310and can provide connectivity to an integrated services digital network/public switched telephone network (ISDN/PSTN) interface314. The CGW312can provide a circuit switched to packet data conversion. In an exemplary, non-limiting embodiment, the PSTN portion of the ISDN/PSTN interface314can be an inter-office interface that uses the Bellcore industry standard ISDN user part (ISUP) signaling on a signaling system seven (SS7) link set. Moreover, the voice trunks on this interface can be timeslots on a T1 connection. Inbound and outbound voice calls can be supported on the ISDN portion of the ISDN/PSTN interface314.

As further illustrated inFIG. 3, a packet data service node (PDSN) gateway316for CDMA, or a Gateway GPRS Support Node (GGSN) for Global System for Mobile Communication (GSM), and a Session Initiation Protocol (SIP) gateway318can also be connected to the GK310. The PDSN gateway316and the SIP gateway318can provide connectivity to an Internet protocol (IP) interface320. Further, the PDSN gateway316or a GGSN can establish a reverse tunnel with the PDSN or GGSN gateway316using generic routing encapsulation (GRE). Moreover, the PDSN gateway316, or GGSN, can implement the Pseudo Random Function (PRF)/Foreign Agent (FA) functionality of the DMA106which supports mobile IP functions.

FIG. 3further shows an SS7 gateway322that provides connectivity to an ANSI-41 and GSM Mobile Application Part (MAP) interface324. In a particular embodiment, the ANSI-41 interface can be an SS7 TCAP/SCCP interface on the same SS7 link set used for ISUP signaling. The same SS7 point code can be used to identify the DMA106in the ANSI-41 network. The ANSI-41 interface can be used for roamer registration. Further, in an exemplary, non-limiting embodiment, the GSM MAP interface can be an SS7 TCAP/SCCP interface on the same SS7 link set used for ISUP signaling. It can be appreciated that there are different protocols of MAP from MAP/B to MAP/I, but in the illustrative embodiment, the different MAP/x protocols are not stacked—they are used independently.

As depicted inFIG. 3, a media gateway326can also be coupled to the GK310. In an exemplary, non-limiting embodiment, the media gateway326can include cellular transcoders, one or more intranet gateways, conferencing bridges, and group calling functionality. Further, an authentication, authorization, and accounting (AAA) module328can be coupled to the GK310. In an exemplary, non-limiting embodiment, there are three levels of authentication management. The highest level is for administration, the mid-level is for operations, and the lowest level is for normal users. The functions of the AAA module328can be included in the user level.

In an exemplary, non-limiting embodiment, the GK310can act as an AAA server and a feather server to support advanced supplementary service, short message service, etc. Moreover, the GK310can act as a call manager and can support ISUP and PSTN f unction calls. Additionally, the GK310can act as a signal gateway, e.g., IP to SS7 inter-working, ISUP, GSM MAP or ANSI-41 to PSTN and ANSI-42/GSM. The GK310can also function as a data call server.

As illustrated inFIG. 3, the BSC module308includes a cellular radio network controller (CRNC)330and a cellular selection/distribution unit (CSDU)332that are connected to a call protocol controller (CPC)334. In turn, the CPC334can be connected to a plurality of base transceiver stations (BTSs)336. Specifically, the DMA106includes a BTS interface338at the CPC334that can be physically and directly connected to the BTSs336. The CRNC330can provide cellular radio resource management and cellular call control. The CSDU332can provide Fundamental Channel (FCH) soft handoff and distribution, Link Access Control (LAC) processing for inband signaling, multiplexer (MUX) functions, and centralized power control. Further, the CPC334can convert a T1 or E1 message or ATM interface to a data packet message. In a particular embodiment, each BTS336supports signals and traffic up to the front point of the CPC334, e.g., up to the BTS interface338. Further, in a particular embodiment, the CRNC330, the CPC334, the CSDU332and the OAMP340can perform one or more of the functions of legacy Base Station Controllers (BSC).

In an exemplary, non-limiting embodiment, the BTS interface338can be an IS-95A OR IS-2000 interface over E1 or ATM, or the BTS interface338can be a GSM BTS interface using Abis or an UMTS Iub interface or customized application for mobile network enhanced logic (CAMEL). In an illustrative embodiment, the CPC334can be connected to one or more BTSs336.FIG. 3further shows that the BSC module308includes an operations, administration, maintenance, and provisioning (OAMP) module340. In an exemplary, non-limiting embodiment, the OAMP module340can use simple network management protocol (SNMP) for operations interfaces. Further, the OAMP module340can include a JAVA user interface. The OAMP module340can also include a software agent that is assigned to each component within the DMA106. The agents independently monitor their respective components. Moreover, each agent can provision its respective component.

In a particular embodiment, a DMA can be implemented as a system or a device. For example, a DMA system or a DMA device can include a DMA server or an DMA on board processor.

FIG. 4depicts a plurality of DMAs. Particularly,FIG. 4depicts a first DMA400, a second DMA402, and a third DMA404.FIG. 4indicates that, in general, each DMA400includes a visitor location register (VLR), a home location register (HLR), and at least one community location register (CLR). In a particular embodiment, the VLR, HLR, and the CLR within each DMA400,402,404are part of an AAA module within each DMA400,402,404. For example, the HLR, VLR, and CLR may be within the AAA module328of the exemplary DMA ofFIG. 3.

In a particular embodiment, as indicated inFIG. 4, the first DMA400includes a VLR406, an HLR408, a second CLR410, and a third CLR412. Further, the second DMA402includes a VLR414, a first CLR416, an HLR418, and a third CLR420. Additionally, the third DMA404includes a VLR422, a first CLR424, a second CLR426, and an HLR428.

In an exemplary, non-limiting embodiment, the first CLR416within the second DMA402and the first CLR424within the third DMA404correspond to the HLR408of the first DMA400. More particularly, the first CLR416within the second DMA402and the first CLR424within the third DMA404include information that is stored within the HLR408of the first DMA server400.

Additionally, in an exemplary, non-limiting embodiment, the second CLR410within the first DMA400and the second CLR426within the third DMA404correspond to the HLR418of the second DMA402. More particularly, the second CLR410within the first DMA400and the second CLR426within the third DMA404include the information that is stored within the HLR418of the second DMA server402.

Also, in an exemplary, non-limiting embodiment, the third CLR412within the first DMA400and the third CLR420within the second DMA402correspond to the HLR428of the third DMA404. More particularly, the third CLR412within the first DMA400and the third CLR420within the second DMA402include the information that is stored within the HLR428of the third DMA server404.

FIG. 4further indicates that the first DMA400can include a destination preference register (DPR)430. Also, the second DMA402can include a DPR432. Moreover, the third DMA404can also include a DPR434. In a particular embodiment, each DPR430,432,434includes a preference for a call path to be used to place calls outside of a DMA network provided by the DMAs400,402,404. In a particular embodiment, the preference is established for each mobile subscriber registered with the DMA network. In another embodiment, the preference is established for each DMA within the DMA network.

Referring toFIG. 5, an exemplary, non-limiting embodiment of an authentication, authorization, and accounting (AAA) module is shown and is generally designated500. The AAA module depicted inFIG. 5can be embedded within any of the DMAs that are described herein. As indicated inFIG. 5, the AAA module500includes data associated with an HLR502, a second CLR504, a third CLR506, and a VLR508. As shown, the HLR502data includes a plurality of IP addresses that can be used to establish one or more telephone calls within a first DMA in which the AAA module500is embedded. The HLR502data further includes a GPS location of the first DMA in which the AAA500is embedded.

As illustrated inFIG. 5, the second CLR504and the third CLR506include one or more IP addresses that can be used to establish one or more telephone calls via a second and third DMA that are coupled to the first DMA in which the AAA module500is embedded. The second CLR504and the third CLR506also include a GPS location for the second and third DMA that are coupled to the first DMA in which the AAA module500is embedded. Further, the second CLR502and the third CLR504include a neighborhood (NB) list to identify neighboring DMS that are located proximately to the DMA in which the AAA module500is embedded.

FIG. 5further indicates the data associated with the HLR502, the second CLR504, the third CLR506, and the VLR508include at least one international mobile subscriber identification (IMSI)512and at least one electronic series number (ESN)514. Moreover, the HLR502, the second CLR504, and the third CLR506records also include at least one mobile directory number (MDN)516. In a particular embodiment, the HLR502includes a location518for at least one mobile subscriber that is registered with the HLR502.

As shown inFIG. 5, the HLR502and the VLR508further include at least one temporary location directory number (TLDN)520, a registration indicator522, a timer524, a mobile switching center (MSC) preference indicator526, an integrated services digital network (ISDN) preference indicator528, and a voice over Internet protocol (VoIP) preference indicator530and a timer interval given to the visited mobile to be registered.

As shown inFIG. 5, the AAA module500can also include a DPR530. As shown the DPR530includes at least one MDN prefix532. Further, the DPR530includes a first preferred destination indicator534, a second preferred destination indicator536, and a third preferred destination indicator538. In a particular embodiment, the preferred destination indicators534,536,638indicate a hierarchy of call paths that may be used to place calls outside a DMA network provided by one or more DMAs. For example, the first preferred destination indicator534can be a VoIP call path, the second preferred destination indicator536can be an ISDN call path, and the third destination indicator can be an MSC call path.

As such, in an illustrative embodiment, when a mobile subscriber attempts to call a particular MDN that is not within the HLR502, the second CLR504, or the third CLR506, the AAA module500can match the prefix of the MDN to the at least one MDN prefix in order to determine a preferred call path destination for establishing a call outside of the DMA network provided by the DMA in which the AAA module500is embedded. Accordingly, if a user wishes to save money, the user can choose to make calls outside of the DMA network via a VoIP interface. In another example, if a user wishes to have a higher call quality, the user can choose to make calls outside of the DMA network via an ISDN interface.

Referring toFIG. 6, a method of determining a preferred call path for calls to be routed outside of a DMA network is shown and commences at block600. At block600, a DMA registers a mobile subscriber within a home location register (HLR) of the DMA. At block602, the DMA receives a call directed to a destination mobile directory number (MDN) that is not within any community location register (CLR) stored within the DMA. In a particular embodiment, this is an indication that the call is being made to a mobile directory number that is outside of a DMA network provided by one or more DMAs. Moving to block604, the DMA determines a preferred call path based on the prefix of the MDN. In a particular embodiment, the DMA can match the prefix of the MDN with an MDN prefix within a destination preference register (DPR) stored within the DMA in order to determine a hierarchy of preferred call paths for routing the call to the MDN. In a particular embodiment, the MDN is a ten digit telephone number, e.g., 222-333-4444, and the prefix of the MDN can be the first three digits of the number, e.g., 222. Further, in a particular embodiment, the preferred call path can be placed over a VoIP interface, an ISDN interface, or an MSC interface.

Proceeding to block606, the DMA determines whether an interface associated with a selected first preferred the call path is available. If so, the method continues to block608and the DMA establishes the call to the MDN outside of the DMA network via a DMA server that routes the call over the preferred call path. The method then ends at state610. For example, with reference toFIG. 2, if the first subscriber208of the first DMA202includes a first preferred call path that is set to ISDN and the ISDN interface at the third DMA206is available, a call from the first subscriber208of the first DMA202to an external device can be routed to the third DMA206. In turn, the third DMA206can route the external device via the ISDN interface224.

Returning to decision step606, if the first preferred call path is not available, the DMA determines the next preferred call path for the matching MDN prefix within the DPR. The method then returns to decision step606and continues as described herein. Again, with reference toFIG. 2, if the ISDN interface224is unavailable, a call to an external device can be routed to the first DMA202, which can route the call to the external device via the MSC interface220. Additionally, if the ISDN interface224and the MSC interface220is unavailable, a call to an external device can be routed to the second DMA204, which can route the call to the external device via the VoIP interface. In a particular embodiment, if none of the preferred call paths are available, the DMA can indicate that the call cannot be connected.

Referring toFIG. 7, a method of establishing communication via a distributed mobile architecture (DMA) is shown and commences at block700. At block700, the DMA registers a first mobile subscriber within the home location register (HLR) of the DMA. Next, at block702, the DMA registers a second mobile subscriber within the home location register (HLR) of the DMA. Moving to block704, the DMA receives a call from the first mobile subscriber to the second mobile subscriber. At block706, the DMA locates the first mobile subscriber within the home location register of the DMA. Next, at block708, the DMA locates the second mobile subscriber within the home location register of the DMA. Proceeding to block710, the DMA connects the call between the first mobile subscriber and the second mobile subscriber via one or more local IP addresses within the DMA. The method then ends at state712.

FIG. 8depicts a method of establishing communication via a first distributed mobile architecture (DMA) and a second DMA. Beginning at block800, the first DMA registers a first mobile subscriber within a home location register (HLR) of the first DMA. At block802, the second DMA registers a second mobile subscriber within the home location register (HLR) of the second DMA. Thereafter, at block804, the first DMA pre-fetches the home location register (HLR) information from the second DMA and stores it within a second community location register (CLR) at the first DMA. In a particular embodiment, the first DMA and the second DMA can be linked to each other via an IP network.

Moving to block806, the first DMA receives a call from the first mobile subscriber to be routed to the second mobile subscriber. At block808, the first DMA locates the first mobile subscriber within the home location register (HLR) of the first DMA. Proceeding to block810, the first DMA locates the second mobile subscriber within the second community location register (CLR) associated with the second DMA. At block812, the first DMA sends a location update request (LocUpdate) to the second DMA. Next, at block814, the first DMA receives an acknowledgement from the second DMA. In an illustrative embodiment, the acknowledgement includes the current address of the second mobile subscriber within the second DMA. Continuing to block816, the first DMA connects the first mobile subscriber to the second mobile subscriber via the first DMA and the second DMA by assigning an IP address at both the first DMA and the second DMA. The method then ends at state818.

Referring toFIG. 9, a method of establishing communication between a first mobile subscriber and a second mobile subscriber that is roaming is shown and commences at block900. At block900, a first distributed mobile architecture (DMA) registers a first mobile subscriber within a home location register (HLR) of the first DMA. At block902, a second DMA registers a second mobile subscriber within a home location register (HLR) of the second DMA. Moving to block904, the first DMA receives the home location register (HLR) information from the second DMA and stores it within a second community location register (CLR) at the first DMA.

Proceeding to block906, a third DMA registers the second mobile subscriber within a visitor location register (VLR) of the third DMA. In a particular embodiment, this indicates that the second mobile subscriber has roamed into a coverage area controlled by the third DMA. At block908, the third DMA sends the registration information of the second mobile subscriber to the second DMA.

Moving to block910, the first DMA receives a call from the first mobile subscriber to be routed to the second mobile subscriber. Thereafter, at block912, the first DMA locates the first mobile subscriber within the home location register (HLR) of the first DMA. At block914, the first DMA locates the second mobile subscriber within the second community location register (CLR) that is associated with the second DMA.

Proceeding to block916, the first DMA sends a location update request (LocUpdate) to the second DMA. At block918, the second DMA sends the location update (LocUpdate) to the third DMA. Then, at block920, the second DMA receives an acknowledgement from the third DMA. In a particular embodiment, the acknowledgement includes a current address of the second mobile subscriber within the third DMA. For example, the third DMA can retrieve the current address of the second mobile subscriber from the VLR within the third DMA. Continuing to block922, the first DMA receives the acknowledgement from the second DMA with the address of the second mobile subscriber. Next, at block924, the first DMA connects the first mobile subscriber to the second mobile subscriber via the first DMA and the third DMA. For example, an IP address at the third DMA is assigned to the call and is used to route the call over an IP network between the first DMA and the third DMA. The method then ends at state926.

Referring toFIG. 10, an exemplary, non-limiting embodiment of a telecommunications system is shown and is generally designated1000. As shown, the system includes one or more DMAs1002that are connected to a wireless carrier's central MSC1004. The DMA(s)1002can be connected to the MSC1004via an E1 CCS (G.703, G732) connection, or any other applicable connection. The MSC1004, in turn, is connected to a code division multiple access (CDMA) network1006.FIG. 10further shows that the DMA(s)1002can be connected to a switching transfer point (STP)1008of a stand-alone carrier. As shown, the DMA1002can be connected to the STP1008via an IS-41+IS-880 (DS0) connection, or an ISUP ITU N7 connection.

As further depicted inFIG. 10, the STP1008can be connected to a short messaging service (SMS) server1010in order to provide text-messaging capabilities for the mobile communication devices using the system1000shown inFIG. 10. Additionally, the STP1008can be connected to a home location register (HLR)1012, a pre-paid wireless server1014and an international roaming network1016in order to provide pre-paid services and roaming between multiple countries.FIG. 10shows that the DMA(s)1002can be connected to the PTSN1018via an E1 CCS (G.703, G732) connection, or any other appropriate connection.

Referring toFIG. 11, a wireless local loop (WLL) system is portrayed and is generally designated1100. As illustrated inFIG. 11, the system1100includes a DMA1102that is connected to a BTS1104. The BTS1104, in turn, is connected to an antenna1106. The antenna1106provides cellular coverage for one or more subscribers1108within transmission distance of the antenna1106.FIG. 11indicates that the system1100can further include a data network connection1110from the DMA1102. The data network connection1110can connect the DMA1102to the PSTN via an ISUP/ISDN signaling connection on an SS7 link set or a T1/E1 wireless connection. Further, the data network connection1110can be an IEEE 802.11 connection between the DMA1102depicted inFIG. 11and other DMAs not shown. The DMA1102can beneficially utilize existing infrastructure used for cellular and SMS data services.

FIG. 12shows a multi-WLL system, generally designated1200. As shown, the system1200includes a plurality of WLLs1202. Each WLL1202can include a DMA1204and an antenna1206connected thereto to provide a cellular coverage site around the antenna1206. As illustrated inFIG. 12, the WLLs1202can be interconnected via a wireless local area network (WLAN), or a wide area network, such as a microwave connection. Moreover, a DMA1204within one of the WLLs1202can provide a back-haul connection1208to the PSTN1210. This type of deployment scenario can greatly reduce the costs associated with a wireless system. Since the DMAs1204are connected to each other via the WLAN or microwave connections, the relatively expensive inter-site back-haul component is removed. Further, using the hand-off logic, the DMAs1204can enable roaming between the WLLs1202and can further provide roaming to an external wireless or other network.

Referring toFIG. 13, a telecommunications system is depicted and is designated1300. As illustrated inFIG. 13, the system1300includes a DMA1302that can be connected to a plurality of BTSs1304. Each BTS1304can provide cellular coverage for one or more mobile communication devices1306, e.g., one or more mobile handsets configured to communicate via the DMA1302.FIG. 13further shows that the DMA1302can be connected to an MSC1308, such as an MSC of an existing cellular system. The DMA1302can be connected to the MSC via an IS-41subset or a MAP subset over a wireless E1/T1 connection. With this implementation, the DMA1302can extend an existing cellular network when connected to an existing cellular system MSC1308.

FIG. 14shows an additional telecommunications system, generally designated1400. As shown, the system1400includes a city area coverage site1402and an urban fringe/nearby village coverage site1404. In an exemplary, non-limiting embodiment, the city area coverage site1402includes a first MSC/BSC center1406connected to a second MSC/BSC center1408. Also, a first representative BTS1410and a second representative BTS1412are connected to the first MSC/BSC center1406. The particular deployment of equipment is configured to provide adequate cellular coverage for mobile communication devices within the city area coverage site1402.

As illustrated inFIG. 14, the urban fringe/nearby village coverage site1404includes a DMA1414having a plurality of BTSs1416connected thereto. The DMA1414can provide hand-off of calls between the BTSs1416and can switch calls made between the BTSs1416locally. However, the DMA1414within the urban fringe/nearby village coverage site1404can also connect telephony traffic to the first MSC/BSC center1406within the city area coverage site1402via a data network connection1418. In one embodiment, the data network connection can be an E1 connection, a T1 connection, a microwave connection, or an 802.11 connection established via an IS-41 subset or MAP subset. The deployment of a DMA1414in a location such as that described above, i.e., in urban fringe or in a nearby village, and the connection of the DMA1414to an MSC/BSC center1406in a city area, can provide service to potential wireless customers that typically would not receive cellular coverage from the city area cellular coverage site1402. Thus, new subscribers receive access to wireless communication service and can further communicate with wireless customers within the city area cellular coverage site1402.

Referring now toFIG. 15, another telecommunications system is depicted and is designated1500. As illustrated inFIG. 15, the system1500includes a DMA1502that can be connected to a plurality of BTSs1504. Each BTS1504can provide cellular coverage for one or more mobile communication devices1506.FIG. 15further shows that the DMA1502can include a data network connection1508that provides a back-haul connection to the PSTN1510. In one embodiment, the data network connection can be an E1 connection, a T1 connection, a cable connection, a microwave connection, or a satellite connection. Moreover, the system1500depicted inFIG. 15can be deployed using CDMA IS-95, CDMA 1X, GSM/GPRS, W-CDMA, or other industry standard technologies.

Using a single back-haul connection greatly minimizes costs associated with the wireless communication network. Further, the system1500shown inFIG. 15can be deployed relatively rapidly and can be maintained remotely. Additionally, with the inclusion of the OAMP module540(FIG. 5) and the AAA module528(FIG. 5), subscriber accounts can be managed locally and billing can be performed locally, i.e., within the DMA1502. Moreover, as the number of subscribers increase, the size of the system can be increased modularly, e.g., by adding DMAs, corresponding BTSs, and the appropriate connections.

FIG. 16illustrates an in-building telecommunications network that is generally designated1600.FIG. 16depicts a structure1602, e.g., an office building, a commercial building, a house, etc. An enterprise local area network (LAN)1604is installed within the building1602. A micro-BTS1606is connected to the enterprise LAN1604. Moreover, a voice mail server1608and plural enterprise services servers1610are connected to the enterprise LAN1604. In an exemplary, non-limiting embodiment, the enterprise services servers1610can include a dynamic host configuration protocol (DHCP) server, a radius server, a domain name server (DNS), etc. As depicted inFIG. 16, a plurality of phones1612, e.g., IP desk phones can be connected to the enterprise LAN1604.

FIG. 16further indicates that an office DMA1614can be connected to the enterprise LAN1604. The office DMA1614can also be connected to the PSTN1616, which, in turn, can be connected to a cellular voice and data network1618. The enterprise LAN1604can also be connected to the cellular voice and data network1618via an Internet protocol (IP) network1620. A signaling system seven (SS7) network1622can be connected to the cellular voice and data network1618and the IP network1620.FIG. 16also depicts an SS7 gateway1624between the SS7 network1622and the IP network1620and a firewall1626between the enterprise LAN1604and the IP network1620.FIG. 16shows a wireless communication device1628in communication with the cellular voice and data network1618and the micro-BTS1606.

Referring toFIG. 17, a mobile in-field telecommunications system is depicted and is generally designated1700. As depicted, the system1700includes a plurality of mobile cellular coverage sites1702. Each mobile cellular coverage site1702includes a vehicle1704in which a field DMA1706is disposed. Moreover, a BTS1708is disposed within each vehicle1704and is in direct physical connection with the field DMA1706, e.g., by a wire or cable connected there between. The field DMA1706and the BTS1708can be removably installed within the vehicle1704or permanently affixed therein.FIG. 17further indicates that each BTS1708can include an antenna1710that is designed to communicate with mobile communication devices. Also, each field DMA1706includes an antenna1712. In an exemplary, non-limiting embodiment, the field DMAs1706can communicate wirelessly with each other via the antennae1712, e.g., via 802.11a, 802.11b, microwaves, or other wireless link.

The mobile cellular coverage sites1702can be deployed to provide a temporary web of cellular coverage for a plurality of mobile communication devices, e.g., devices carried by soldiers during a battle. The mobile in-field communications system1700can be recalled, moved, and re-deployed as necessary. Further, the system can include a wireless connection, e.g., 802.11a, 802.11b, microwaves, to the PSTN1714.

Referring toFIG. 18, still another telecommunications system is illustrated and is generally designated1800. As depicted inFIG. 18, the system1800includes a DMA1802that is connected to a BTS1804. The BTS1804, in turn, is connected to an antenna1806.FIG. 18further illustrates that a first satellite transceiver1808is also connected to the DMA1802. The first satellite transceiver1808communicates with a second satellite transceiver1810via a satellite1812. Additionally, the second satellite transceiver1810includes a data network connection1814, e.g., a T1 connection, or an E1 connection. The satellite transceivers1808,1810and the satellite1812can provide a backhaul connection for the DMA1802. Or, the satellite transceivers1808,1810and the satellite1812can connect the DMA1802to an additional DMA (not shown).

FIG. 19shows yet another telecommunications system that is generally designated1900. As illustrated inFIG. 19, the system includes a DMA1902that is connected to a first satellite transceiver1904. Moreover, the DMA1902includes a primary network connection1906, e.g., a T1 connection, or an E1 connection, and a secondary network connection1908, e.g., an IP connection.FIG. 19shows that the first satellite transceiver1904communicates with a second satellite transceiver1910and a third satellite transceiver1912via a satellite1914. Each of the second and third satellite transceivers1910,1912is connected to an interworking unit (IWU)1916via a data network connection1918, e.g., an IP connection. Each IWU1916is connected to a BTS1920, which in turn, is connected to an antenna1922. The satellite transceivers1904,1910,1912provide an IP network extension for the DMA1902. Moreover, in the deployment illustrated inFIG. 19, the DMA1902can act as a centralized micro-switch for handling calls received at the antennas1922and transmitted via the second and third satellite transceivers1910,1912.

Referring toFIG. 20, another telecommunications system is depicted and is designated2000. As shown, the system2000includes a DMA2002having a primary network connection2004. Moreover, the DMA2002can be connected to a plurality of IWUs2006. In an exemplary, non-limiting embodiment, the DMA2002can be connected to each IWU2006via a secondary network connection2008, such as a category five (Cat 5) cable connection, a microwave connection, or a WLAN connection. Further, each IWU2006is connected to a BTS2010and each BTS2010, in turn, is connected to an antenna2012. Each BTS2010can be a 3-sector BTS. In the deployment depicted inFIG. 20, the DMA2002can act as a centralized micro-switch that can be used to handle telephony traffic received at the antennae2012.

FIG. 21illustrates yet another embodiment of a communications system, designated2100. As shown, the system2100includes an airplane2102in which a DMA2104is installed. As shown, the DMA2104is coupled to a BTS2106and a first satellite transceiver2108.FIG. 21also shows a mobile communication device2110within the airplane2102. The mobile communication device2110can be in wireless communication with the BTS2106.

In a particular embodiment, the first satellite transceiver2108can communicate with a second satellite transceiver2112via a satellite2114. As shown, the second satellite transceiver2112can be connected to a terrestrial server gateway2116, e.g. a DMA gateway, that 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. The OMP2118, the CDR212, and the VRL-GW2122can be separate from or incorporated within the server gateway2116.FIG. 21further shows that the server gateway2116can be connected to a first mobile switching center (MSC)2124that is coupled to a second MSC2126.

Accordingly, the system2100shown inFIG. 21can allow a user in the airplane2102to communicate with a ground based telephone. For example, the mobile communication device2110can communicate with the BTS2106, which, in turn, can communicate with the first satellite transceiver2108via the DMA2104. Further, the first satellite transceiver2108can transmit the call to a ground based communication system via the second satellite transceiver2112and the satellite2114.

FIG. 21shows a single airplane, however, multiple airplanes can be configured as described herein to provide communication from multiple airplanes to ground based telephones. Further, airplane-to-airplane communication can be provided. Additionally, the system2100can include other airborne vehicles, e.g., blimps.

FIG. 22illustrates yet another embodiment of a communications system, designated2200. As shown, the system2200includes a ship2202in which a DMA2204is installed. As shown, the DMA2204is coupled to a BTS2206and a first satellite transceiver2208.FIG. 22also shows a mobile communication device2210within the ship2202. The mobile communication device2210can be in wireless communication with the BTS2206.

In a particular embodiment, the first satellite transceiver2208can communicate with a second satellite transceiver2212via a satellite2214. As shown, the second satellite transceiver2212can be connected to a terrestrial server gateway2216, e.g. a DMA gateway, that can provide connectivity to an operations and management platform (OMP)2218, a call detail record (CDR)2220, and a visitor location register gateway (VLR-GW)2222. The OMP2218, the CDR222, and the VRL-GW2222can be separate from or incorporated within the server gateway2216.FIG. 22further shows that the server gateway2216can be connected to a first mobile switching center (MSC)2224that is coupled to a second MSC2226.

Accordingly, the system shown inFIG. 2200can allow a user within the ship2202to communicate with a ground-based telephone. For example, the mobile communication device2210can communicate with the BTS2206, which, in turn, can communicate with the first satellite transceiver2208via the DMA2204. Further, the first satellite transceiver2208can transmit the call to a ground based communication system via the second satellite transceiver2212and the satellite2214.

FIG. 22shows a single ship, however, multiple ships can be configured as described herein to provide communication from multiple ships to ground based telephones. Further, ship-to-ship communication can be provided. Additionally, the system2200can include other waterborne vehicles.

Referring toFIG. 23, a method of deploying a distributed management architecture server is shown and commences at block2300wherein during deployment, the succeeding steps are performed. At block2302, the DMA is moved to a desired location proximate to a BTS. Moving to block2304, the DMA is opened. For example, if the DMA is the DMA shown inFIG. 1, the latch is unlocked and the lid is rotated about the hinges into the open position. Proceeding to block2306, a physical connection is established between the DMA and the BTS, e.g., the BTS is coupled to the DMA via a wire.

Continuing to block2308, the DMA is activated, e.g., powered on. At block2310, a network connection is established with another remote DMA. In a particular embodiment, the network connection is a peer-to-peer connection between the DMAs. Moving to block2312, DMA software within the DMA is activated. Thereafter, at decision step2314, it is determined whether the system is operational. That decision can be a performed by the DMA, e.g., by a self-diagnostic routine or module within the DMA. Alternatively, that decision can be determined manually by a technician. If the system is not operational, a system check is performed at block2316. In a particular embodiment, the system check performed at block2316is performed by a self-diagnostic routine or module within the DMA. On the other hand, a technician can perform the system check. After the system check, the logic then returns to decision step2314and continues as described herein. At decision step2314, if the system is operational, the method proceeds to block2318and call transmission is allowed. The method then ends at state2320.

Referring toFIG. 24, a method of deploying a distributed management architecture server is shown and commences at block2400wherein a direct physical connection between a first DMA and a base transceiver station is disconnected. At block2402, the first DMA is removed. Proceeding to block2404, a second DMA is moved to a location that is substantially proximate to the base transceiver station. At block2406, the second DMA is opened. For example, if the DMA is the DMA shown inFIG. 1, the latch is unlocked and the lid is rotated about the hinges into the open position. Next, at block2408, a direct physical connection is established between the second DMA and the base transceiver station.

Continuing to block2410, the second DMA is activated. At block2412, a network connection is established between the second DMA and another remote DMA. In a particular embodiment, the network connection is a peer-to-peer IP connection between the DMAs. Further, in a particular embodiment, the peer-to-peer connection is established via a private IP network. At block2414, DMA software within the second DMA is activated.

Proceeding to decision step2416, it is determined whether the system is operational. That decision can be a performed by the second DMA, e.g., by a self-diagnostic routine or module within the second DMA. Alternatively, the decision can be determined manually by a technician. If the system is not operational, a system check is performed at block2418. In a particular embodiment, the system check performed at block2418is performed by a self-diagnostic routine or module within the second DMA. On the other hand, a technician can perform the system check. After the system check, the logic then returns to decision step2416and continues as described herein. At decision step2416, if the system is operational, the method proceeds to block2420and call transmission is allowed via the second DMA. The method then ends at state2422.

With the configuration of structure described above, the present disclosure provides a flexible telecommunications device, i.e., a DMA, that is distributive and associative, i.e., it can operate stand-alone or seamlessly within an existing cellular or other network. Moreover, the DMA can be integrated with virtually any third party base station. The DMA can operate with multiple air interfaces including CDMA IS-95, CDMA 1X, CDMA EVDO, GSM, GPRS, W-CDMA, 802.11 (Wi-fi), 802.16 (Wi-fi), etc. Further, the DMA can provide integrated prepaid billing, OAMP, network management, and AAA functionality. The DMA can include a Java based user interface and feature configuration system. Also, the DMA can provide real time call metering, call detail record (CDR) generation, and real time call provisioning. The DMA may be implemented in a relatively small footprint and has a relatively low power requirement. Further, the DMA may be implemented using inexpensive and widely available computer equipment.

With one or more of the deployment configurations described above, the present system provides mobile to landline calls from mobile handsets within a DMA cellular coverage area. Also, mobile to landline calls can be made from mobile handsets roaming into DMA coverage areas. Mobile to mobile calls can be made from home/roaming handsets to DMA handsets and vice versa. Further, mobile to IP calls and IP to mobile calls can be made from within a DMA coverage area. IP to IP calls can be made from any DMA handset to any IP phone. Additionally, IP to landline calls and landline to IP calls can be made from a DMA handset to any phone. Further, land-line to mobile calls to DMA handsets can be made.

The systems described above can support call forwarding, call waiting, 3-way calling caller ID, voice mail, and mobile to mobile SMS service, i.e., text messaging. Further, the systems described above can provide broadcast SMS service, mobile to land high-speed IP data (1X or GPRS) service and mobile-to-mobile high speed IP data (1X or GPRS) service. Also, the systems described above can provide IP-PBX capability.

Further, one or more of the illustrated systems can provide IP transport between distributed elements, e.g., DMAs. Packet back-haul from BTS to RAN can be provided. Further, the control logic within the DMAs can be distributed and associated. Associated systems can be redundant, self-healing, self-organizing, and scalable. Distributed systems can be “snap-together,” i.e., a DMA can be linked to a previously deployed DMA in order to broaden, or otherwise extend, cellular coverage. Further, distributed systems can be de-centralized to avoid single points of failure.

One or more of the systems described above can also provide soft and softer call handoffs on the same frequency interfaces. Also, soft handoffs can be provided on different systems. Further, a DMA based system can operate stand-alone with a billing system provided by a DMA and CDR generation. Or, a system can use the SS7 network to pass CDRs to a central switch for integrated billing and operation with an existing network.