An enterprise mobile network for providing cellular wireless service using licensed radio frequency spectrum and internet protocol backhaul

ES 2 554 541 T3

DESCRIPTION

An enterprise mobile network to provide a wireless mobile (cellular) telephone service using a licensed radio frequency spectrum and an Internet Protocol backhaul

CROSS REFERENCE WITH THE RELATED APPLICATION

This application claims the benefit of the United States provisional patent application, US Provisional Patent Application Serial No. 61 / 027,363, filed February 8, 2008.

This application is related to the following patent applications:

United States Patent Application Serial No. _ / _, _ (Attorney Docket No. 100.894US01), filed on the date included in this document, entitled MULTIPLE-TRX PICO BASE ESTACIÓN FOR PROVIDING IMPROVED WIRELESS CAPACITY AND COVERAGE IN A BUILDING.

United States Patent Application Serial No. _ / _, _ (Attorney Docket No. 100.111US01), filed on the date included in this document, entitled AN ENTERPRISE MOBILE NETWORK FOR PROVIDING CELLULAR WIRELESS SERVICE USING LICENSED RADIO FREQUENCY SPECTRUM AND SUPPORTING MULTIPLEDEVICE RING FOR INCOMING CALLS .; Y

United States Patent Application Serial No. _ / _, _ (Attorney Docket No. 100.1119US01), filed on the date included in this document, entitled AN ENTERPRISE MOBILE NETWORK FOR PROVIDING CELLULAR WIRELESS SERVICE USING LICENSED RADIO FREQUENCY SPECTRUM AND THE SESSION INITIATION PROTOCOL .

BACKGROUND

In conventional wireless mobile phone (cellular) networks, typical initial development involves the installation of macro base stations in order to provide cellular wireless coverage for mobile units. A macro base station is made up of multiple transceiver units, which emit relatively high power (i.e. 10 watts or more) to its antenna (s) and which are communicatively coupled to a telephone network via a backhaul connection. The backhaul connection includes a T1 connection (in the United States) or an E1 connection (in Europe) to a base station controller (BSC) which is, in turn, connected to a mobile switching center (MSC) and to an external telephone network. Because macro base stations emit high power, they can provide large coverage areas.

The capacity of a macro base station can be expanded to a limited degree by adding transceivers and antennas to the macro base station. Macro base stations can also be added additionally to the cellular (mobile phone) network. However, these measurements have limitations due to interference between macro base stations as a consequence of their large coverage areas and high emission power.

One solution to this capacity problem has been to add micro or pico base stations to the cellular (mobile phone) network. Like a macro station, a micro base station comprises multiple transceiver units and is communicatively coupled to a telephone network via a backhaul connection to the BSC and the MSC. However, compared to the power output of a macro base station, a micro base station emits relatively low power (i.e. in the 1-2 watt range) to its antenna (s). A conventional pico base station is also typically communicatively coupled to a telephone network via a backhaul connection, but consists of only one transceiver unit and typically uses an Internet Protocol (IP) backhaul connection in which the voice signals are converted into IP packets. A conventional pico base station also puts out even less power (that is, less than a watt) to its antenna. The pico base stations can be located indoors, such as in offices, shopping malls, convention centers, and airports. In addition to having low power output levels, micro and pico base stations for Code Division Multiple Access (CDMA) and broadband wireless protocols also support lower capacity levels than macro base stations due to their reduced processing power. .

A disadvantage of this approach to adding capacity to the network is that the micro or pico base stations are located at the sites where the additional capacity is required and therefore requires additional infrastructure for each site. Also, they are not easily accessible for maintenance and updates. Also, because an additional backhaul link is required for each micro or pico base station, backhaul links tend to increase installation and maintenance costs. On the other hand, the coverage provided by the pico base stations is generally limited and often the problem in developments in interior spaces is due to the walls and the configuration of the buildings.

ES 2 554 541 T3

Another issue with covering large areas with peak cells is that capacity demand is often dynamic with respect to both location and load. As users move around an area, the capacity demands will change for different locations. Network designers often provision excess capacity, which can cause many peak cell resources to be underutilized. Also, for wider bandwidth technologies such as Universal Mobile Telecommunications System (UMTS), Worldwide interoperability for Microwave Access (WiMAX) and Long Term Evolution (LTE) technologies, which spread multiple peak cells with lower emission of power and ability to cover larger areas is inefficient due to co-channel interference created by neighboring cells. A trunking gain can be achieved by distributing a higher level of capacity over the entire coverage area instead of individually developed sheets of capacity at various points in the total coverage area.

The United States patent application document US Patent Application Publication No. US 2002/0191595 A1 entitled Providing Communications Capabilities to Mobil Devices at an Enterprise describes a softswitch in a COR Network Operations Center (COR (NOC)) in communication data with one or more companies. The softswitch performs the calling process, mobility management, and media connection switching and signaling in order to provide communication capabilities including basic and enhanced calling features for mobile devices in enterprises. . The softswitch routes control signals for calls between the companies and the COR (NOC), as well as routes the call media on the most efficient point-to-point paths between the devices on the calls. This routing reduces the amount of bandwidth required between companies and COR (NOC) and provides economies of scale, thereby enabling a centralized COR (NOC) to efficiently support multiple companies. Every company has a network based on an Internet Protocol (IP) coupling one or more base station transceivers in order to provide coverage to mobile devices. Each company optionally has a media gateway (Gateway) connected to the IP network and a change of private branch and / or a public telephone network.

RESUME

An embodiment of the present invention is directed to a mobile network for the company to provide the wireless service within a coverage area associated with a company that is using a licensed radio frequency spectrum. The mobile network for the company consists of a subsystem with a base station developed at the company premises in order to provide wireless capability within the coverage area that is using the licensed radio frequency spectrum. The mobile network for the company also has a local mobile switching subsystem deployed at the company's facilities, where the local mobile switching subsystem is communicatively coupled to a public land mobile network, where the public land mobile network comprises a public mobile switching subsystem. The base station subsystem is communicatively coupled to the local mobile switching subsystem using an Internet Protocol (IP) network. The invention is characterized in that the mobile network of a company includes hybrid subscribers, each of which is a local subscriber of the mobile network of a company and has a respective local mobile phone number for use with the mobile network of the company and is a public subscriber of the public land mobile network and has a respective public mobile phone number for use with the public land mobile network. The local mobile switching subsystem is configured to function as a home location register for the hybrid subscribers in connection with the local mobile phone numbers of the hybrid subscribers. The local mobile switching subsystem is configured to function as a visitor location register and has the function of a public mobile switching subsystem as a home location register for the hybrid subscribers in connection with the public mobile phone numbers of the hybrid subscribers. .

Another embodiment is directed to a mobile network of a company for the purpose of providing the wireless service within a coverage area associated with a company using the licensed radio frequency spectrum. The company's mobile network includes a base station subsystem deployed at a company facility in order to provide wireless capability within the coverage area using licensed radio frequency spectrum. The company's mobile network further includes a mobile switching subsystem deployed in an office of a service provider operating a public land mobile network. The mobile switching subsystem is communicatively coupled to the public land mobile network. The base station subsystem is communicatively coupled to the mobile switching subsystem using an Internet Protocol (IP) network. The mobile switching subsystem is configured to function as a mobile switching center (MSC) and a visitor location register (VLR) for roaming subscribers and local subscribers of the company. The mobile switching subsystem is configured to function as a home location registry (HLR) and mobile gateway switching center (GMSC) for the company's local subscribers.

Another embodiment is directed to a mobile network of a company to provide the wireless service within a coverage area associated with a company using the licensed radio frequency spectrum. The company's mobile network includes at least one subsystem of a base station, deployed at the company's premises in order to provide wireless capability within the coverage area using the spectrum of

ES 2 554 541 T3 licensed radio frequency. The company's mobile network further includes at least one local mobile switching subsystem deployed at the company's premises that is communicatively coupled with the base station subsystem and a central mobile switching subsystem deployed in an office of a service provider operating a public land mobile network. The central mobile switching subsystem is communicatively coupled to the public land mobile network. The local mobile switching subsystem is communicatively coupled to the central mobile switching subsystem using an Internet Protocol (IP) network. The local mobile switching subsystem is configured to function as a mobile switching center (MSC) and as a visitor location register (VLR) for the coverage area associated with the company. The central mobile switching subsystem is configured to function as a home location registry (HLR) and a mobile gateway switching center (GMSC) for the company's local subscribers.

Another embodiment is directed to a mobile network of a company to provide the wireless service within a coverage area associated with a company using the licensed radio frequency spectrum. The company's mobile network consists of a base station subsystem deployed at the company's premises in order to provide wireless capability within the coverage area using licensed radio frequency spectrum and a mobile switching subsystem deployed in the company's facilities. The mobile switching subsystem is communicatively coupled to the base station subsystem using an Internet Protocol (IP) intranet deployed in the enterprise. The mobile switching subsystem is communicatively coupled to a public land mobile network. The call and data signaling is communicated between the base station subsystem and the mobile switching subsystem over the IP intranet.

Another embodiment is directed to a mobile network of a company to provide the wireless service within a coverage area associated with a company using the licensed radio frequency spectrum. The company's mobile network includes a base station subsystem deployed at the company's premises in order to provide wireless capability within the coverage area using licensed radio frequency spectrum and a mobile switching subsystem deployed in the company's facilities. The mobile switching subsystem is communicatively coupled to the base station subsystem using an Internet. The mobile switching subsystem is communicatively coupled to a public land mobile network over the Internet. The mobile switching subsystem and the base station subsystem are communicatively coupled to the Internet through at least one firewall.

Details of the various embodiments of the claimed invention are set forth in the accompanying drawings and in the description below. Other features and advantages will become apparent from the description, drawings, and claims.

DRAWINGS

Figure 1 illustrates one embodiment of a system for providing improved wireless capability and coverage in a building.

Figure 2 is a block diagram of one embodiment of a multiple TRX pico base station. Figure 3 is a block diagram of one embodiment of a multiple TRX pico base station. Figure 4 is a block diagram of one embodiment of a multiple TRX pico base station. Figure 5 illustrates an example of a distributed architecture for a corporate mobile network. Figure 6 illustrates an example of a distributed architecture for a corporate mobile network. Figure 7 illustrates an example of a distributed architecture for a corporate mobile network. Figure 8 illustrates an example of a distributed architecture for a corporate mobile network. Figure 9 illustrates an example of a distributed architecture for a corporate mobile network.

Figure 10 illustrates an example of a distributed architecture for an enterprise mobile network.

Figure 11 illustrates a usage scenario where the technology described here is used to provide wireless local loop (WLL) service for both voice and data within an enterprise.

Figure 12 illustrates a usage scenario in which the technology described here is used to provide only roaming service within a company.

Figure 13 illustrates a usage scenario where a business mobile network is configured to support both local and hybrid subscribers.

Figure 14 illustrates a usage scenario in which an enterprise mobile network includes a Private A-Link Intelligent Multiplexer (PALIM) switching function.

Figure 15 illustrates an example in which a company mobile network is implemented through two offices of a company.

Figure 16 illustrates an example where two separate enterprise mobile networks share a GSN and a TMS (MSS).

Figure 17 illustrates an example where a CSP (PBX) with IP is integrated with a mobile network of a company.

Figure 18 illustrates an example in which an access gateway (Gateway) integrates with a mobile network of a company.

Figure 19 illustrates an example of a company mobile network.

ES 2 554 541 T3

Figure 20 illustrates an example of a company mobile network.

Figure 21 illustrates an example of a company mobile network.

Figure 22 illustrates an example of a company mobile network.

Figure 23 illustrates how a mobile device is registered with the IP-based CSP (PBX) of Figure 22 in connection with a location update.

Figure 24 illustrates how a mobile device that is camped on the company mobile network of Figure 22 can make a call to a device connected to the PSTN (PSTN).

Figure 25 illustrates how a call that is made to a number associated MSIS-DN with a local subscriber can be completed in the company's mobile network shown in Figure 22.

Figure 26 illustrates how to make a call that is made to an extension number of a CSP (PBX) associated with a local subscriber in a company's mobile network shown in Figure 22.

Figure 27 illustrates an example of a company mobile network.

Figure 28 illustrates an example of how a phone call made to a CSP extension (PBX) associated with a local subscriber of a company is handled in the mobile network of the company shown in Figure 27.

Figure 29 illustrates an example in which someone uses a SIP landline to call a user's CSP (PBX) extension.

Figure 30 illustrates an example in which someone uses a mobile phone to call an ISDN NEM number (MSISDN) of a local user.

Figure 31 illustrates an example in which someone uses a UC unified communications endpoint in order to call a user's UC endpoint.

Figure 32 illustrates an example where a computer / phone integration (CTI) application installed at a UC endpoint is used to remotely control a mobile device.

Figure 33 illustrates an example of the development of a mobile network of a company that includes a CSP (PBX) with virtual IP.

Figure 34 is illustrating the use of the security functionality of the Gateway (SEG) in a mobile network of a company.

Figure 35 illustrates how SIP server functionality can be integrated into a TMS (MSS) as part of an FMC solution.

Figure 36 illustrates how a SIP User Agent can be implemented in a base station subsystem.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

Figure 1 illustrates one embodiment of a system 100 to provide enhanced wireless capability and coverage in a building 134. In the particular embodiment shown in Figure 1, the system 100 consists of a multiple TRX pico base station 102 that it is communicatively coupled to the public land mobile telephone network (PLMN) 104 via a backhaul link 106. Within the network 104, the backhaul link 106 is coupled to a base station controller (BSC) 108, which, in turn, is coupled to a network switching subsystem (NSS) 110. The NSS 110 is coupled to a public switched telephone network (PSTN) 112 (eg, for voice communications) and to other public land mobile networks 105. Also, the BSC 108 is communicatively coupled to one or more data nodes (for example, a Serving GPRS Support Node (SGSN)) in order to communicate communicatively couple the BSC 108 (and the multiple TRX 102 base station peak ). to one or more data networks 114 such as the Internet (eg, for data communications). Although throughout the following description the terms BTS, BSC and BSS are used, it should be understood that the concepts described here can also be applied to the embodiments that make use of network elements that refer to the use of other terms. , such as Node B, eNB, RNC and the radio access network (RAN) that are most frequently associated with the 3G and 4G networks.

The BSC 108 performs various conventional BSC functions, including assigning radio channel, handover of calls between base stations, configuring the multiple TRX 102 peak base station, setting up alarms, and performing management functions. of the network. BSC 108 includes or is communicatively coupled with an appropriate network element (eg, a packet control unit (PCU)) to direct traffic to and from data network 114.

The NSS 110 performs various conventional functions, including circuit switching and providing call features and applications to mobile subscribers, such as ringing and roaming. For example, the NSS 110 typically includes a mobile switching center (MSC) and other functionalities such as a home location register (HLR) and a visitor location register (VLR). In one embodiment, certain of the features conventionally performed by the BSC 108 and NSS 110 may be performed by the TRX 102 pico multiple base station instead. For example, the TRX 102 pico multiple base station may include a local server that is configured with a Linux (or other) operating system in order to implement these functions.

ES 2 554 541 T3

The multiple TRX pico base station 102 consists of multiple transceiver units (TRXs) 116. In one implementation, the multiple TRX base 102 pico base station consists of two TRX 116. However, it should be understood that a larger number may be included. of TRXs in the peak multi-TRX 102 base station (eg 4 TRXs). Each of the TRX 116s is used to output a reduced energy RF channel (specifically, less than one watt). In one implementation, multiple TRXs 116 are implemented as a multi-carrier radio card comprising one or more digital signal processors (DSP) that produce and process upstream and downstream baseband link wireless signals for each of the multiple RF channels supported by multiple TRXs 116, one or more upconverters in order to convert (upconvert) the wireless baseband signals downlinks to the appropriate RF frequencies and one or more down converters in order to convert (down convert) the RF uplink signals received by the radio card from baseband wireless signals for processing by one or more DSPs. Such type of multi-carrier radio card also includes other conventional base station components known to those skilled in the art including, for example, filters and amplifiers (for example, an appropriate amplifier in order to cause the radio card to emit low power RF signals). It should be understood that the various components described here (for example, the amplifiers) can be implemented separately from that type of multiple carrier radio card or TRXs 116. In addition, each of the multiple TRXs 116 can also be implemented from other ways. For example, a separate radio card can be used to implement each of the multiple TRXs 116.

The multiple TRX pico base station 102 consists of a convenient interface 115 for the purpose of communicatively coupling the TRX multiple pico base station 102 (and the TRXs 116 included therein) to the network 104. In one embodiment, the TRX multi-peak base station 102 uses an Internet Protocol (IP) backhaul connection in which voice and data signals are converted into IP packets for communication via the network link. the backhaul 106 to the BSC 108 (eg, using a cable modem or a DSL modem). Alternatively, the TRX multi-peak base station 102 may use a T1 or E1 connection (that is, a Time Division Multiplexing (TDM) connection) for the backhaul link 106. Alternatively, a wireless link ( eg a WIMAX wireless link) in order to provide the backhaul 106 link, which in the case of interface 115 would comprise a suitable WIMAX interface. In this sense, it is observed that only a single link of the backhaul network 106 needs to be provided with the intention of providing service to the multiple TRXs 116 that are included in the multiple TRX 102 peak base station. This is in contrast to the Conventional pico base station developments in which multiple, single TRX pico base stations are deployed, each of which requires a separate backhaul link.

In a GSM implementation of the embodiment shown in figure 1, the GSM A-bis interface is used in order to communicate between the multiple TRX 102 pico base station and the BSC 108 over the network connection of backhaul 106. In such a GSM implementation, the BSC 108 communicates with an MSC on the NSS 110 using the GSM A interface and a BSC packet control unit 108 communicates with an SGSN on the data network 114 using the interface GPRS Gb. In such an application, the various interfaces are implemented in the software running the TRX multi-pico base station 102. A BSC 108 may communicate with one or more TRX multi-pico base stations 102.

Each of the transceiver units 116 communicates on a single bi-directional RF channel of a licensed wireless RF communications band. Each of the channels of this type of bidirectional RF consists of an upstream channel and a downlink channel. In an example implementation, each of the transceiver units 116 of the multiple TRX 102 pico base station transmits and receives 200kHz of GSM uplink and downlink of the RF channels within the 850 MHz frequency band (for example, 824-849 MHz uplink and 869-894 MHz downlink). In another embodiment, each of the transceiver units 116 of the multiple TRX 102 pico base station transmits and receives on the 1.25 MHz, CDMA uplink and downlink RF channels within the 1900 frequency band. MHz (for example, 1850-1910 MHz uplink and 1930-1990 MHz downlink). In other embodiments, the transceiver units 116 support other wireless protocols (eg, other GSM bands, other CDMA bands, and the GPRS, EDGE, UMTS, W-CDMA, LTE, EVDO, CDMA2000, UMB, HSPA, and WIMAX protocols). Furthermore, it should be understood that the TRX 102 multi-pico base station can support multiple and different wireless protocols such that different wireless protocols can be supported by a single TRX 102 multi-mode multi-pico base station. For example, one transceiver 116 can support one wireless protocol while other transceivers 116 can support other wireless protocols.

In the particular embodiment shown in Figure 1, the multiple TRX pico base station 102 is also communicatively coupled to a distributed antenna system (SAD (DAS)) 118. The SAD (DAS) 118 comprises a hub (hub ) multi-port repeater 120 that is communicatively coupled to a plurality of antenna units 122. Each antenna unit 122 includes or is coupled to at least one antenna 124 from which the antenna unit 122 receives and radiates the RF signals.

The SAD (DAS) 118 is used to provide wireless RF coverage from the antenna units 122

ES 2 554 541 T3 located remotely and spatially separated, using the capacity that is provided by the multiple TRX 102 pico base station. This is in contrast to conventional pico base station deployments in which multiple, single TRX pico base stations are located throughout the coverage area (i.e. each single TRX pico base station is co-located with the antenna from which that base station transmits and receives the single RF channel). With the embodiment shown in FIG. 1, the TRXs 116 of the pico base stations 102 are centralized and can be located in a secure location (eg, a closet or a server or utility room).

In the particular embodiment shown in Figure 1, core 120 is communicatively coupled to antenna units 122 via one or more intermediate expansion cores 126. In such an embodiment, core 120 is communicatively coupled to each of expansion cores 126 by one or more cables 128. For example, in an embodiment described herein in connection with FIG. 1, cables 128 are comprised of one or more fiber optic cables. Antenna units 122 are communicatively coupled to expansion core 126 via appropriate cabling 130 (eg, coaxial fine cabling, CATV cabling, or fiber optic cabling). In other embodiments, antenna units 122 may be communicatively coupled to core 120 directly without the use of expansion intermediate cores 126.

In one implementation of such an embodiment, core 120 receives an RF downlink channel from each of the transceiver units 116 included in the multiple TRX 102 peak base station. Core 120 downconverts each of such RF downlink channels at an intermediate frequency (IF) for distribution to antenna units 122. The downconverted IF channels are combined and communicated to each expansion core 126 over a respective fiber link 128 using an analog optical modulator. Each expansion core 126 receives and demodulates the optical signal for the purpose of recovering the combined downlink IF signal, which is then transmitted to each of the antenna units 122 that are coupled to that expansion core 126 using cabling. 130. Each antenna unit 122 receives the combined IF signal and separates the IF signals into separate IF signals for each downlink RF channel received from the multiple TRX peak base station 102. The antenna unit 122 then converts ( upconvert) each such IF signal spaced to its original RF frequency as received from pico base station 102. The upconverted downlink RF signals are then combined and radiated from an antenna 124 coupled to antenna unit 122.

A similar process is done in the uplink direction. In each antenna unit 122, the RF signals that are received from the antenna 124 coupled to that antenna unit 122 are filtered in order to produce an RF uplink channel for each of the transceiver units 116 included in The pico TRX 102 multiple base station. The antenna units 122 downconverts each such intermediate frequency (IF) RF uplink channel for distribution back to the core 120 through an expansion core 126. The downconverted IF channels are combined and communicated to expansion core 126 over a cable 130. Each of the expansion cores 126 combines the various IF channels it receives from the antenna units 122 that are coupled in this way and communicates the combined IF channels with the core 120 over a fiber link 128 using an analog optical modulator. . Core 120 receives and demodulates the optical signal from each expansion core 126 in order to recover the combined IF signal transmitted from that expansion core 126. The combined IF signals recovered from all expansion cores 126 are then combined. The core 120 then separates the combined IF signals into separate IF signals for each RF uplink channel supported by a transceiver unit 116 at the multiple TRX peak base station 102. Core 120 then upconverts each such separate IF signal to its original RF frequency depending on how it is received over the air. Each upconverted RF uplink channel is then communicated with a respective transceiver unit 116 at the multiple TRX peak base station 102.

In other embodiments, signal separation is not required if the IF and RF frequencies are selected such that one block of upconverters and one block of downconverters can be used (instead of using separate, narrow-band converters - upconverters and downconverters-). In the simplest example of such an embodiment, if the system were designed to distribute multiple GSM operators in the 900 MHz band and each carrier was located at the correct frequency offset one with respect to the other, the entire IF spectrum could be converted (upconverted) as a continuous block against having individual narrowband upconverters and also with the conversion (downconversion) of the RF spectrum.

The SAD (DAS) 118 may include one or more of the following filtering, amplifying, wave division multiplexing, duplexing, timing and monitoring functionalities as necessary and as is known in the Art. Also, power can be provided to the antenna units 122 over the wiring 130 such that no additional source of power is needed to power the antenna units 122. An example of a suitable SAD (DAS) 118 is the InterReach FUSION building distributed antenna system which is commercially available from ADC Telecommunications, Inc. of Eden Prairie, Minnesota.

Although a particular type of SAD (DAS) is shown in Figure 1, it should be understood that other types of

ES 2 554 541 T3

SAD (DAS) can be used in other embodiments. Such alternative SAD (DAS) networks and configurations include, without limitation, the use of multiple, single band and SAD IF analog overlay (DAS) networks (for example, using unshielded twisted pair or CAT5 cabling), SAD networks (DAS) do not use any expansion cores, SAD networks (DAS) that make use of radio frequency digital transport and passive SAD networks (DAS). On the other hand, the wireless signals communicated between the multiple TRX base station pico 102 and the antennas 124 can be carried in one or more of the following ways: in analog RF form, in analog IF form, in the form of Analog baseband, in digitized RF form, digitized IF form, and digitized baseband form.

The multiple TRX peak base station 102 and the core 120 of the SADs (DAS) 118 are installed in a building 134 in which coverage and capacity must be provided. Building 134 is not controlled by the service provider that operates that network 104. That is, building 134 is comprised of a customer facility, which is owned, controlled, or otherwise used by a person or entity other than the service provider that operates network 104, such as a company (e.g., a company such as a business, non-profit organization, or government entity). Examples of buildings include, without limitation, office buildings, shopping centers, educational or government buildings, airports, stadiums for sports or entertainment centers, hospitals, single-family homes, condominiums, apartments or hotels or motels.

In one implementation of such an embodiment, the TRX multi-base station peak unit 102 and the core 120 of the SAD (DAS) 118 are installed in a rack of shelves 136 that is included in a utility or server room or closet of the facility. building 134. In the particular embodiment shown in figure 1, at least a part of such equipment is rack mountable. That is, at least a portion of such equipment is packaged to fit within one or more standard shelf racks 136 located within the utility room. Such types of rack racks 136 allow such rack mountable equipment to be stacked on the racks in an efficient, organized and standard manner. An example of such a type of shelf frame is a 19-inch shelf frame (for example, a 19-inch shelf frame that meets one or more of the following standards: Electronic Industries Alliance (EIA) 310-D, Commission Electrotechnical International (IEC) 60297 and Deutsches Instituí für Normung eV (DIN) 41494 SC48D).

In the embodiment shown in FIG. 1, the TRX multiple base station pico 102 and core 120 are rack mountable. That is, each respective chassis in which the various components of the multiple TRX pico base station 102 and core 120 are housed and designed to fit (and be installed) in the rack frame 136. Each chassis includes a correct clamping and structural support elements in order to secure the TRX 102 manifold base station peak and core 120 to the rack frame 136 and in order to support the TRX 102 manifold peak base station. and core 120 when installed in shelf frame 136.

In another embodiment, base station 102 and core 120 are housed within the same physical chassis (eg, the same physical chassis for shelf rack mounting).

Together, the antenna units 122 form one or more coverage areas. Antenna units 122 are distributed throughout building 134 in such a way as to form one or more coverage areas that substantially include occupied areas within building 134.

Mobile communications equipment 132 (eg, a cellular-cell phone) within a coverage area is communicatively coupled to network 104 via one or more of antenna units 122, an expansion core 126, core 120, the multiple TRX pico base station 102 and the backhaul 106.

Centralizing at the TRX 102 pico multi-base station and then distributing the aggregate capacity provided by the TRX 102 multi-peak base station is more efficient in terms of resource utilization, including frequency spectrum, than deployment of pico conventional base stations, which can result in under-utilization of pico cell resources.

The multiple TRX pico base station 102 shown in Figure 1 is described above as to send and receive the RF signals with the SAD (DAS) 118. It should be understood that in other embodiments, the TRX multi-peak base station transceivers 116 102 send and receive other types of signals (which are distributed by the SAD (DAS) 118 and which are ultimately used for the purpose of produce an RF signal in the downlink (downlink) and that were originally received as an RF signal in the uplink (uplink)). For example, the transceivers 116 and the SAD (DAS) 118 can communicate using the IF signals, in which case, on the downlink, the transceivers 116 upconvert the downlink baseband signals. at appropriate IF frequencies and, in the uplink, the SAD (DAS) 118 provides the IF signals to transceivers 116, which downconvert the received IF signals to baseband for processing. Similarly, analog baseband signals or digital data can be communicated between the transceivers 116 and the SAD (DAS) 118 (in which case, in the downlink direction, the RF signals are ultimately produced in the SAD (DAS)

ES 2 554 541 T3

118 and, in the uplink direction, the SAD (DAS) 118 receives the original RF signals from the mobile equipment 132 and processes the RF signals in order to produce the desired signal for communication to the transceivers 116) .

Figure 2 is a block diagram of an alternate embodiment of the TRX 202 multiple base station pico. As in the TRX 102 multiple base station pico shown in Figure 1, the TRX 102 pico base station The multiple TRX 202 shown in figure 2 includes multiple TRXs 116. However, the multiple TRX 202 pico base station of Figure 2 also includes at least a portion of the base station controller functionality 208 necessary in order to control the multiple TRX 116 included in the pico station. multiple base station TRX 202 and to communicate the pico multiple base station TRX 202 with a PLMN (PLMN) 204 (eg, with the NSS 110 and / or the data network 114). In one implementation of such an embodiment, the base station controller 208 functionality is implemented with software running on one or more programmable processors that are included in the multiple TRX 202 pico base station.

In the implementation of a GSM of such an embodiment, the BSC 208 functionality implements at least a part of the GSM A interface in order to communicate with the NSS 110 on the backhaul 106 and implement at least a part of the Gb GPRS interface in order to communicate with a SGSN included in the data network 114.

Otherwise, the articles shown in Figure 2 that are referenced in Figure 2, using the same reference numerals that have been used in Figure 1 are substantially the same as described above in connection with Figure 1.

In other embodiments, the BSC functionality 208 further comprises at least some functionality related to an MSC. Figure 3 is a block diagram of such an alternative embodiment of a multiple TRX 302 pico base station. As with the multiple TRX 102 and 202 pico base stations shown in Figures 1 and 2 , the multiple TRX 302 pico base station shown in Figure 3 comprises multiple TRXs 116. As with the TRX 202 multiple base station pico shown in Figure 2, the TRX 302 multiple pico base station in Figure 3 also includes the base station control functionality 308 needed to control the multiple TRXs 116 included in the pico TRX 302 multiple base station and to communicate the pico TRX 302 multiple base station with a PLMN (PLMN) 304 (for example, with the public NSS 110 and / or a data network 114) of the peak TRX multiple base station. In one implementation of such an embodiment, the base station controller functionality 308 is implemented with software that runs on one or more programmable processors that are included in the multiple TRX 302 pico base station.

The multiple TRX 302 pico base station shown in Figure 3 also includes the functionality of an NSS 310. For example, in the particular embodiment shown in Figure 3, the functionality of NSS 310 implements at least one part of the call switching functionality normally implemented in an MSC (for example, the functionality 340 of the GSM Gateway (MGW) gateway means). In particular, when a mobile device that is in communication with the TRX 302 pico base station (for example, mobile equipment A in Figure 3) calls another mobile device that is in communication with the TRX 302 pico base station. Multiple TRX 302 (for example, Mobile Equipment B in Figure 3) the MGW 340 functionality in the multiple TRX 302 pico base station is capable of switching traffic for that call when instructed to do so, through a public MSC included in the public NSS 110. In this way, the call traffic does not need to be returned back to the public MSC at the public NSS 110 and only the signaling traffic necessary to set up the calls needs to be returned to the public MSC. In such an embodiment, the NSS 310 functionality implements an appropriate interface (for example, the GSM Me interface) between the MGW 340 functionality and the public MSC in order to allow the public MSC to control the MGW 340 functionality over the link. backhaul 106.

In one such embodiment, the functionality of NSS 310 is implemented in software running on one or more programmable processors that are included in the multiple TRX 310 pico base station (for example, the same or more processors running software that implements BSC 308 functionality).

Otherwise, the items shown in Figure 3 that are referenced in Figure 3 with the same reference numerals as those used in Figure 1 are substantially the same as described above in connection with Figure 1 .

In other implementations, other functionality related to an NSS is implemented within the TRX 302 multiple base station pico including, without limitation, at least some MSC server functions. Figure 4 is a block diagram of such an alternative embodiment of a multiple TRX 402 pico base station. As in the case of the multiple TRX pico base stations 102, 202, and 302 shown in Figures 1-3, the multiple TRX 402 pico base stations shown in Figure 4 includes multiple TRXs 116. As With the TRX 302 multi-base station pico shown in Figure 3, the TRX 402 multi-base station pico of Figure 4 also includes the base station control functionality 408 needed to

ES 2 554 541 T3 to control the multiple TRXs 116 included in the pico TRX 402 multiple base station and for the pico TRX 402 multiple base station to communicate with a PLMN (PLMN) 404 (for example, with an NSS 110 public or with a data network 114). In one such embodiment, the base station controller 408 functionality is implemented by software running on one or more of the programmable processors that are included in the multiple TRX 402 pico base station.

In the embodiment shown in Figure 4, the multiple TRX 402 pico base station comprises NSS 410 functionality. NSS 410 functionality includes MGW 440 functionality as described above in connection with Figure 3. The NSS 410 functionality in the embodiment shown in FIG. 4 also implements the GSM private MSC server functionality (MSC-S) 442 and a private home location register (HLR) 444. The private MSC-S 442 functionality and the private HLR 444 functionality allow the NSS 410 functionality to perform full mobility management and call handling between mobile stations 132 that are in communication with the multiple TRX 402 pico base station. or between one or more pieces of fixed equipment 456 (or other SIP entities) that are located within building 134. In the particular embodiment shown in Figure 4, the fixed equipment 456 includes voice over IP phones (VOIP) that are communicatively coupled to a CSP (PBX) with IP 454 over a corporate IP local area network (LAN) 450. In such an embodiment, the NSS 410 functionality further comprises a Session Initiation Protocol (SIP) agent 452 in order to enable the functionality of the private MSC-S 442 and the CSP (PBX) with IP 454 to use the protocol. SIP in order to establish sessions between mobile equipment 132 (which otherwise does not support the SIP protocol) and fixed equipment 456. Likewise, the SIP agent 452 allows the private MSCS 442 functionality to establish sessions with other entities on the network that support the SIP protocol, including, for example, a unified communications server 458 (for example, the MICROSOFT OFFICE COMMUNICATIONS SERVER 2007). . As a result, these sessions can be established without the use of PSTN (PSTN) 112 or PLMN (PLMN) 404. However, the functionality of the private MSC-S 442 can be configured to support call groups to the PLMN (PLMN) 404 or another PLMN (PLMN) 105 in case such type of mobile station 132 moves out of the coverage area of the base station pico while a session is still in progress. In the same way, the private MSC-S functionality 442 can be configured in order to support incoming groups from another MSC when such type of mobile station 132 enters the coverage area of ​​the peak base station 402.

In such an embodiment, the functionality of MGW 440 communicates, for example, with a SIP Session Border Controller (CBS (SBC)) 460 with the intention of communicating call traffic between mobile equipment 132 and fixed equipment. 456 (or other SIP entities) and perform any required transcoding.

In the embodiment shown in figure 4, the functionality of the private MSC-S 444 and the private HLR 442 are private in the sense that said functionalities are only used to establish sessions between the mobile stations 132 of the licensed RF spectrum. that are on the private HLR 444 and SIP-supported equipment that is communicatively coupled to the corporate IP 450 LAN. In such an embodiment, each mobile station 132 in the private HLR 44 is also in a public HLR within the PLMN (PLMN) 404. In case the mobile station 132 that is in the private HLR 444 makes a call to a mobile station that is not in the private HLR 444 or to a fixed device that is not coupled to the corporate LAN IP 450, the functionality of MSC- S from the public MSC in the public NSS 110 is used to establish such a call, in which case the public MSC interacts with the pico base station 402 in the conventional manner. Also, if a mobile that is not in the private HLR 444 uses the pico base station 402 to establish a call, the MSC-S functionality of the public MSC in the public NSS 110 is used to establish that call (directly or via interaction with another public NSS), in which case the public MSC in the NSS 110 interacts with the pico base station 402 in the conventional manner. In other embodiments, the MSC-S functionality and the integrated HLR in the pico base station 402 is public and acts like a conventional MSC-S and HLR in such scenarios (for example, by including other NSS functionality such as a visitor location register (VLR) and prepaid services (PPS)).

In the embodiment shown in Figure 4, the features are provided by the unified communications server 458 of (for example, a voice message to the gateway for email or conference calls) in order for users to SIP-compliant devices can be provided to non-SIP-enabled mobile devices that are on the private HLR 444.

On the other hand, the private functionality MSC-S 442 can be configured in order to route the calls from the mobile device 132 to the PSTN (PSTN) 112 through the CSP (PBX) with IP 454 and its connection to the PSTN (PSTN) 112 (for example, where to do that results in the least cost to the company).

In the same way, supplementary services can be implemented locally using the CSP (PBX) with IP 454 and the private MSC-S 442 functionality of the multiple TRX 402 pico base station. For example, a user who has both, a VOIP fixed telephone coupled to the CSP (PBX) with IP 454 and a mobile device that communicates with the multiple TRX 402 pico base station can have calls from outside that also come in. a device sent to the other device or for both devices to ring when such an outside call comes in. On the other hand, voicemail messages that are received through any device can be routed to the unified communications server 458 (for example, for delivery through a

ES 2 554 541 T3 email user account), thus providing a single repository of voicemail messages.

The above-mentioned SIP-related features can be provided to licensed RF spectrum mobile devices (e.g. GSM) that are on the private HLR 444 while still allowing other licensed RF spectrum mobile devices communicate with PLMN (PLMN) 404 or other PLMN (PLMN) 105 using conventional cellular technology.

In an implementation of such an embodiment, the NSS 410 functionality is implemented in software that is run on one or more of the programmable processors that are included in the multiple TRX 410 pico base station (e.g., the same one or more more than the processors running the software that implements the BSC 408 functionality).

Otherwise, the articles shown in Figure 4 that are referenced in Figure 4 with the same reference numerals that have been used in Figure 1 are substantially the same as those described above in connection with Figure 1.

The functionality described above in connection with Figures 3 and 4 may, in other embodiments, also be implemented using base stations other than the multiple TRX pico base stations (for example, using the single TRX pico base stations, micro base stations and macro base stations). On the other hand, such functionality is described above when it is being implemented in an integrated base station device. However, it should be understood that in some other embodiments, such functionality is implemented using separate network nodes.

The various elements described above (eg, the TRX multiple base station pico and the SAD (DAS) attached to it) can be deployed in diverse architectures and usage scenarios.

Figure 5 illustrates an example of a distributed architecture 500 in which the technology described above (for example, a multiple TRX pico base station and a SAD (DAS)) can be deployed in order to provide coverage and coverage. capacity to GSM / GPRS mobile devices while they are in an enterprise 502. In this example, a base station pico subsystem 504 is coupled to a SAD (DAS) 506. The pico base station 504 is communicatively coupled to an IP corporate local area network 508 (using a GSM Ater-over-IP interface for calls and a Gb-over-IP GPRS data interface). The corporate local area network LAN IP 508 is used to gain access to the central office of the wireless service operator 510 via an IP Network 512, where there is a server MSC (MSC-S) 514, a media gateway ( Gateway) (MGW) 516 and a GSN 518. In the embodiment shown in FIG. 5, a router 532 is used in order to communicatively couple the IP network 512 to the various central office elements of the operator 510.

The MSC-514 handles the signaling of the traffic routed to the central office 510 and controls the MGW 516. In the particular embodiment, the MSC-S 514 includes a SIP user agent (AU) 530 in order to handle related signaling. with SIP (as described below). The MGW 516 switches calls and performs any necessary media conversions (for example, conversions between formats used in company 502 and formats used in the public switched telephone network or by some other PLMN (PLMN) (shown collectively at reference numeral 526 in Figure 5)). The GSN 518 is also coupled to an IP 528 network (over the Gb interface) and implements the conventional SGSN functionality.

In such an embodiment, the NSS functionality is centralized at the central office 510 while the base station subsystem (BSS) is located at the enterprise 502. In one example, the pico base station 504 implements functionality similar to that described above in connection with Figures 3 and 4 in order to allow the pico base station subsystem 504 to locally switch sessions between mobiles 520. that are within their coverage area and / or sessions with a CSP (PBX) with IP 522 (and SIP phones 534 attached to it). In this example, IP522 CSP phones (PBXs) and 534 SIP phones are coupled to the 504 pico base station subsystem over the 508 corporate local area network using a SIP Session Border Controller (CBS (SBC) ) 524, which manages signaling and media flows for sessions established with these types of devices (implementing, for example, a Back-to-Back user agent). The CBS (SBC) 524 handles, for example, transcoding and NAT traversal (using, for example, the Interactive Connectivity Establishment (ICE) protocol or the Session Traverse Utilities protocol for NAT (STUN)).

In this embodiment, the NSS functionality is centralized at the operator's central office 510, which makes it easier to maintain such NSS functionality. However, firewalls are typically used in order to communicatively couple said NSS functionality to the subsystem of the pico base station 504 in enterprise 502, some mechanism is typically used (for Internet Protocol security software (IPsec) ) in order to secure communications between these devices and, Some mechanism is used to prioritize the flow data and with the intention of helping to ensure a desired quality of service (QOS) for the communications between these devices that use the Internet. On the other hand, communications between the

ES 2 554 541 T3 NSS functionality located at operator headquarters 510 and BSS peak 504 at company 502 involves at least one Network Address Translation (NAT) handover.

Figure 6 illustrates another architecture 600 for a company mobile phone system 601 where a company 602 connects to a media gateway (MG) 604 and a mobile switching center server (TMS (MSS)). 606 to the intranet 608 of the company based on an IP. In each office 603 of company 602, a base station pico subsystem 610 and an SAD (DAS) 612 are installed and are coupled to MGs 604 and TMS (MSS) 606 via the intranet 608 of the company. In this way, the pico BSS / SAD (DAS) equipment installed in the various offices 603 of company 602 can share the MG 604 and TMS (MSS) 606 via the Intranet 608. The MG 604 and the MSC-S 606 are coupled communicatively to a wireless carrier PLMN (PLMN) 616 using a suitable backhaul link (eg, TDM links). In this example, Peak BSS 610, SAD (DAS) 612, MG 604, TMS (MSS) 606, and Intranet 608 are located in the enterprise.

The elements of the company's mobile phone system 601 are communicatively coupled to each other using the Intranet 608 (the solid lines between such elements and the Intranet 608 represent the IP communication links). SS7 and GSM compliant signaling (e.g. with signaling format according to user part (ISDN) (ISUP) and mobile application part (MAP) protocols) are communicated between nodes in the PLMN (PLMN) 616 from the operator and the TMS (MSS) 606 and the TMS (MSS) 606 and the BSS peak 610. SS7-related signaling is shown in Figures 6-10 using the dashed lines. Call-related media streams are communicated between the BSS peak 610 and the MG 604 using the Real Time Transport Protocol (PTTR (RTP)). The TMS (MSS) 606 controls the various functions of the media gateway in the system 601 using, for example, the Media Gateway Control Protocol (MGCP). In this embodiment, the SIGTRAN is also used to communicate the signaling data over the IP links.

In this example, the external devices (not shown) are communicatively coupled to the corporate mobile phone system 601 through the operator's PLMN (PLMN) 616. Calls between external communication devices (not shown) and mobile devices 618 with peak BSS service 610 are established using TMS (MSS) 606 and associated media streams are switched by MG 604.

Figure 7 illustrates an architecture 700 similar to that shown in Figure 6 (and those elements that are the same as those used in the example shown in Figure 6 are referenced in Figure 7, using the same numerals reference used in figure 6). In addition, the architecture 700 is extended to include an enterprise IP phone system 720 that is deployed in the enterprise. The corporate IP phone system 720 includes a CSP (PBX) with IP 722 that supports communications with SIP phones 724. In this embodiment, a SIP Session Border Controller (CBS (SBC)) 726 is used with the In order to couple the SIP phones 724 to the Intranet 608. The CBS (SBC) 726 manages the signaling and current media streams for the sessions established with these devices and performs any necessary transcoding.

The TMS (MSS) 606 includes a SIP user agent (SIP AU) (SIP UA) 614 in order to establish the sessions between the 618 mobiles that are being handled by the BSS 610 pico and the 724 SIP phones or the CSP (PBX) with IP 722. The sessions between the 618 mobiles and the devices that are coupled to the PSTN (PSTN) 728 can be established using the SIP AU (SIP UA) 614 and the connection to the PSTN (PSTN) 728 provided by the CSP (PBX) with IP 722. Alternatively, the sessions between such mobiles 618 and the devices that are coupled to the PSTN (PSTN) 728 can be channeled through the operator's PLMN (PLMN) 616 (as is the case in the example shown in Figure 6).

Note that in both architectures shown in figures 6 and 7, a firewall is not used to couple the TMS (MSS) 606, the MG 604 and each of the BSS 610 pico to the Intranet 608. Furthermore, they are not necessary IPSec and SPTTR (RTP) in order to secure communications between these devices. If the QOS and intranet backhaul bandwidth is sufficient to support the services provided by the company's 601 mobile phone system (for example, via a dedicated VPN) then the special features and QOS devices will not they are required in order to provide such a backhaul. If backhaul QOS is a problem, a resource reservation mechanism may be necessary in order to prioritize data flows and in order to help ensure a desired quality of service. On the other hand, in the examples shown in Figures 6 and 7, the TMS (MSS) 606, the MG 604 and each of the BSS 610 pico are assigned to a respective Intranet IP address and the communications between those devices do not they involve no NAT handover.

Figure 8 illustrates an architecture 800 that is similar to that shown in Figure 6 (and those elements that are the same as those used in the example shown in Figure 6 are referenced in Figure 8 with the same reference numerals used in figure 6).

The architecture example 800 shown in figure 8 is similar to the example shown in figure 6 except that the TMS (MSS) 606 and MG 604 and the pico BSS 610 are coupled to each other over the public Internet. 830 instead a company intranet. As a result, 832 firewalls are required in order to dock

ES 2 554 541 T3 the TMS (MSS) 606 and MG 604 and each subsystem of pico base station 610 to the Internet 830. Also, IPSec and SPTTR (RTP) are used with the intention of ensuring communication between those devices and QOS is used in order to prioritize data flows and to help ensure a desired quality of service for communications between these devices using the Internet 830. Furthermore, each of the TMS (MSS) 606, MG 604, and each subsystem of the pico base station 610 is assigned an Internet IP address and communications between those devices occur over the Internet 830.

Figure 9 illustrates an example of architecture 900 that is similar to that shown in figures 7-8 (and those elements that are the same as those used in the examples shown in figures 7-8 are referenced in figure 9 using the same reference numerals used in Figures 7-8).

The 900 architecture example shown in figure 9 is similar to the example shown in figure 7 except that the one shown in figure 9 uses a company Intranet 934 and Internet 830 in order to integrate a CSP (PBX) with IP 722 and SIP 724 phones in the system. In this example, the SIP AU (SIP UA) 614 user agent included in the TMS (MSS) 606 is used to establish the sessions between the 618 mobiles that are being managed by the MSC-S 606 and the SIP phones. 724 or the CSP (PBX) with IP 722. The sessions between the mobiles 618 and the PSTN (PSTN) 728 can be established using the SIP UA 614, in which case the connection to the PSTN (PSTN) 728 is provided through the CSP (PBX) with IP 722. In this example, the CBS (SBC) 726, the CSP (PBX) with IP 722 and the SIP phones 724 are located behind the 832 firewall that is between the Intranet 934 and the Internet 830. In this way, the CSP (PBX ) with IP 722 and SIP phones 724 are intranet IP assigned addresses and communications going over CBS (SBC) 726 involve NAT handover. In this embodiment, the CBS (SBC) 726 manages the signaling and media streams for the sessions established with these devices (implementing, for example, a Back-to-Back agent). Also, the CBS (SBC) 726 handles, for example, NAT transcoding and traversal (using, for example, the Interactive Connectivity Establishment (ICE) protocol or the Session Traversal Utilities for the NAT (STUN) protocol).

In this example, IPSec and SPTTR (RTP) are required in order to secure communications between the TMS (MSS) 606, MG 604, pico BSS 610, and the company IP phone system 720 that occur over the Internet 830. Also , QOS is necessary in order to prioritize data flows and to help ensure a desired quality of service for communications between TMS (MSS) 606, MG 604, and pico BSS 610 that occur over the Internet 830.

Figure 10 illustrates an example architecture 1000 that is similar to the example shown in Figure 9 (and those elements that are the same as those used in the example shown in Figure 9 being referenced in Figure 10 using the same reference numbers used in figure 9).

The example architecture 1000 shown in Figure 9 is similar to the example shown in Figure 9 except that the deployment of each BSS / SAD (DAS) peak is also coupled to a company's Intranet 934. As a result, each pico base station 610 is assigned an intranet IP address and is behind the intranet 832 firewall. The communications between the pico base station 610 and both the TMS (MSS) 606 or MG 604 cross the NAT of the Intranet and circulate through the Internet 830 and, therefore, IPSec / SPTTR (RTP) is used in order to secure such communications and QOS is used in order to help ensure a desired quality of service.

The various architectures and techniques described above can be used in many service delivery scenarios. Figure 11 illustrates such a scenario in which the technology described here is used to provide wireless local loop (WLL) service for both voice and data within an enterprise (for example, using the low power RF spectrum ) in order to implement a mobile network of the company 1100 to provide wireless service within the company. In this scenario, a TMS (MSS) 1102 offers MSC, HLR and PPS services for local mobiles 1104 that are local subscribers to that company mobile network 1100 and provides the possibility of non-roaming for any non-local mobile that deals of itinerar (roam) in a coverage area associated with the company. Sessions can be established between a local mobile 1104 and a non-local device through the PSTN (PSTN) (Public Switched Telephone Network or PSTN in Spanish) 1106.

Wireless coverage and capacity are provided by pico BSS 1108 and SAD (DAS) 111. A Media Gateway (MG) 1112 is used in order to communicate communicatively the elements of the company's mobile network 1100 to the PSTN (PSTN) 1106 and, under the control of the TMS (MSS) 1102 , to switch the call media flows between mobiles 1104 and devices connected to the PSTN (PSTN) 1106 and in order to carry out any necessary transcoding. A GPRS Support Node (GSN) 1114 is included in the private network 1100 to provide GPRS data service to local mobiles 1104. The GSN 1114 is coupled to the Internet 1116 using a firewall 1118. The elements of the mobile network of company 1100 are communicatively coupled to each other using the company's IP intranet 1120.

Figure 12 illustrates another scenario where the technology described here is used to provide only roaming service within an enterprise. In this example, the TMS (MSS) 1202 implements the functionality

ES 2 554 541 T3

MSC / VLR in order to support such roaming. The company's mobile network 1200 is used for the purpose of providing roaming services to other wireless networks and itself does not have any local subscribers. In other words, from the perspective of the operator's wireless network (PLMN) 1222, the TMS (MSS) 1202 of a company's mobile network 1200 appears to be another MSC / VLR of the PLMN (PLMN) 1222. The TMS (MSS) 1202 of the company network 1200 communicates with the other elements of the PLMN (PLMN) 1222 using the MAP protocol. A media gateway (Gateway) 1224 is used in order to communicate communicatively the elements of the company network 1200 to the PLMN (PLMN) 1222 and under the control of the TMS (MSS) 1202, in order to switch the call media flows between mobiles 1104 and PLMN connected devices 1222 and in order to perform any necessary transcoding. Authentication and other functions are provided by the NSS functionality of PLMN (PLMN) 1222. Otherwise, company mobile network 1200 is similar to company mobile network 1100 in Figure 11.

Figure 13 illustrates another usage scenario in which an enterprise mobile network 1300 is configured to support both local subscribers and hybrid subscribers. As used in this document, the hybrid subscribers are both the local subscribers of the mobile network of the company 1300 and the subscribers of the PLMN (PLMN) 1222. In one application, each hybrid subscriber has a local ISDN NEM (MSISDN) that is assigned by the company mobile network 1300 and a public ISDN NEM (MSISDN) that is assigned by the PLMN (PLMN) 1222. When A hybrid subscriber enters a coverage area associated with the mobile network of the company 1300, a location update occurs with the TMS (MSS) 1302 of the mobile network of the company 1300. The local TMS (MSS) 1302, in connection with such a location update, acts as an MSC / VLR for the public hybrid ISDN NEM subscriber (MSISDN) and communicates with the public HLR (which is not sample) in the PLMN (PLMN) 1222 in order to complete a location update for the public hybrid subscriber with ISDN NEM number (MSISDN) using the MAP / D protocol. Also, the local TMS (MSS) 1302, in connection with such a location update, performs a location update for the local hybrid subscriber number with ISDN NEM number (MSISDN) and handles both the MSC / VLR and the HLR / PPS for the location update. As a result, when a hybrid subscriber is within the coverage area associated with the company's mobile network 1300, the hybrid subscriber is able to receive calls made to both his public ISDN NEM number (MSISDN) and his number. local ISDN NEM (MSISDN). When the hybrid subscriber is outside the coverage area of ​​the mobile network of the company 1300, the hybrid subscriber is only able to receive calls made to its public ISDN NEM number (MSISDN). The TMS (MSS) 1302 of the mobile network of the company 1300 also acts as an MSC / VLR in order to also support the groups and the like.

Figure 14 shows another usage scenario, in which a mobile network of a company 1400 also includes a Private A-link Intelligent Multiplexer (PALIM) switching function 1426 in order to support three types of subscribers, - private subscribers ( subscribers who are only subscribers of the private mobile network of the company 1400), the hybrid subscribers (subscribers who are subscribers of the private mobile network of the company 1400 and the public PLMN (PLMN) 1222) and the public subscribers (subscribers that are subscribers of the public PLMN (PLMN) 1222 and are not subscribers of the mobile network private company 1400). PALIM 1426 switching technology enables the 1400 company mobile network to provide local NSS functionality for private and hybrid subscribers that are within a coverage area of ​​the 1400 company mobile network while supporting roaming for subscribers. public.

The PALIM function 1426 is used to logically couple the rest of the elements of the mobile network of the company 1400 to the PLMN (PLMN) 1222 using the GSM A interface in such a way that the mobile network of the company 1400 appears, from the perspective of the PLMN (PLMN) 1222, as another base station subsystem of the PLMN (PLMN) 1222 in connection with the service provided to public subscribers and hybrid subscribers in connection with their public ISDN NEM (MSISDN) numbers. However, for local subscribers and hybrid subscribers in connection with their private ISDN NEM (MSISDN) numbers, the 1400 company mobile network provides full NSS functionality (i.e. MSC / VLR and HLR / PSS functions ).

Figure 15 illustrates an example in which a company mobile network 1500 is applied across two offices of a company. In this example, two intranets 1520s (at respective offices A and B) are communicatively coupled to each other via a virtual private network (VPN) connection (using, for example, the IPSec protocol). In this example, the TMS (MSS) 1402 and the GSN 1114 are deployed in Office A, while the PSTN connection (PSTN) and the associated MG 1112 are located in Office B. The mobile network traffic is routed between the 1520 Intranets using the underlying IP network technology.

Figure 16 illustrates an example in which two separate 1600 enterprise mobile networks share a 1614 GSN and a 1602 TMS (MSS). The 1614 GSNs and a 1602 TMS (MSS) are located in a 1628 wireless operator central office. and they are connected to the respective 1620 intranets of the two companies using a VPN. Mobile network traffic is routed between Intranets 1620 and TMS (MSS) 1602 and GSN 1614 using the underlying IP network technology.

Figure 17 shows an example in which a CSP (PBX) (Private Branch Automatic Switching) with IP 1730 is integrated with the mobile network of the company 1700. In this embodiment, a SIP AU user agent of SIP (SIP UA)

ES 2 554 541 T3

1732 included in the TMS (MSS) 1702 allows mobile wireless devices 1104 to use the SIP protocol in order to establish sessions with the 1734 SIP phones that are linked to the CSP (PBX) with IP 1730. The CSP (PBX) with IP 1730 is coupled to PSTN 1106 through a Media Gateway 1740.

In this example, the CSP (PBX) with IP 1730 can be configured in order to associate the numbers of a CSP extension (PBX) with the local subscribers of the mobile network of the company 1700 (for example, the private subscribers and hybrids). For example, when a local subscriber also has a 1734 landline SIP phone that has a particular CSP (PBX) extension number, the 1730 IP CSP (PBX) and the 1702 TMS (MSS) can be configured in order to associating the same CSP extension number (PBX) with the local subscriber's mobile 1104 and calls made to that CSP extension (PBX) cause both the SIP phone 1734 and the mobile 1104 to ring. In this way, the mobile devices 1104 can act as wireless extensions of the CSP (PBX) with IP 1730.

Figure 18 illustrates an example in which an Access Gateway 1836 is integrated with the mobile network of a company 1800. The Access Gateway 1836 is used to couple SIP devices to other types of networks. voice. In the particular embodiment shown in figure 18, the access gateway 1836 is used to couple the SIP devices to the PSTN (PSTN) 1106 with an analog trunking line (independent cellular network structure) 1838. In this example, the SIP user agent 1732 included in the TMS (MSS) 1702 allows the TMS (MSS) 1702 to use the access gateway 1836 to access the devices and networks attached to it (such as telephones SIP 1734 and 1840 analog phones).

Figures 19-36 show additional examples of services and usage scenarios that can be implemented using the technology described here.

Figure 19 illustrates an example of a company 1900 mobile network in which the technology described above can be deployed (for example, a multiple TRX pico base station and an SAD (DAS)) in order to provide the coverage and capacity to 1902 GSM / GPRS mobile devices within a 1904 company. In this example, the company 1900 mobile network is not coupled to some PLMN (PLMN) and is also referred to here as an isolated company 1900 mobile network. Company 1904 can get access to proper GSM spectrum, which is usually licensed spectrum. In this example, one way in which a company 1904 can have access to a suitable GSM spectrum for use in such an isolated mobile network from company 1900 is to obtain a license to use a low power RF spectrum that is available in some jurisdictions.

In this example, a base station pico subsystem 1906 is coupled to a SAD (DAS) 1908. The company's mobile network 1900 also comprises a mobile switching subsystem (TMS (MSS)) 1910 that is coupled to the mobile network subsystem (MSS) 1910. pico base station 1906 and which is also located in company 1904. The TMS (MSS) 1910 all related NSS functions for the mobile network of company 1900. The TMS (MSS) 1910 is coupled to the PSTN (PSTN) 1912 using a 1914 analog CSP (PBX). The analog CSP (PBX) 1914 is also coupled to the various analog phones 1916. A media gateway 1918 is provided in order to perform any necessary media conversions between the media formats used by the TMS ( MSS) 1910 and the 1906 base station pico subsystem and the media formats used by the 1914 analog CSP (PBX).

The mobile network of a 1900 company also includes a GSN 1920 that is coupled to the Internet 1922. The GSN 1920 is used to provide GPRS data service to the mobile device 1902 while it is camped on the mobile network of the 1900 company.

In this example, company 1900 mobile network is configured to be used with the same 1902 mobile devices that users use when they are outside the 1900 company coverage area. That is, in this example, 1902 mobile devices (and Associated Subscriber Identity Module (SIM) cards) have a home PLMN (PLMN) that is not the company's 1900 mobile network. The company's mobile network 1900 is configured to be used with these mobile devices 1902 without requiring users to change their subscriber identity module (SIM) cards. If the coverage area of ​​a user's home PLMN overlaps with the coverage area of ​​the company's mobile network 1900, the user must manually select the appropriate network to use.

Each local user of the company 1900 mobile network registers with the 1900 network using the International Mobile Equipment Identity (IMEI) assigned to the user's mobile device 1902 (which the user can access, by himself, from the device Mobile 1902 via the device's user interface). Each local user (also known here as a local subscriber) is assigned a local telephone number (local ISDN NEM (MSISDN)) that is used by the company 1900 mobile network to provide wireless cellular service to that subscriber. local. In other words, each mentioned user has a regular public mobile phone number that is used in the user's home PLMN and a local mobile phone number that

ES 2 554 541 T3 can be used in the mobile network of the company 1900.

Also, in this example, each local subscriber has an associated analog telephone 1916 that has a CSP extension number (PBX) associated with it. In this example, the user can use the call forwarding function provided by the user's home PLMN (PLMN) to, while the user who is not camped in the home PLMN, can forward calls that are made to the number the user's public telephone number to the user's CSP extension number (PBX). In this example, the CSP (PBX) 1914 supports a double ringing feature and is configured such that when a call is made to the CSP (PBX) extension number, the CSP (PBX) 1914 causes them to ring for that call both the user's analog landline 1916 and mobile phone 1902 (using the user's local mobile phone number). The CSP (PBX) 1914 rings the mobile phone 1902 by forwarding the associated signaling and call data to the TMS (MSS) 1910.

A similar approach can be used with an IP-based CSP (PBX).

Figure 20 illustrates another example of a 2000 company mobile network where the technology described above (for example, a multiple TRX pico base station and a SAD (DAS)) can be deployed in order to provide coverage and capacity to GSM / GPRS 2002 mobile devices located within a company 2004.

In this example, company 2000 mobile network gains access to RF spectrum by entering into an agreement with the operator of a PLMN 2006. In this example, company 2000 mobile network is configured to support subscribers local and non-local subscribers (i.e. roaming users)

A 2008 pico base station subsystem and 2010 SAD (DAS) are provided within each company office 2004. Also, a local 2012 TMS (MSS) is provided at company 2004 that is coupled to the pico subsystem. 2008 base station. The local TMS (MSS) 2012 is also coupled to a central TMS (MSS) 2014 located at the operator's headquarters 2016. In this example, the local TMS (MSS) 2012 serves as the MSC / VLR for those 2002 mobile devices that are in a coverage area associated with the company's mobile network 2000 and the central TMS (MSS) 2014 implements the functionalities GMSC and HLR for all 2004 company offices and local company subscribers. Each local TMS (MSS) 2012 is coupled to the central TMS (MSS) 2014 over an IP 2018 network using the MAP and ISUP protocols.

The mobile network of the company 2000 also includes a GSN 2020 that is coupled to the mobile devices 2002 in each office of the company 2004 through the IP network 2018. The GSN 2020 is used to provide the GPRS data service to the mobile device 2002 while camping in the company mobile network 2000. The GSN 2020 is also connected to an IP 2022 network which is the way the GPRS service is provided. Headquarters 2016 also includes a Media Gateway (MGW) 2024 that switches calls and performs any necessary media conversions. The 2016 head office also includes a 2026 router for coupling TMS (MSS) 2014, GSN 2020 and MGW 2024 to the 2018 IP network.

Each local TMS (MSS) 2012 is also coupled to the PSTN (PSTN) 2026 via an analog CSP (PBX) 2028. The 2028 analog CSP (PBX) is also coupled to several 2030 analog phones. A media gateway 2032 is provided in order to perform whatever conversion is needed by the media between the media formats used by the local TMS (MSS) 2012 and the base station pico subsystem 2008 and the formats of the media used by the analog CSP (PBX) 2028.

In this example, the HLR in the central TMS (MSS) 2014 is the HLR for the company's local subscribers and is managed by the operator of the PLMN (PLMN) 2006. As a result, local subscribers can be registered using their IMSI numbers. Local subscribers are otherwise provided with service in a manner similar to that described above in connection with Figure 19 (including, for example, integration with the CSP (PBX) 2028).

In this example, the company's mobile network 2000 is also used to provide wireless services to non-local subscribers (including PLMN 2006 subscribers to roaming users). For such subscribers, the local TMS (MSS) 2012 serves as the MSC / VLR and the roaming service is provided using the roaming agreements and functionality in the 2006 PLMN (PLMN), in which the local TMS (MSS) 2012 accessed through the IP 2018 network.

Figure 21 illustrates another example of a 2100 company mobile network in which the technology described above can be deployed (for example, a multiple TRX pico base station and a SAD (DAS)) in order to provide the coverage and capacity to GSM / GPRS mobile.

In this example, the capacity of the base station is deployed within each office of company 2104 and all NSS functions are performed in a PLMN (PLMN) 2106. The mobile network of company 2100 has no local subscribers and instead , is a part of PLMN (PLMN) 2106. More specifically, in this example, they are

ES 2 554 541 T3 provided a 2108 pico base station subsystem and a 2110 SAD (DAS) within each 2104 company office. Each 2108 base station pico subsystem is coupled to the NSS functionality of the PLMN (PLMN ) 2106 over an IP network 2112. For example, as shown in figure 21, a TMS (MSS) 2114, a GSN 2116, and an MGW 2118 are deployed within a central office 2120 of the operator of the PLMN (PLMN) 2106. The TMS (MSS) 2114, in this example, serves as the MSCA / LR for mobile devices 2102 that are within a coverage area associated with company 2104.

The GSN 2116 is used to provide the GPRS data services on the mobile device 2102 while it is camped on the company mobile network 2100. The GSN 2116 is also connected to an IP network 2122 via which the GPRS service is provided. The central office 2120 also includes an MGW 2118 that switches calls and performs any necessary media conversions. The central office 2120 also includes a router 2124 for coupling the TMS (MSS) 2114, GSN 2116 and MGW2118 to the IP network 2112.

Also, the company's 2100 mobile network can be configured to implement different types of location-based services such as the use of a call routing desk to selectively route calls, Computer Supported integration Telecommunications Applications (CSTA) / Cali Detail Record (CDR), location-based fees, HLRA / LR virtual support, local switching and support for a distributed mobile station roaming number (MSRN).

Figure 22 illustrates another example of a mobile network of a 2200 company in which it can be deployed described above (for example, a pico base station with multiple TRX and a SAD (DAS)) in order to provide coverage and the capacity to 2202 GSM / GPRS mobile devices located within a company 2204.

This example illustrates how the company's 2200 mobile network can be integrated with a CSP (PBX) with IP. In this example, company 2200's mobile network gains access to RF spectrum by entering into an agreement with a PLMN operator 2206. In this example, company 2200's mobile network is configured to support the local subscribers and non-local subscribers (ie roaming users).

Each company office 2204 provides a base station pico subsystem 2208 and a SAD (DAS) 2210. Also, each base station pico subsystem 2208 is coupled to a TMS (MSS) 2212 located at the central office of the company. operator 2214. In this example, the TMS (MSS) 2212 serves as the MSC / VLR for those mobiles 2202 that are located within a coverage area associated with the mobile network of a company 2200. Also, the TMS (MSS) 2212 implements the GMSC and HLR functionalities for all the local subscribers of the company offices 2202. Each subsystem of pico base station 2208 is coupled to the TMS (MSS) 2212 over an IP Network 2216 using a Ater over IP interface.

The company 2200 mobile network also includes a GSN 2218 that is coupled to the 2202 mobile devices in each company 2204 office through the 2216 IP network. The GSN 2218 is used to provide the GPRS data service for the devices. 2202 mobiles while camped on the company 2200 mobile network. GSN 2218 is also connected to an IP 2220 network through which GPRS services are provided. Central office 2214 also includes a media gateway (MGW) 2222 that switches calls and performs any necessary media conversions. The central office 2214 also includes a router 2224 for coupling the TMS (MSS) 2212, GSN 2218 and MGW 2222 to the IP network 2216.

In this example, the HLR in the TMS (MSS) 2212 is the HLR for the local subscribers of the company and is managed by the operator of the PLMN (PLMN) 2206. As a result, the local subscribers can be registered using their numbers IMSI.

In this example, a company's mobile network 2200 is also used to provide wireless services to non-local subscribers (including PLMN subscribers (PLMN) 2206 and roaming users). For such subscribers, the TMS (MSS) 2212 serves as the MSC / VLR and the roaming service is provided using the roaming agreements and functionality in the PLMN (PLMN) 2206, which the TMS (MSS) 2212 accesses via the IP network 2216.

Each 2208 pico base station subsystem is also coupled to the 2226 PSTN via a 2228 IP CSP (PBX). The 2228 IP CSP (PBX) is also coupled to several 2230 SIP phones. Each subsystem The peak base station 2208 is coupled to a CSP (PBX) with IP 2228 over a corporate IP 2232 LAN. A SIP Session Border Controller (CBS (SBC)) 2234, manages signaling and media flows for sessions established with mobile devices 2202. In this example, the CBS (SBC) 2234 routes the SIP signaling data for such sessions between a SIP AU SIP User Agent (SIP UA) 2236 on the TMS (MSS) 2212 and the CSP (PBX) with IP 2228 as necessary for routing the media streams for such sessions between the base station pico subsystem 2208 (for final communication with the mobile devices 2202) and the SIP phones 2230. Also, in this example, the CBS (SBC) 2234 handles the transcoding of the media streams communicated between the SIP phones 2230 and the mobile devices 2202 and any NAT handover.

ES 2 554 541 T3

As with the example described above in Figure 19, in this example, the company's mobile network 2200 is configured to be used with the same mobile devices 2202 that users use when they are outside the home area. 2200 company mobile network coverage. That is, in this example, 2202 mobile devices (and associated SIM cards) have a home PLMN (PLMN) that is not the 2200 company mobile network. The company's 2200 mobile network is configured to be used with these 2202 mobile devices without requiring users to change their SIM cards. If the coverage area of ​​a user's home PLMN (PLMN) matches the coverage area of ​​the company's 2200 mobile network, the user may need to manually select the appropriate network to use.

Each local subscriber of the 2200 company mobile network is registered with the 2200 network and is assigned a local telephone number (local ISDN NEM (MSISDN)) which is used by the 2200 company mobile network with the in order to provide the wireless cellular service to that local subscriber. In other words, Each such local subscriber has a regular public mobile phone number (also referred to here as the public ISDN NEM (MSISDN) or home ISDN NEM (MSISDN)) that is used in the user's home PLMN (PLMN) 2206 (and for which the user has an associated record in the main domestic HLR in the home PLMN (PLMN) 2206) and a local mobile phone number that is used in the company's mobile network 2200 (and for which the user has a record associate in the HLR of the company that maintains the TMS (MSS) 2212). Also, in this example, each local subscriber has an associated SIP phone 2230 that has an associated CSP extension number (PBX), which is managed by the 2228 IP-based CSP (PBX).

As shown in Figure 23, when a local subscriber roams in a coverage area associated with the company's mobile network 2200, the local subscriber's mobile device 2202 performs a location update with the TMS (MSS) 2212 This location update is forwarded from the pico base station subsystem 2208 to the TMS (MSS) 2212 over the IP network 2216. The TMS (MSS) 2212, acting as an MSC / VLR, takes care of the location update in the normal way in order to update the local subscriber information in the home HLR in the home PLMN (PLMN) 2206 with respect to to the home ISDN NEM number (MSISDN) of the local subscriber. This allows the local subscriber to receive calls made to the subscriber's home ISDN NEM (MSISDN) number while the local subscriber is camped on the company's mobile network 2200. In this example, the subscriber's local ISDN NEM (MSISDN) number is registered with the HLR of the company that maintains the TMS (MSS) 2212. Also, the SIP AU 2236 in the TMS (MSS) 2212 is registered with the CSP (PBX) with IP 2228 so that the CSP (PBX) with IP 2228 will contact him when calls are made to the extension of the local subscriber's CSP (PBX) using the double ring feature of Call from CSP (PBX) with IP 2228.

Figure 24 illustrates how a mobile device 2202 that is camped on the company's mobile network 2200 can make a call to a device connected to the PSTN (PSTN) 2206. As shown in Figure 24, when the mobile device 2202 calls such an external device, the signaling data from the originating mobile (MO) as part of the call is communicated to the TMS (MSS) 2212. In this example, there are two options to complete the call. In the first option, the TMS (MSS) 2212 is configured to establish the call using the CSP (PBX) with IP 2228. This is done by having the SIP UA 2236 in the TMS (MSS) 2212 making the call using the CSP (PBX) with IP 2228. In other words, the SIP2236 UA appears to be another SIP 2230 phone that is making a call. Once the call is established, the media flow for the MO portion of the call is routed between the mobile device 2202 and the IP 2228 CSP (PBX) using the corporate local area network LAN 2232 and the CBS (SBC ) 2234, where the CBS (SBC) 2234 performs any necessary conversion of the media between the media format used by the 2202 mobile devices and the format used by the CSP (PBX) with IP 2228 and the CSP (PBX) with IP 2228 performs any necessary media conversion between the format used by the CSP (PBX) with IP 2228 and the format used by the PSTN (PSTN) 2226. In the second option, the TMS (MSS) 2212 is configured to establish the call using the PLMN (PLMN) 2206 in a similar way as when making any other GSM call. Once the call is established, media flows are routed for the MO portion of the call between mobile device 2202 and PLMN 2206 using MGW 2222, which performs whatever media conversions are necessary. With both options, the base station peak subsystem 2208 is used in order to provide the radio links for the mobile device 2202.

Figure 25 illustrates how a call is made to an ISDN NEM (MSISDN) associated with a local subscriber (for example, the local subscriber's ISDN NEM (MSISDN) or the home public ISDN NEM (MSISDN) ) can be completed using the company's mobile network 2200 in Figure 22. When a local subscriber is camped on the company 2200 mobile network and a call is made to an ISDN NEM number (MSISDN) associated with that local subscriber, the PLMN (PLMN) 2206 will route the signaling associated with the call to the TMS (MSS) 2212. The TMS (MSS) 2212 acts as the MSCA / LR for the PLMN (PLMN) 2206 and will cause the local subscriber mobile device 2202 to ring by sending appropriate signaling messages to the mobile devices 2202 using the base station pico subsystem. 2208. If the local subscriber uses the mobile device 2202 to answer the call, the TMS (MSS) 2212 establishes the media flows for the GSM call in the conventional manner using the base station pico subsystem 2208 and the MGW 2222. The TMS (MSS) 2212 will also cause the SIP phone 2230 associated with that local subscriber to ring as well. The TMS (MSS) 2212 does this by having the AU of SIP2230 establishing the call with the CSP (PBX) with IP 2228 that is directed to the extension

ES 2 554 541 T3 associated with the CSP (PBX) of the local subscriber. The CSP (PBX) with IP 2228 will ring the SIP phone 2230 associated with that extension of the CSP (PBX). If the local subscriber uses the SIP phone 2230 to answer the call, the TMS (MSS) 2212 establishes the media flows for the call between the PLMN (PLMN) 2206 (and the calling phone) and the SIP phone. 2230 using the MGW 2222 (which performs any necessary media conversion between the formats used by the SIP phone 2230 (for example, the PTTR (RTP) format) and the GSM media formats in the PLMN (PLMN) 2206).

Figure 26 illustrates how a call that is made to a CSP extension number (PBX) associated with a local subscriber can be completed using the company's mobile network 2200 of Figure 22. When a local subscriber is camped out at the company mobile network 2200 and a call is made to an extension of the CSP (PBX) associated with that local subscriber, the PSTN (PSTN) 2226 will direct the signaling associated with such call to the CSP (PBX) with IP 2228. The CSP (PBX) with IP 2228, in the conventional manner, will cause the local SIP subscriber's telephone 2230 to ring by sending appropriate signaling messages to the SIP telephone 2230. If the local subscriber uses the SIP telephone 2230 to answer the call, the 2228 IP CSP (PBX) establishes the call media flows in the conventional manner between the 2228 IP CSP (PBX) and the 2230 SIP phone. In this example, the CSP (PBX) with IP 2228 will also cause the mobile device 2202 associated with that local subscriber to ring (using the double ringing feature of the CSP (PBX) with IP 2228). The IP CSP (PBX) 2228 does this by interacting with the SIP UA 2236 on the TMS (MSS) 2212 as if the SIP UA 2236 were another SIP phone. In response to this, the SIP UA 2236 causes the mobile device 2202 to ring, using the pico base station subsystem 2208. If the local subscriber uses the mobile device 2202 to answer the call, the TMS (MSS) 2212 establishes the call. call between the mobile device 2202 and the CSP (PBX) with IP 2228. Once the call is established, the media flows for the call are routed between the mobile device 2202 and the CSP (PBX) with IP 2228 using the corporate Local Area Network (LAN) 2232 and the CBS (SBC) 2234 , where the CBS (SBC) 2234 performs any necessary conversion of the media between the formats used by the mobile device 2202 and the format used by the CSP (PBX) with IP 2228 and the CSP (PBX) with IP 2228 performs any conversion of the media that is necessary between the format used by the CSP (PBX) with IP 2228 and the format used by the PSTN (PSTN) 2226.

Figure 27 illustrates another example of a company 2700 mobile network in which the technology described above (for example, a multiple TRX pico base station and an SAD (DAS)) can be deployed in order to provide the coverage and capacity for GSM / GPRS 2702 mobiles located within a 2704 company.

In this example, a base station pico subsystem 2706 is coupled to a SAD (DAS) 2708. The company's mobile network 2700 also comprises a mobile switching subsystem (TMS (MSS)) 2710 that is coupled to the pico subsystem. base station 2706 and which is also located at company 2704. In this example, company 2700's mobile network is coupled to a PLMN (PLMN) 2718 with which company 2704 has an agreement. In this example, the local subscribers of company 2704 have both a local ISDN NEM number (MSISDN) and a public ISDN NEM number (MSISDN) as described above and the TMS (MSS) 2710 acts as the HLR (as well as the MSC / VLR) for local subscribers with respect to their local ISDN NEM numbers (MSISDN) but only acts as an MSCA / LR for local subscribers with respect to their ISDN NEM numbers (MSISDN ) public.

In the example shown in figure 27, the TMS (MSS) 2710 is also coupled to the PSTN (PSTN) 2712 through a CSP (PBX) with IP 2714. The TMS (MSS) 2710 is coupled to the CSP (PBX) CON IP 2714 using a session border controller and a corporate Local Area Network (LAN) (both of which are not shown in Figure 27). The 2714 IP CSP (PBX) is also coupled to several 2716 SIP phones. Any transcoding that is necessary between the media formats used by the 2706 pico base station subsystem and those used by the IP 2714 CSP (PBX) can be performed by the CBS (SBC) and / or the CSP (PBX itself). ) of IP 2714.

The company's 2700 mobile network also includes a GSN 2720 that is coupled to the 2722 Internet. The GSN 2720 is used in order to provide GPRS data service to 2702 mobile devices while they are camped on the company's mobile network. company 2700.

In this example, company 2704 also has UC (from CU) unified communications technology deployed. UC technology is implemented in enterprise 2704 using one or more unified communications servers 2724 that are communicatively coupled to various UC 2726 endpoints (such as personal computers, telephones, and video conferencing equipment) and other IP devices. (such as 2716 SIP phones and 2714 IP CSPs (PBXs) using the LAN with corporate IP. In particular, the UC 2724 unified communications servers integrate and manage real-time, synchronous communication services (such as VOIP telephony, instant messaging, audio and video conferencing, and private cellular telephony), and asynchronous communication services. Unified Messaging (such as asynchronous communication services, email, voicemail, faxes, calendars, and presence) for the purpose of, among other things, offer unified messaging to users' inboxes. In one such implementation, the unified communications servers 2724 are implemented using the package

ES 2 554 541 T3

Microsoft Office Communications Server 2007 to integrate and manage synchronous communication services and Microsoft Exchange Server 2007 to integrate and manage asynchronous communication services and deliver Unified Messaging. In such an implementation, the UC server software is hosted locally within company 2704 (ie, UC server software runs on hardware servers that are deployed at company 2704). Although the unified communications servers 2724 are shown in Figure 27 as they have been deployed within the enterprise 2704, it should be understood that in other embodiments the UC servers 2724 include one or more UC servers or services that are provided by external service providers (also known as "host" services -hosted-), such as the host Microsoft Exchange Server services or Microsoft Office Communications Server services).

In this example, several UC 2726 endpoints use UC client software that is compatible with UC 2724 servers (such as Microsoft Office Communicator 2007 for the synchronous communication service and / or Microsoft Outlook 2007 for the asynchronous communication service and to access the inbox for the user's UM). In addition, the UC 2724 server managing synchronous communication services integrates the 2714 IP CSP (PBX) and 2716 SIP phones into the complete UC solution. The TMS (MSS) 2710 includes SIP AU User Agent (UA) (not shown in Figures 27-31) that the TMS (MSS) 2710 uses to interact with the 2714 IP-based CSP (PBX) and server of UC 2724. Thus, mobile devices 2702 appear to be the CSP (PBX) with IP 2714 and UC 2714 to be another SIP device.

UC technology can be used in order to unify a mobile device of each local subscriber 2702, SIP landline 2716, and other UC 2726 endpoints with respect to synchronous and asynchronous communications. For example, as shown in figure 28, when a call is made to a CSP extension (PBX) associated with a local subscriber of company 2704, the call will be received in the CSP (PBX) with IP 2714 of the RTC (PSTN) 2712. The 2714 IP CSP (PBX) is configured to ring the called user's 2716 SIP phone in the normal way. In addition, the IP CSP (PBX) 2714 is configured to interact with the SIP UA on the TMS (MSS) 2710 to cause the called user's mobile device 2702 to ring (if mobile device 2702 is camped on the company's 2700 mobile network at the time). As noted above, the SIP UA on the TMS (MSS) 2710 appears to be, from the perspective of the IP 2714 CSP (PBX), another SIP device.

The IP CSP (PBX) 2714 is also configured to interact with the UC server 2724 that manages the synchronous communication services to indicate that there is an incoming call for the user who has been called. The UC 2724 server causes the called user's UC 2726v endpoint to ring or otherwise indicate that there is an incoming call attempt.

If the called local subscriber uses the 2716 fixed SIP phone to answer the call, the 2714 IP CSP (PBX) establishes the media flows for the call in the conventional manner between the 2714 IP CSP (PBX) and the 2716 SIP landline phone. If the user uses the 2726 UC endpoint to answer the call, the 2724 UC server and 2714 IP-based CSP (PBX) establish the call.

If the user uses the mobile device 2702 in order to answer the call, the CSP (PBX) with IP 2714 establishes the call with the SIP UA on the TMS (MSS) 2710 and the TMS (MSS) 2710 in turn establishes the call with the mobile device 2702 of the called user (via the pico base station subsystem 2706 and the SAD (DAS) 2708). Once the call is established, the media flows for the call are routed between the mobile device that has been called 2702 and the device that has made the call connected to the PSTN 2712 (where any transcoding can be performed It is necessary through a CBS (SBC) that is used to couple the 2706 pico base station subsystem to the corporate IP LAN and the CSP (PBX) with IP 2714).

Figure 29 illustrates an example in which someone uses a 2716 landline SIP phone to call a CSP user extension (PBX). The processing of such a call is substantially similar to the processing described above in connection with Figure 28.

Figure 30 illustrates an example where someone uses a mobile device 2702 to call a number of a local ISDN user NEM (MSISDN). The TMS (MSS) 2710 is configured to ring the mobile device 2702 of the local subscriber that has been called in the normal way. Also, the TMS (MSS) 2710 uses the SIP AU to call both, the CSP (PBX) with IP 2714 and the UC server 2724 that handles the synchronous communication services. IP CSP (PBX) 2714 and UC server 2724 cause called user's SIP landline 2716 and UC 2726 endpoint to ring, respectively, or otherwise indicate that an incoming call is being attempted .

If the user uses the mobile device 2702 to answer the call, the TMS (MSS) 2710 establishes the call in the normal way.

If the local subscriber uses the fixed SIP phone 2716 to answer the call, the CSP (PBX) with IP 2714 establishes the call with the SIP UA on the TMS (MSS) 2710 and the TMS (MSS) 2710 in turn establishes the call

ES 2 554 541 T3 with the mobile device 2702 of the user who has made the call (via the subsystem of the pico base station 2706 and the SAD (DAS) 2708). Once the call has been established, the media flows of the call are routed between the mobile device 2702 that has been called and the landline SIP 2716 that is making the call (where any transcoding that is necessary can be performed by a CBS (SBC) that is used in order to couple the 2706 pico base station subsystem to the corporate IP LAN).

If the called user uses the UC 2726 endpoint to answer the call, the UC 2724 server establishes the call with the SIP UA on the 2710 TMS (MSS) and the 2710 TMS (MSS) establishes the call. calling with the calling user's mobile device 2702 (via the pico base station subsystem 2706 and the SAD (DAS) 2708). Once the call is established, the media streams of the call are routed between the calling mobile device 2702 and the UC 2726 endpoint that has been called (where any necessary transcoding can be performed by a CBS (SBC) which is used to couple the 2706 pico base station subsystem to the corporate IP LAN).

Figure 31 illustrates an example where someone uses a UC 2726 endpoint (such as a computer) to call a UC 2726 user point. The UC 2724 server that handles synchronous communications is configured to ring the UC 2726 endpoint. UC 2726 of the called user (or, otherwise, at the UC 2726 endpoint of the called user that an incoming call is being attempted) in the normal way. Also, the UC server 2724 causes the SIP landline phone 2716 of the user who has been called using the CSP (PBX) with IP 2714 to ring as normal. In this example, the UC server 2724 is also configured to interact with the SIP UA on the TMS (MSS) 2710 in order to cause the called user's mobile device 2702 to ring (if mobile device 2702 is camped on the company's 2700 mobile network at the time). As noted, the SIP UA on the TMS (MSS) 2710 appears to be, from the perspective of the UC 2724 server, another SIP device.

If the called user uses a UC 2726 endpoint to answer the call, the UC 2724 server establishes the call between the UC 2726 endpoint that is calling and the UC 2726 endpoint that is being called from the normal way. Likewise, if the called user uses the 2716 landline SIP phone to answer the call, the 2724 UC server and the 2714 IP-based CSP (PBX) establish the call with the 2716 landline SIP phone in the normal way. .

If the user uses the mobile device 2702 in order to answer the call, the UC server 2724 establishes the call with the SIP UA on the TMS (MSS) 2710 and the TMS (MSS) 2710 in turn establishes the call with the user's mobile device that has been called 2702 (via the pico base station subsystem 2706 and the SAD (DAS) 2708). Once the call is established, the media streams of the call are routed between the mobile device 2702 that has been called and the UC server 2724 that has made the call (where any necessary transcoding can be performed by means of a CBS (SBC) which is used to couple the 2706 pico base station subsystem to the corporate IP LAN).

Figure 32 illustrates an example in which a computer / telephone integration (CTI) 3202 application installed at the UC endpoint 2726 is used in order to remotely control the user's mobile device 2702. In this example, the TMS (MSS) 2710 includes a Computer Supported Telecommunications Applications (CSTA) / SIP 3204 interface that is used in order to interact with CTI applications that may be running on UC 2726 endpoints. In this example, the CTI application 3202 is designed to remotely control the user's mobile device 2702. For example, UC technology may include a function called click to cali, a method by which a user can click some part of the UI of the UC 2726 endpoint in order to initiate a call. This click-to-call function can be extended to initiate a call using the mobile user device 2702. When the user makes such a one-click call, the CTI 3202 application interacts with the CSTA / SIP 3204 interface on the TMS (MSS) 2710 indicating that the TMS (MSS) 2710 should initiate an originating mobile (MO) call. from mobile device 2702, which TMS (MSS) 2710 proceeds to do if the user of mobile device 2702 is camped on company mobile network 2702. If the call is answered, the TMS (MSS) 2710 establishes the call with the mobile device 2702 and the called party as if the user had used the mobile device 2702 to make the call.

In the examples described above in connection with Figures 27-32, the MSS 2710 can be configured with the intention of providing presence information to the UC 2724 server about the mobile device 2702 for use by the UC 2724 servers. (for example, to display presence information about 2702 mobile devices on a UC client (such as Microsoft Office Communicator 2007) running on UC 2726 endpoints).

Figure 33 illustrates another example of deployment of a mobile network of the 3300 company in which the technology described above (for example, a pico base station of multiple TRX and a SAD (DAS)) can be deployed in order to provide coverage and capacity for 3302 GSM / GPRS mobile devices located within a 3304 enterprise.

ES 2 554 541 T3

The example shown in figure 33 is similar to that shown in figure 22 except that there is no locally deployed IP CSP (PBX) within one or more of the 3304 company offices. example shown in figure 22, the mobile network of company 3300 shown in figure 33 includes a base station pico subsystem 3308 and a SAD (DAS) 3310 that are provided within each office of company 3304 . Also, each base station pico subsystem 3308 is coupled to a TMS (MSS) 3312 located at the operator's central office 3314. In this example, the TMS (MSS) 3312 serves as the MSCA / LR for those 3302 mobile devices that They are located within a coverage area associated with the mobile network of the 3300 company. Also, the TMS (MSS) 3312 implements the GMSC and the HLR functionality for the local subscribers of all the offices of the 3300 company. Each base station pico subsystem 3308 is coupled to the TMS (MSS) 3312 over an IP Network 3316.

As with the example shown in Figure 22, the company mobile network 3300 shown in Figure 33 includes a GSN 3318 that is coupled to mobile devices 3302 at each company office 3304 via the 3316 IP network. GSN 3318 is used to provide GPRS data service to 3302 mobile devices while they are camped on the 3300 company's mobile network. The GSN 3318 is also connected to an IP 3320 network via which the GPRS service is provided. The central office 3314 also includes a media gateway (MGW) 3322 that switches calls and performs any necessary media conversions. The 3314 central office also includes a 3324 router to couple the 3312 TMS (MSS), 3318, and 3322 MGW to the 3316 IP network.

As noted above, in the example shown in Figure 33, there is no IP-based CSP (PBX) deployed locally within the 3304 company offices. Instead, the IP-based CSP (PBX) software Virtual 3328 runs on the 3312 TMS (MSS) so that the 3312 TMS (MSS) can act as a CSP (PBX) for the 3300 enterprise for both 3302 mobile devices and any other SIP devices (such as SIP landlines 3330). The CSP (PBX) software with virtual IP 3328 and SIP devices communicate with each other over the IP 3316 network using the SIP protocol for signaling and an appropriate media format (such as the Real-Time Transport Protocol ( PTTR (RTP))) for call data. The virtual 3328 IP CSP (PBX) is also configured to associate a CSP (PBX) extension number with a 3330 SIP landline phone in such a way that calls made to that associated CSP (PBX) extension number will cause the associated 3330 SIP landline to ring.

In this example, each 3304 company office includes a 3350 access gateway that is controlled by the 3328 virtual IP CSP (PBX) software (for example, using the Media Gateway Control Protocol (MGCP )). Gateway 3350 serves as a local gateway to PSTN (PSTN) 3326 such that call data sent to or from SIP phones 3330 or mobile devices 3302 can be communicated to PSTN (PSTN) 3326 without having to go through TMS (MSS) 3312 and PLMN (PLMN) 3306. Gateway 3350 is coupled to SIP phones 3330 and pico base station subsystem 3308 over a corporate IP LAN (not shown in Figure 33). The access gateway 3350 performs whatever media conversion is necessary between the formats used by the media on the company mobile network 3300 and the formats used on the PSTN (PSTN) 3326). The software of the CSP (PBX) with virtual IP 3328 (and the devices attached to it) can also access the PSTN (PSTN) 3326 via the PLMN (PLMN) 3306.

The 3328 Virtual IP PBX (CSP) software is used to provide Centrex-like services that wireless providers have historically provided for wireline landlines. The 3328 virtual IP CSP (PBX) software running on the 3312 TMS (MSS) implements Centrex-type features such as short number dialing, outgoing calls using a designated special digit (e.g. number 9) and the restriction of outgoing calls. The 3328 Virtual IP CSP (PBX) software can be coupled to a voicemail server to provide voicemail service for users of the 3300 enterprise mobile network.

As the CSP (PBX) with local IP is shown in figure 22, the software of the virtual central office CSP (PBX) with IP 3328 of figure 33 is configured to ring both the fixed SIP phone 3330 and the mobile device 3302 associated with a specific local subscriber when an incoming call is made to a number associated with any of those devices.

In the above examples, a public IP network such as the Internet is used to communicatively couple the pico base station subsystem (and any TMS (MSS) deployed within the enterprise) to the wireless operator equipment. As a result, signaling bearer IP traffic and call data need to be secured. Figure 34 illustrates an approach to a method for securing IP traffic. As shown in figure 34, the functionality of the security gateway (SEG) 3450 is deployed in the subsystem of the pico base station 3406, a router 3410 is used in order to couple the elements deployed in the company 3400 to a public IP network 3418, the router 3426 used to couple the elements deployed in the office of the wireless operator 3416 to the public network IP 3418, on the TMS (MSS) 3412 in the wireless operator's office 3416 and on the Media Gateway (MGW) 3422 deployed in the wireless operator's office 3416.

ES 2 554 541 T3

In this example, the IP traffic that passes between company 3404 and the wireless operator's office 3416 is secured using Internet Protocol Security (IPSEC). The SEG 3450 functionality supports the IPSEC protocol and is used to implement a virtual private network over which said IP traffic can be communicated securely, where the SEG 3450 functionality is used at each end of each VPN channel. In this example, the devices on the 3400 network use the Secure RTP Protocol in order to further guarantee the media streams that are communicated over the public IP 3418 network, while signaling the data (for example, data from Ater-over-IP, Gb-over-IP data and / or SIP data) is secured using the underlying IPSEC channel.

The SEG (Secure Gateway) 3450 functionality can be integrated into the relevant network element (e.g. on the 3406 pico base station subsystem or 3412 TMS (MSS) (if there is sufficient processing capacity to do so) and / or on 3410 and 3426 routers and 3422 media gateway) or provided by a separate device deployed with the relevant network element where the relevant network element does not have sufficient processing capacity to implement SEG 3450 functionality (for example by implementing a CISCO router supporting the Relevant security features where the TMS (MSS) 3412 does not have sufficient processing power to implement the SEG 3450 functionality by itself).

Also, in the example described here, a SIP user agent is deployed in the TMS (MSS) with the intention of coupling the elements of the mobile network to the elements of the SIP-based network (including SIP servers such as a CSP (PBX) with IP or a UC server). However it should be understood that fixed-mobile convergence (FMC) can be implemented in other ways. For example, mobile devices themselves can run a SIP client to act as a partner in such SIP systems (as defined by the 3GPP / IMS specifications) using a packet-switched core network. However, when a company's mobile network is unable to support this type of approach (for example, because the company's mobile network does not implement UMTS), other approaches can be used. For example, SIP server functionality can be integrated in the TMS (MSS), a SIP user agent can be deployed in the TMS (MSS), or a SIP user agent can be deployed in the base station subsystem.

Figure 35 illustrates how SIP server functionality can be integrated into a TMS (MSS) 3500 as part of an FMC solution. As shown in Figure 35, the TMS (MSS) 3500's MSC (switching) 3502 functionality is extended to support the SIP Proxy 3504 feature, the SIP Redirect 3506 redirect feature, and the SIP Registrar feature. Register 3508. The VLR 3510 of the TMS (MSS) 3500 is enhanced to support the location function of SIP Location 3512. The HLR 3514 of the TMS (MSS) 3500 is extended to save the SIP profile 3516 of each subscriber with the GSM subscription information. The Authentication Center (AUC) 3518 in the TMS (MSS) 3500 is expanded to support the SIP authentication algorithms 3520.

In this example, the TMS (MSS) 3500 can be used to support SIP devices and SIP servers such as SIP phones and a CSP (PBX) with IP. The TMS (MSS) 3500 can also be configured to provide GSM services for SIP phones. Examples of such GSM services include basic call assistance, mobility management, supplementary services, prepaid services, call data recording (CDR) / call statistics, voice announcements, and mail. voice.

As discussed above in connection with Figures 22-26, the SIP user agent can be implemented in the TMS (MSS).

Figure 36 illustrates how a SIP user agent can be implemented in a base station subsystem. The example shown in Figure 36 is implemented in a modified version of the company's mobile network 2200 described above in connection with Figures 22-26.

In the example shown in FIG. 36, the SIP user agent (SIP UA) 3650 is implemented in a pico base station subsystem 3608, rather than in a TMS (MSS) 3612.

When a local subscriber mobile device 2202 performs a location update, the SIP3650 UA in the 3608 pico base station subsystem registers the local subscriber with the IP 2228 CSP (PBX). The SIP 3650 UA, from From the perspective of the CSP (PBX) with IP 2228, it seems to be another normal SIP device.

When a user uses a 2230 SIP phone to call the extension of the CSP (PBX) of a local subscriber of the 2200 company mobile network, the 2228 IP CSP (PBX) causes the associated 2230 landline SIP phone to ring with the extension of the CSP (PBX) that has been called. In this example, the IP CSP (PBX) 2228 is also configured to interact with the SIP UA 3650 in order to ring the mobile device 2202 of the called party. From the perspective of the IP 2228 CSP (PBX), the SIP 3650 UA in the 3608 pico base station subsystem appears to be a normal SIP device and the 2228 IP CSP (PBX) uses standard SIP signaling to let the SIP 3650 UA to recognize that a call has been received by the party that has been

ES 2 554 541 T3 call. The SIP AU 3650, in turn, generates the appropriate GSM signaling messages from the SIP messages received from the CSP (PBX) with IP 2228 and generates the appropriate SIP messages from the SIP from the GSM signaling messages it receives from mobile device 2202 (via pico base station subsystem 3608). If user uses the mobile device 2202 to answer the incoming call, the CSP (PBX) with IP 2228 establishes the call with the SIP AU in the subsystem of the pico base station 3608 and the subsystem of the pico base station 3608 establishes in turn the call with the mobile device of the party that has been called 2202 (via the subsystem of the pico base station 3608 and the SAD (DAS) 2208). Once the call is established, the media streams of the call are routed between the mobile phone 2202 that has been called and the SIP phone 2230 that has made the call (where any necessary conversion can be performed through CBS (SBC ) which is used to couple the 3608 pico base station subsystem to the 2232 corporate IP LAN).

The methods and techniques described herein can be implemented in a digital electronic circuit or with a programmable processor (for example, a special-purpose processor or a general-purpose processor such as a computer), firmware, software, or in combinations of the above. themselves. Apparatus incorporating these techniques may include appropriate input and output devices, a programmable processor, and a storage medium that incorporates the tangible program instructions for execution of the programmable processor. A process in which these techniques are incorporated can be carried out by a programmable processor that executes a program of instructions to carry out the desired functions to operate on the input data and that generates the appropriate orders. The techniques can be advantageously implemented in one or more programs that are executable in a programmable system including at least one programmable processor coupled to receive the data and instructions and to transmit data and, a data storage system, at least one input device, and at least one output device. Typically, a processor will receive instructions and data from read-only memory and / or random access memory. Storage devices suitable for tangibly holding computer program data and instructions include all forms of non-volatile memory, including, by way of example, semiconductor memory devices such as EPROM, EEPROM, and memory devices. flash; magnetic drives such as internal hard drives and portable drives; magneto-optical discs and DVD discs. Any of the above can be supplemented by or by incorporation into specially designed application-specific integrated circuits (ASICs).

A number of embodiments of the invention defined by the following claims have been described. However, it will be understood that various modifications of the described embodiments can be made without leaving the scope of the claimed invention. Accordingly, other embodiments are within the scope of the following claims.