PL2337393T3

Self-configuring cellular basestation

Abstract

This record has no abstract on file.

Term

Term ended

Projected expiry passed 28 July 2026, 0.2 years ago.

1 claim: 1 independent, 0 dependent

1
Patent claims Zastrzeżenia patentowe 1. Base station (110) for use in a cellular telecommunications network, which base station is adapted to:1. Stacja bazowa (110) do zastosowania w komórkowej sieci telekomunikacyjnej, która to stacja bazowa jest przystosowana do: odbierania z systemu zarządzania (160) listy dozwolonych nośnych;wykrywania sygnałów transmitowanych przez otaczaj ące stacje bazowe na kanałach rozgłoszeniowych na dozwolonych nośnych;receiving from the management system (160) a list of allowed carriers;detecting signals transmitted by surrounding base stations on broadcast channels on allowed carriers;dokonywania wyboru nośnej z listy dozwolonych nośnych przeznaczonych do użycia przez stacj ę bazową;making a carrier selection from the list of approved carriers intended for use by the base station;dokonywania ekstrakcji informacji systemowej z kanałów rozgłoszeniowych otaczaj ących stacji bazowych;extracting system information from broadcast channels surrounding base stations;using said extracted system information to create a BA list;and transmitting the BA list. wykorzystania wspomnianej wyekstrahowanej informacji systemowej w celu stworzenia listy BA;oraz transmitowania listy BA. 2. The base station of claim 1, further adapted to report the BA list to said management system. 2. Stacja bazowa według zastrzeżenia 1, przystosowana ponadto do raportowania listy BA do wspomnianego systemu zarządzania. 3. The base station of claim 1, wherein the cellular telecommunications network is a GSM network. 3. Stacja bazowa według zastrzeżenia 1, w której komórkowa sieć telekomunikacyjna jest siecią GSM. 4. The base station of claim 1, wherein the cellular telecommunications network is a UMTS network. 4. Stacja bazowa według zastrzeżenia 1, w której komórkowa sieć telekomunikacyjna jest siecią UMTS. 5. The base station according to any one of the preceding claims, adapted to authenticate with the management system using a subscriber identification module, Subscriber Identity Module, before receiving said list of allowed carriers. 5. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, przystosowana do uwierzytelniania z systemem zarządzania z wykorzystaniem modułu identyfikacji abonenta, Subscriber Identity Module, przed odebraniem wspomnianej listy dozwolonych nośnych. 6. A base station according to any one of the preceding claims, comprising a radio frequency receiving path (226, 228), and adapted to receive signals at system download link frequencies using said receiving path. 6. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, zawierająca tor odbiorczy częstotliwości radiowej (226, 228), a także przystosowana do odbierania sygnałów na systemowych częstotliwościach łącza pobierania z wykorzystaniem wspomnianego toru odbiorczego. 7. The base station according to any one of the preceding claims, further adapted to monitor the strength of the signals of the detected signals transmitted by the surrounding base stations. 7. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, przystosowana ponadto do monitorowania siły sygnałów wykrytych sygnałów transmitowanych przez otaczaj ące stacje bazowe. 8. The base station according to any one of the preceding claims further adapted to monitor the carrier ratio to the interference of the detected signals transmitted by the surrounding base stations. 8. Stacja bazowa według dowolnego z poprzednich zastrzeżeń przystosowana ponadto do monitorowania stosunków nośnej do zakłóceń wykrytych sygnałów transmitowanych przez otaczaj ące stacje bazowe. 9. A base station according to any one of the preceding claims, wherein the carrier selection step from the list of allowed carriers for use by the base station comprises the carrier selection step of said list having the minimum received power for detecting signals transmitted by the surrounding base stations. 9. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, w której etap wyboru nośnej z listy dozwolonych nośnych do wykorzystania przez stacj ę bazową zawiera etap wyboru nośnej ze wspomnianej listy maj ącej minimalną odbieraną moc przy detekcji sygnałów transmitowanych przez otaczaj ące stacje bazowe. 10. A base station according to any one of the preceding claims, wherein the base station is further adapted to select an initial power level for transmission from the base station. 10. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, w której stacja bazowa jest ponadto przystosowana do wyboru początkowego poziomu mocy dla transmisji ze stacji bazowej. 11. A base station according to any one of the preceding claims, adapted to share a common LAN connection with at least one other base station. 11. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, przystosowana do współdzielenia wspólnego połączenia sieci lokalnej LAN z co najmniej jedną inną stacj ą bazową. 12. A base station as claimed in any preceding claim, comprising: 12. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, zawierająca: radio frequency receiving path;radio frequency transmission path;and network connection;ścieżkę odbiorczą częstotliwości radiowej;ścieżkę transmisyjną częstotliwości radiowej;oraz połączenie z siecią;gdzie, przy instalacji, stacja bazowa jest przystosowana do: where, at installation, the base station is adapted to: configuring the radio frequency receiving path to work in a wireless telecommunications network;konfigurowania ścieżki odbiorczej częstotliwości radiowej w celu pracy w bezprzewodowej sieci telekomunikacyjnej;monitoring the strength of received signals on each of the numerous carrier networks established;monitorowania siły odbieranych sygnałów na każdej z założonych licznych nośnych sieci;dokonywania wyboru, na podstawie wspomnianych sił odbieranych sygnałów, pierwszej wspomnianej grupy nośnych sieci jako roboczej nośnej łącza pobierania;a także dokonywania wyboru, na podstawie sił odbieranych sygnałów wspomnianej wybranej pierwszej grupy założonych nośnych sieci, początkowego poziomu mocy dla wspomnianej ścieżki transmisyjnej częstotliwości radiowej;oraz gdzie stacja bazowa jest ponadto przystosowana do pracy z wykorzystaniem wspomnianej roboczej nośnej łącza pobierania i odpowiedniej roboczej nośnej łącza wysyłania, po wspomnianej instalacji. making a selection based on said received signal strengths of said first network carrier group as a working download link carrier;and selecting, based on the strength of the received signals of said selected first group of assumed network carriers, an initial power level for said radio frequency transmission path;and wherein the base station is further adapted to operate using said operational download link carrier and the corresponding operational upload link carrier after said installation. 13. A base station as claimed in any preceding claim, comprising: 13. Stacja bazowa według dowolnego z poprzednich zastrzeżeń, zawieraj ąca: a radio transceiver system for connection to wireless telecommunication devices via a cellular wireless telecommunications protocol;and an interface for connection via an IP network (170);wherein the base station is adapted to communicate using UMA protocols via said IP network with a UMA network controller to obtain communication with said wireless telecommunications devices via said cellular wireless telecommunications protocol. układ nadajnika-odbiornika radiowego do połączenia z bezprzewodowymi urządzeniami telekomunikacyjnymi za pośrednictwem protokołu komórkowej telekomunikacji bezprzewodowej;oraz interfejs do połączenia za pośrednictwem sieci IP (170);gdzie stacja bazowa jest przystosowana do komunikowania się z wykorzystaniem protokołów standardu UMA za pośrednictwem wspomnianej sieci IP z sieciowym kontrolerem UMA, w celu uzyskania komunikacji ze wspomnianymi bezprzewodowymi urządzeniami telekomunikacyjnymi za pośrednictwem wspomnianego protokołu komórkowej telekomunikacji bezprzewodowej. Authorized: Ubiquisys Limited Uprawniony: Ubiquisys Limited Pełnomocnik: Proxy: dr inż. Robert Teofilak Patent Attorney dr inż. Robert Teofilak Rzecznik patentowy ETHERNET: ETHERNET: :Τ - ·> (to the Network and POTS k Local) ,: :Τ -·> (do Sieci i POTS k Lokalnej),: VolP Codec VolP Kodek Figura 2 Figure 2 Figura 1 Figure 1 Network Sieć Frame Szkieletowa P switch Przełącznik P Network Sieć Radiowa radio UNC UNC IP przez DSL lub kabel IP via DSL or cable And a cell phone I elefon komorkowy Dom/ House/ Biuro Office Base station Stacja bazowa Phone / Fax Telefon/Fax 214 c 214 c c c Interfeis Interfeis H H USB USB USIM USIM Ethernet Ethernet Aparat — FLASH Camera - FLASH Protocol Protokołu 802.11b / g 802.11b/g SPRAM ] SPRAM] ADSL ADSL ARM9xx ARM9xx Modem / Router! Modem/Router ! Transceiver transceiver CPUbus / "230 CPUbus /"230 Accelerator Akcelerator Accelerator Akcelerator GSMRF GSMRF Analogowy analog Interfejs interface Modemu modem GSM / UMTS Baseband Modem Modem Pasma Podstawowego GSM/UMTS Kodowania coding Przetwarzania processing Packages (AES / 3DES) Pakietów (AES/3DES) UMTS RF UMTS RF SLfC SLfC Odniesienie Czas/ Reference Time / Power Zasilanie Częstotliwość Frequency Base Station Management System System Zarządzania Stacji Bazowej SNDCP SNDCP RR / GRR RR/GRR Zdalne remote IP IP GPRSL1 GPRSL1 Figura 3 Figure 3 312 312 310 310 302 302 Control of the ZoneGame session Sterowanie sesją StrefaBramka 304 304 NAS306 r308 <314 NAS306 r308 <314 320 n 320 n - control motion fi = - Session control -sterowanie ruch fi =-Sterowanie Sesją Web server Web serwer DHCP server DHCP serwer OSG server OSG serwer 316 <LISIM SMS 316 < LISIM SMS 348 348 UMA-Client UMA-Klient SIP-Client SIP-Klient JMA-RRC / RLC / RRJ JMA-RRC /RLC/RRJ RTCP RTCP RTP RTP SDP SDP UMTS UMTS GERAN aj LLC [ GERAN aj LLC [ 332 332 - RLC - RLC 342 342 356 356 ABOUT O Kodeki codecs FAKS FAX MAC MOTHER 344 344 Dźwięku fuMTS L1, FuMTS L1 sound, 362 362 346 346 366 366 364 364 324 324 358 358 POTS l / F POTS l/F LAN l / F LAN l/F USB l / F USB l/F 352 switching 352 przełączanie IP transporting horizontal access levels IP transportującej poziomy poziomy dostępu Figura 7 szerokopasmowa sieć IP Figure 7 Broadband IP network Figura 6 Figure 6 Up up SGSN lu-CS SGSN lu-CS Base Station Stacja Bazowa AAL2 AAL2 UNC UNC MSC broadband IP network MSC szerokopasmowa sieć IP AAL2SAR AAL2SAR SSCS SSCS RTP / UDP or UP RTP/UDP lu UP Remote IP Zdalne IP IPSecESP IPSecESP RTP / UDP RTP/UDP Remote IP Zdalne IP IPSecESP IPSecESP MAC MOTHER IP transporting access levels IP transportujące poziomy dostępu dostępu GMM / SM / GMM/SM/ SMS SMS RRC RRC RLC RLC MAC MOTHER LI LI GMM / GMM/ SIW SIW RANAP RANAP SCCP nośnik sygnalizacji SCCP signaling medium AAL5 AAL5 ATM ATM AMR codec AMR kodek RLC RLC MAC MOTHER AMR codec lu UP AMR kodek lu UP AAL2SAR AAL2SAR SSCS SSCS AAL2 AAL2 ATM ATM IP transporting access levels IP transportujące poziomy dostępu IP transporting access levels IP transportujące poziomy dostępu Base Station Stacja Bazowa RRC RRC Figura 8 Figure 8 1601 1601 1611 1611 1603 1603 1609 1609 Figura 16 Figure 16 1721 1721 Figura 17 cn Figure 17 cn Figura 19 Figure 19 Figura 20 Figure 20 Figura 21 Figure 21 Figura 22 co Figure 22 co Figura 23 £- σ> co ΣΞ ο ο rz Ci Ώ S Figure 23 £ - σ> what you think -cj- ^ = Γ -cj- ^=Γ Λ | Μ Ol OJ CM ίΝ Λ| Μ Ol OJ CM ίΝ Figura 24 Figure 24 Figura 25 Figure 25 Figura 26 Figure 26 Figura 27 Figure 27 ZJ ZJ Figura 29 Figure 29 DOCUMENTS CITED IN THE DESCRIPTION DOKUMENTY CYTOWANE W OPISIE Ta lista dokumentów cytowanych przez Zgłaszającego została przyjęta jedynie dla informacji czytającego i nie jest częścią europejskiego opisu patentowego. Została ona utworzona z dużą starannością;Europejski Urząd Patentowy nie ponosi jednak żadnej odpowiedzialności za ewentualne błędy i braki. This list of documents cited by the Applicant was accepted only for the information of the reader and is not part of the European patent specification. It was created with great care;However, the European Patent Office shall not be liable for any errors or omissions. Dokumenty patentowe cytowane w opisie • US 6314294 B [0005] • US 20040224716 A1 [0007] • US 2004166867 A [0006] Patent documents cited in the description • US 6314294 B [0005] • US 20040224716 A1 [0007] • US 2004166867 A [0006]

388 paragraphs, as filed

[0001] The present invention relates to a cellular base station, and in particular to a base station for a cellular telecommunications network that can be conveniently used to provide cellular services, e.g. within a home or office. [0002] Broad range cellular services for standards such as GSM and UMTS are provided from ordinary base stations capable of covering a large area (cell radius of the order of many kilometers). However, indoor coverage can be a greater challenge, due to the attenuation of the RF signal by the building structure and due to the effects of signal reflection from neighboring buildings. This coverage problem is becoming increasingly embarrassing for standards focused on supporting medium or high bandwidth data transmission, such as EDGE and UMTS, due to the higher signal-to-noise ratios required for signals using higher order constellations and low scattering indicators. Higher frequencies such as those used for UMTS also highlight this problem, because these signals are more attenuated by building constructions.

[0003] A classic solution to these problems will be the deployment of many subsequent base stations and RF relay systems to increase interior coverage of buildings and urban areas. Such solutions become disproportionately expensive, and the additional impact on the aesthetics of this much larger number of base stations / antennas creates opposition from residents and increases the legal costs of operators. The use of short-range radio links such as WiFi and Bluetooth to support cellular communication inside the home or office is an alternative approach, but requires the client or operator to invest in new phones, which on a large scale is a considerable expense in itself.

[0004] Recent indicators suggest that more than 70% of all cellular connections are made inside buildings, so this issue presents several significant obstacles to the future development of the cellular industry.

[0005] US-6 314 294 discloses a wireless telecommunications system that is capable of performing self-configuration activities. That is, each base station is capable of receiving signal strength measurements between the base station and the cell phones connected to it. These signal strength measurements are reported to the network node, which is then able to assign channels to base stations in the system in order to obtain the reuse of the desired frequency.

[0006] US-2004/166867 discloses a wireless LAN in which access points are capable of selecting their own channel. When an access point is added to the LAN, it scans the supported channels over that network, and also selects a channel for its own use, for example, choosing a channel on which it is unable to detect transmission from any other access point or the weakest transmitting channel signal.

[0007] US2004 / 0224716 A1 discloses how a terminal uses a BCCH Allocation list (BCCH) to make a cell selection.

[0008] According to a first aspect of the present invention, there is provided a base station for use in a cellular telecommunications network, which base station is adapted to:

receiving from the management system an approved list of carriers;

detecting signals transmitted by surrounding base stations on broadcast channels on allowed carriers;

making a carrier selection from the list of approved carriers intended for use by the base station;

extracting system information from the broadcast channels of the surrounding base stations;

using said extracted system information to create a BA list; and transmitting the BA list.

Brief description of the drawings [0009]

Figure 1 is a block diagram of a telecommunications system comprising a base station according to the present invention;

Figure 2 is a block diagram of the base station hardware architecture of the present invention;

Figure 3 is a block diagram of the base station software architecture of the present invention;

Figure 4 illustrates part of the system protocol architecture according to embodiments of the present invention;

Figure 5 illustrates part of the system protocol architecture according to embodiments of the present invention;

Figure 6 illustrates part of the system protocol architecture according to embodiments of the present invention;

Figure 7 illustrates part of the system protocol architecture according to embodiments of the present invention;

Figure 8 illustrates part of the system protocol architecture according to embodiments of the present invention;

Figure 9 illustrates a process according to an aspect of the present invention;

Figure 10 illustrates a process according to an aspect of the present invention;

Figure 11 illustrates a process according to an aspect of the present invention;

Figure 12 illustrates a process according to an aspect of the present invention;

Figure 13 illustrates a process according to an aspect of the present invention;

Figure 14 illustrates a process according to an aspect of the present invention;

Figure 15 illustrates a process according to an aspect of the present invention;

Figure 16 illustrates a process according to an aspect of the present invention;

Figure 17 illustrates a process according to an aspect of the present invention;

Figure 18 illustrates a process according to an aspect of the present invention;

Figure 19 illustrates a process according to an aspect of the present invention;

Figure 20 illustrates a process according to an aspect of the present invention;

Figure 21 illustrates a process according to an aspect of the present invention;

Figure 22 illustrates a process according to an aspect of the present invention;

Figure 23 illustrates a process according to an aspect of the present invention;

Figure 24 illustrates a process according to an aspect of the present invention;

Figure 25 illustrates a process according to an aspect of the present invention;

Figure 26 illustrates a process according to an aspect of the present invention;

Figure 27 illustrates a process according to an aspect of the present invention;

Figure 28 illustrates a process according to an aspect of the present invention; and Figure 29 illustrates a process according to an aspect of the present invention.

[0010] Figure 1 illustrates a communication system 100 comprising a base station 110 according to the present invention. In this exemplary embodiment, base station 110 is designed to provide indoor coverage, such as a home or office 120, for calls and data services using both GSM / GPRS and UMTS wireless connections within an existing cellular network, allowing using existing 122 cell phones, without requiring significant modification. As described in more detail below, base station 110 also provides a flexible connection to the network operator's backbone network 130 via Unlicensed Mobile Access (UMA) or Session Initiation Protocol (SIP), as opposed to regular interfaces or ( UMTS) or Abis (GSM) used by standard cellular base stations. The backhaul from base station assemblies, referred to as ZoneGates, is implemented through the use of a Digital Subscriber Line (DSL) 140 on an established home or office telephone line; this approach allows cheap data and call transfer using Internet telephony (VoIP, Voice-over Internet Protocol) techniques.

[0011] Figure 2 is a block diagram illustrating in more detail aspects of the base station 110 hardware architecture.

[0012] The architecture includes a plurality of function blocks interconnected via a processor bus 202, such as the AMBA ARM bus. The main blocks are described below.

[0013] First, base station 110 supports various external wired connections as described below.

[0014] Preferably, base station 110 includes an embedded ADSL modem / router 204. The router's functionality will include a NAT and a DHCP server.

[0015] USB 1.1 206 interface. In the absence of an internal ADSL modem / router, this USB 206 interface will support connection of an external DSL modem. If the internal ADSL 204 modem is built-in, the USB 206 interface provides connection of a local PC to the broadband internet service and advanced configuration and control of the base station 110.

[0016] RJ45 Ethernet 10/100/1000 208 interface. This interface provides connection to an external local area network (e.g. home or office) (not shown in figure 2) for advanced configuration and control of base station 110 and allows the base station to access to external devices to provide advanced services. Along with the built-in ADSL 204 modem, the Ethernet 208 socket is used for broadband internet service as a more flexible alternative to the USB 206 socket.

[0017] As described in more detail below, a plurality of base station assemblies 110 installed in the extensive space inside the building and connected to a common Ethernet LAN can manage switching between them without the involvement of other systems in the operator's radio network 150, or in the backbone network 130.

[0018] Classic RJ11 POTS telephone connection socket (Plain Old Telephone Service). The telephone and fax POTS services are supported via the RJ11 telephone socket. The SLIC 210 device controlling this connector can be advantageously configurable to support numerous national standards, including, for example, Great Britain, Germany, France, Italy, Spain, Japan and the United States of America. Voice services are provided via VoIP using the appropriate standard 212 codecs. An analog fax service is also supported. This socket does not provide power to the line.

[0019] USIM 214 interface. Base station 110 will have support for the Subscriber Identification Module (SIM) card connector to enable the use of a standard SIM card for unambiguous device identification in management system 160, and in network operator radio network 150, and on the core network 130, and hence will enable the inclusion of certain services, as described in more detail below.

[0020] Base station 110 includes a Protocol Engine 216 (Protocol Engine) implemented as a small, embedded CPU, such as, for example, ARM926 (with proper peripherals) supported by dedicated coprocessors 218, 220 according to the coding and processing of packets that will offload the main processor CPU for particularly demanding tasks. The protocols implemented in the 216 protocol engine include:

Session control, including web server, DHCP server, OSGi server;

GSM / UMTS access layer functions (NAS)

Functions of the UMA Client GERAN access layer; and

SIP client.

[0021] Packet Processing Accelerator 220 supports forming packets flowing to / from the GSM / GPRS layer 1 function implemented in the Baseband Modem 222 and forming packet streams to / from the UMTS layer 1 function implemented in the band modem Basic (Baseband Modem) 222. The packet processing accelerator 220 also forms VoIP packets to / from the POTS interface. The VoIP codec functions are provided by the Baseband Modem 222.

[0022] Encryption of the contents of the IPSec package is supported by the Encryption Accelerator 218. The AES and 3DES encryption protocols will be supported. Only the VPN connection between ZoneGate (Gateway Zone) and the UNC / management system will use internal encryption processing; user VPN encryption processing will be handled outside base station 110.

[0023] The main CPU processor 216 is also responsible, through the main processor bus 202, for the configuration and control of all system function blocks including baseband modem 222, USB 206 socket, Ethernet 208 socket and, optionally, ADSL 204 modem / router and WiFi 224 transceiver. An image of the system software containing the configuration data of all function blocks is stored in FLASH 226, inside base station 110; two full system images are stored, so that updated system images can be downloaded by base station 110 from management system 160, while the previous image is left as a backup in case the image is damaged during download.

[0024] Peripherals of the main CPU include:

supervisory counters (watchdog timers) for checking the correct operation of the program;

JTAG connection and serial ports for system debugging;

General purpose GPIO I / O ports for system control, including LED status indicators, system power management, and system alarm collection.

[0025] Base station 110 supports sample rate processing, chip-rate processing (only UMTS), and symbol rate processing for GSM modems and base station UMTS, and supports simultaneous GSM and UMTS operation. A limited GSM mobile terminal (MS, Limited GSM Mobile Station) and UMTS modem functionality of user equipment (UE, User Equipment) will also be implemented to enable the base station to obtain a broadcast channel (BCH, Broadcast Channel) from local GSM / UMTS base stations and from nearby similar base stations 110. The device will enter UE modem mode during the first installation to examine the local RF environment, and at constant intervals after the first installation to check the RF environment and, if necessary, modify the configuration of the base station 110.

[0026] The DSP signal processor functionality included in baseband modem 222 is also used to implement the VoIP codec.

[0027] The baseband modem is implemented using a software-based architecture to ensure that the modem is highly adaptable to operating conditions for at least 5 years. The operation of GSM and UMTS baseband modems is suitable for stationary users or those traveling on foot at a speed not exceeding 10 km / h within a 50 m radius of base station 110. The baseband 222 modem, which is based on software, can be updated to allow future transition to HSDPA or EDGE services so that it can be delivered in field conditions without having to replace the device. [0028] Base station 110 has an RF GSM 226 system and an UMTS 228 RF system, each of which is connected to a baseband modem 222 via an analog modem interface 230 to support simultaneous operation of GSM on either 900MHz or 1800MHz and UMTS on 2100MHz. For GSM and UMTS receiving tracks, both send link frequencies (reception at the base station) and download links (reception at the terminal) are available; only the download link frequencies (broadcast at the base station) are available for the transmission paths. During installation, base station 110 selects the RF carrier frequency of the transmission link with the lowest noise / interference ratio for both GSM and UMTS from the list of allowed GSM and UMTS carrier frequencies provided from the management system 160; the allowed transmission frequencies will be scanned by the base station 110 with its receiving path configured in UE mode and with its receiving path turned off.

[0029] The base station 110 is designed to provide a cellular service at a distance of 50m or less for stationary or pedestrian users within the building, hence the required transmit power is drastically limited compared to conventional base stations.

[0030] Base station 110 includes time and frequency standards 236 that will provide sufficient accuracy for the operation of the GSM base and UMTS for a period of 5 years.

[0031] The base station thus provides a service platform that can utilize the potential of connecting three data networks within base station 110, namely an external backbone network (via DSL), mobile devices (via GSM / UMTS) and a home network (via Ethernet).

[0032] Figure 3 shows the main elements of the protocol software architecture implemented in the protocol engine processor 216.

[0033] Base station session control subsystem 302 manages and implements service and security flows that determine how base station 110 is configured and how it works for each specific configuration of the mobile network operator (MNO, mobile network operator) and end customer. Session control functions include:

Implementing security for registration, connection control and traffic flow for the base station in the MNO backbone;

Control of UMA and SIP clients for registration, call control and traffic flow;

Information flow control with a network based management system; Resource management of the Radio Access Network (RAN) for registering mobile phones and transferring calls;

Control and implementation of methodologies for MNO and end-customer services; Base station packet core management; and Handling Java-based application requests for network resources.

[0034] Non-Access Stratum 304 functionality is required for services to be provided to the UE while the MNO operator's GSM / UMTS backbone is not connected to the base station, which will usually be the case the base station connects via SIP. This functionality enables base station 110 to offer normal GSM / UMTS services such as SMS and MMS to which mobile users are accustomed when not connected to the GSM / UMTS 130 backbone network. In order to offer such services, base station 110 contains a concise subset of backbone network functions usually contained in a mobile switching center (MSC), a node offering GPRS services (SGSN, Serving GPRS Service Node), a GSM base station subsystem (BSS, GSM Basestation Subsystem) and the UMTS radio network subsystem (RNS, UMTS Radio Network Subsystem).

[0035] The access-free layer 304 as used in the base station 110 includes the following functions:

[0036] Connection control (CC) 306 - ensures the establishment of a telephone connection between two equal units, mainly for circuit switched connections. For the base station, it also provides mapping between the established SIP connection and the switched voice call to GSM and UMTS.

[0037] Session management (SM) 308 - controlling packet data sessions.

[0038] Short message service server (SMS) 310 - sending an SMS between the base station and the network's SMS service center.

[0039] Multimedia messaging service server (MMS) 312 - multimedia messaging between the base station and the network's MMS service center.

[0040] Additional services (SS) 314 - providing such services as call waiting, call hold, conference calls.

[0041] Mobility management / GPRS mobility management (MM / GMM) 316 management of UE mobility components, such as Location Registration, authentication, encryption.

[0042] USIM 318 - control of functions related to the SIM card which can be placed in the base station 110.

[0043] The access layer (Access Stratum) 320 includes lower level functionalities that are specific to the GSM EDGE radio access network (GERAN), and UMTS. The GERAN functionality is selected for GSM, GPRS, and EDGE access, and the UMTS functionality for UMTS enabled services.

[0044] The GERAN access layer functionality 322 includes both BSS (layer-1 324, radio resources 326, radio link control 328 / media access control 330) and SGSN functionality (connection layer 332 control and subnet convergence protocol 334). The BSS functionality is required for the base station to support all GSM / GPRS / EDGE services, regardless of the interface used between the base station and the MNO operator's backbone network. SGSN functionality is only required when the MNO operator's GERAN backbone functionality is bypassed, for example for SIP, or Internet-based services through GERAN.

[0045] Thus, the functionality of GERAN access layer 322 includes the following components:

[0046] Sub-Network Dependent Convergence Protocol (SNDCP) 322 - multiplexing several packet data protocols; data compression / decompression (optional); header compression / decompression (optional), splitting and recombining.

[0047] Logical Link Control (LLC) 332 - LLC provides direct peer-to-peer data transfer without or with confirmation, and GPRS encryption functionality.

[0048] Radio link control / media access control (RLC / MAC, Radio Link Control / Medium Access Control) 328, 330 - RLC / MAC supports modes with and without confirmation; segmentation and recombining of LLC control PDUs; multiplexing of several physical channels; broadcasting system information.

[0049] Radio Resource Management (RR) 326 RR connection establishment, service and release; system information broadcasting, packet data resource management.

[0050] Layer 1 GSM / GPRS 324 - interface for modem functions

GSM / GPRS / EDGE used in the 222 baseband modem.

[0051] The functionality of the UMTS access layer 336 includes the functionality of the radio network controller (RNC) (radio resource control, packet data compliance protocol, radio link control / media access control) and the interface to the UMTS physical layer implemented in baseband modem 222. RNC and physical layer interface functionality is required by all base station services supporting UMTS regardless of the backbone interface used.

[0052] The functionality of UMTS 336 access layer includes the following elements: [0053] Packet Data Convergence Protocol (PDCP) 338 - header compression and decompression of IP data streams (optional), user data transmission, PDCP order number support.

[0054] Radio Resource Control (RRC) 340 broadcast of information related to NAS and AS; establishing, servicing and releasing RRC connections; establishing, reconfiguration and disconnection of radio bearers (Radio Bearers) and radio resources; RRC connection mobility functions; control of QoS requests; reporting and control of UE device measurements; external loop power control; encryption control.

[0055] Radio Link Control (RLC) 342 - sending and receiving signaling packets and data, including buffering, splitting and bundling. Contains three types of units, for confirmed mode, no confirmation mode, and transparent modes.

[0056] Medium Access Control (MAC) 344 mapping between logical channels and transferring channels, selecting the appropriate transfer formats (Transport Formats) for each transferring channel, handling priority between UEs, multiplexing / demultiplexing higher layer PDUs to / from the transfer block (block sets) on common and allocated transfer channels.

[0057] Layer 1 UMTS 346 - interface to the UMTS modem functions used in baseband modem 222.

[0058] The software architecture shown in Figure 3 also includes the UMA client 348. Base station 110 uses the UMA protocol in a custom configuration. The standard UMA protocol is designed to allow GSM MS stations or UE UMTS devices that include a UMA client and a non-licensed wireless interface, such as IEEE802.11b / g or Bluetooth, to communicate with the GSM / UMTS backbone network using the band niekoncesjonowanego. The base station implementation used in the present invention uses the UMA 348 client as part of the GSM / UMTS base station network interface so that UMA protocols created to communicate with the GSM / UMTS backbone network via an unlicensed network controller (UNC) can be used to manage telephone connections served by this base station, including forwarding to / from the parent network.

[0059] The use of UMA in a base station according to the present invention is described in more detail below.

[0060] SIP client 350. Base station 110 maps GSM / UMTS protocols to SIP client protocol so that standard GSM / UMTS cellular services are mapped by the base station to the corresponding SIP services. This approach eliminates the need for SIP protocols or SIP services to be presented or implemented in MS stations / UEs. For example, a standard GSM / UMTS voice connection is mapped to a SIP VoIP connection at base station 110, which also includes mapping the additional signaling required to register a user in the SIP backbone, and initiating, terminating, and clearing the voice connection. To implement GSM / UMTS signaling at the base station, a complete GSM / UMTS protocol stack is required, which includes BSS / RNS, and MSC / SGSN functionality.

[0061] The software architecture shown in Figure 3 also includes IP Transport Layers 352. IP transfer layers 352 include standard Internet protocols such as UDP 354, TCP 356, and IPv4 358. Additional protocols are implemented to provide base station 110 of required signaling functionality. IPSec 360 is required to provide an encrypted and secure transmission medium between base station 110 and backbone network 130 which is required to maintain a secure connection between portable user device 122 and backbone network 130. This is especially important because encrypted coding is a standard feature for the GSM / UMTS wireless interface, and coding is necessary for the transmission of secure information such as encryption and security keys between base station 110 and core network 130. To ensure mobility within a packet network , remote IP 362 is implemented.

[0062] The program architecture shown in Figure 3 also includes functionality of 370 switched circuits, including a set of voice codecs 364 to enable standard POT telephone connections (to a standard analog telephone) to the backbone network using SIP (VoIP). In addition, the 366 Fax codec allows you to connect a standard fax device to the base station for sending and receiving faxes over the internet, again using SIP (FoIP). [0063] The base station 110 is a compact device designed to be placed on a desk or internal wall or ceiling within a home or office. What is unusual for a GSM / UMTS base station, installation of cells is not required for installation in order to mount base station 110 due to low levels of emitted power and self-configurability to the frequency / encryption code.

[0064] After physical installation, insertion of the SIM card (if necessary) and connection of an external DC power supply and network connection via DSL or cable, the base station 110 performs the following sequence of actions:

1. Establishes communication with the base station management system 160, terminates authorization in the management system using data stored on the SIM, and downloads various configuration parameters, including the "list of allowed" carrier frequencies and UMTS encryption keys, which the network operator providing base station services has chosen to admit.

2. The RF receiving path is configured to operate on GSM cell phone download link frequencies so that nearby GSM base stations (and other operational base stations according to the present invention) can be detected and identified. The baseband 222 modem is then configured as the baseband receiver of a GSM cell phone so that synchronization and broadcast channels transmitted by surrounding base stations can be fully demodulated and the system information parameters recovered. Then, base station 110 monitors each carrier frequency from the allowed list by measuring the base station signal strength as if it were a GSM cell phone in accordance with GSM standards. Information about the strength of the signals, and the broadcast channel of the detected base stations is stored for future reference.

3. The RF receiving path is configured to operate on UMTS download link frequencies, and the baseband modem is configured as a UMTS user device capable of demodulating primary and secondary synchronization channels (to determine the encryption code) and the broadcast channel so that system information messages can be recovered. Then, base station 110 successively controls each of the UMTS carrier frequencies and encryption codes from the allowed list by measuring the carrier (C / I) to interference ratio for each of the detected base stations (including other base stations according to the present invention) in the same the way the UE UMTS device does. The obtained C / I ratio and system information data recovered for each base station is stored for future reference.

4. Base station 110 then selects the GSM carrier and UMTS carrier and the encryption code from the allowed list with the least received strength from the surrounding base stations (including other base stations according to the present invention) on the basis that these carriers will cause the least interference to the surrounding macrocells / microcells or other base stations according to the present invention. The RF transmission paths for GSM and UMTS are configured for selected carrier frequencies and encryption keys ready for operation. Base station RF receiving paths 110 are configured to monitor the send link frequency corresponding to the selected download link carriers according to the standardized pairing of the download link carriers and the send link in Frequency Division Duplex schemes for GSM and UMTS.

5. Then base station 110 selects the initial signal levels for GSM and UMTS transmission paths. The correct signal level is deduced from the received signal strength / C / I ratio detected by the base station 110. The goal is that the power level of the transmitted signal is sufficient to provide cellular services at a distance of 20 m assuming the level of in-band interference created by the surrounding base stations (including other base stations of the present invention). Transmission power is changed during the connection to maintain satisfactory quality of service (QoS) according to GSM and UMTS standards - base station RF equipment 110 imposes an upper limit of transmitted power that is low enough to prevent unacceptable interference by the base station 110 in case of software failure.

6. System information obtained from broadcast channels surrounding GSM and UMTS base stations is used to create the BA list for GSM and UMTS broadcast channels, which is transmitted by base station 110 according to GSM and UMTS standards. This BA list identifies the surrounding base stations that should be monitored by the cell phone receiving the BA list in readiness to switch when the signal level from the base station 110 received by the cell phone falls below acceptable limits. The BA lists for GSM and UMTS are forwarded to the 160 management system.

7. Base station 110 will start transmission on selected GSM and UMTS carriers with selected initial power levels.

8. If base station 110 is part of a group of base stations according to the present invention that share a LAN connection and can transfer calls to each other, then the BA list can be updated for other base stations within the group to allow the cell phone to switch between such base stations as described in more detail below.

[0065] The base station device 110 is designed to repeat the RF test process at regular intervals (every 1 to 10 days) following the first installation, so that changes in the RF environment can be detected and previous carrier / encryption code decisions may have been re-determined if necessary. [0066] As mentioned above, base station 110 uses the protocols defined by the UMA standard in an innovative way to enable base station 110 to connect on broadband IP 170 network with UMA UNC 152, and thus ensure connectivity between the mobile station (MS) 122 and GSM / UMTS 150 radio networks (to ensure imperceptible switching) and backbone network 130 (to provide standard GSM / UMTS services). The base station software protocol stack 110 maps the standard GSM / UMTS wireless protocol to the UMA protocol, as shown in Figure 4 for the UMA-to-GSM case, and as shown in Figure 5 for the UMA-to-GPRS case.

[0067] For GSM (figure 4), the relay function within the base station protocol stack maps the GERAN (RR) radio resource protocol directly to the UMA-RR protocol, which terminates in UNC 152. Base station 110 requires full implementation of the UMA sub-layer -RR to connect to an MS (MS stations) 122 that are currently registered with the base station. A subset of RR tasks is passed to the UMA-RR sub-layer to connect to the backbone network (e.g. forwarding).

[0068] For GPRS (figure 5), the base station implements RLC / MAC sub-layers to connect to a registered MS (registered MS stations) 122. The relay function within base station 110 maps RLC / MAC sub-layers to sub-layers UMA-RLC layer that ends at UNC 152.

[0069] The UMA-UMTS control layer is shown in figure 6. Base station 110 implements UMTS RRC, RLC, and MAC sub-layers, while encryption is implemented in both RLC and MAC. The UMA-RRC sub-layer additionally includes UMTS related signaling. UNC 152 can be upgraded to include a lu interface that connects to 3G-SGSN. The higher layers of GMM, SM, and SMS are included in 3G-SGSN and connect to their nodes in the EU.

[0070] For the UMAN-UMTS voice service (figure 7), voice traffic is sent via RLC and MAC sub-layers, where encryption is performed in MAC. Voice traffic is transferred using RTP / UDP between base station 110 and UNC 152. UNC 152 routes voice traffic through lu-CS to 3G-MSC, which includes the backbone AMR codec.

[0071] For the UMAN-UMTS user layer (figure 8), IP user data is transferred to base station 110 using PDCP, RLC, and MAC sub-layers. The base station implements UMLC's RLC and MAC sub-layers, while encryption is implemented in the RLC sub-layer. The PDCP sub-layer may be moved to the base station rather than the indicated location in UNC 152, but this depends on future UNC implementation.

[0072] For GERAN encryption, the encryption keys and other information elements must be transferred to base station 110 from the parent backbone 130, firstly so that CIPHERING MODE messages can be transferred between base station 110 and the MS device 122, and secondly that GSM layer 1 of base station 110 can encrypt and decrypt subsequent control messages and user layer messages. The main condition and change in the specification of the UMAN protocol is the requirement of the encryption key value Kc at base station 110 so that encryption and decryption of GSM layer 1 messages can take place at the base station. It is proposed that the Kc value be received in an additional message received from UNC 152. Therefore, it is proposed that the next two messages constitute an extension of the standard UMA message set:

<td>Name of the message</td><td>Description</td><td>Content</td>

<td>URR CIPHERING KEY REQUEST (KEY REQUEST ENCRYPTING URR)</td><td>base station request that the encryption key be sent via the network to the base station</td><td>Lack.</td>

<td>URR CIPHERING KEY RESPONSE (ANSWERING THE URR CODE KEY)</td><td>response from the web containing the encryption key</td><td>1. 64-bit Kc GSM encryption key 2. a status word indicating whether the request was successful or unsuccessful</td>

[0073] In the case of switching from GERAN to UMAN, the new Kc value is included in the GERAN A-HANDOVER REQUEST message sent from MSC to UNC 152, which is not currently sent to MS 122 or base station 110. The content of the A-HANDOVER REQUEST message regarding encryption must be forwarded to the base station to start encryption as soon as the switchover is completed (if encryption is active and enabled after switching).

[0074] In the case of switching from UMAN to GERAN, the value of Kc is already transmitted to base station 110 (via modified CIPHERING MODE COMMAND messages) during the procedure of configuring encryption for UMAN. The Kc value is passed to the target BSS via the A-HANDOVER REQUEST message from the MSC, so no further modification is required.

[0075] The encryption configuration for GSM is made as shown in figure 9 and as described in the following steps below:

901. The backbone 130 sends to UNC 152 a BSSAP CIPHER MODE COMMAND command that contains the GSM Kc encryption key and an encryption algorithm that should be used by UNC (and MS).

903. UNC 152 sends the URR-CIPHERING MODE COMMAND command to base station 110, which indicates whether encryption should be started or not (after switching to GERAN), if so, which algorithm to use, and the random RAND number. The message also indicates whether the MS should include IMEI in the URR CIPHERING MODE COMPLETE message (COMPLETED URR ENCRYPTION MODE).

905. Base station 110 requests the value of the Kc encryption key from the network by sending a proprietary URR-CIPHERING KEY REQUEST message, as described above.

907. UNC 152 sends the value of the encryption key to base station 110 in the URR-CIPHERING KEY RESPONSE message, as described above. The encryption key value can be sent by UNC 152 only if the base station connection - UNC is encrypted. If the base station has not been allowed the Kc value, or the link is not encrypted or the current request is incorrect, then the response message should not contain the encryption key and its status should be set to "Incorrect encryption key", otherwise the status should be set to "Valid encryption key".

909. The base station generates and sends to MS 122 the CIPHERING MODE COMMAND command, indicating whether encryption is enabled or not, and if so, which algorithm to use. The content of this message is based on the URR CIPHERING MODE COMMAND command.

911. MS 122 returns a CIPHERING MODE COMPLETE message, optionally containing the International Mobile Equipment Identity (IMEI).

913. The Message Authentication Code (MAC) is calculated by base station 110 from the input value RAND, Kc, IMSI, using the HMAC-SHAI-96 algorithm, and returned with the IMEI, if so indicated, in the URR CIPHERING MODE message COMPLETE (COMPLETED URR ENCRYPTION MODE).

915. UNC 152 checks the MAC. If the MAC checked by the UNC is correct, then the UNC sends a CIPHERING MODE COMPLETE message to the core network 130.

[0076] For UMTS encryption, the encryption keys and other information elements are to be forwarded to the base station from the parent backbone network in order, first, that SECURITY MODE messages can be transmitted between the base station and the UE 122, and after second, so that the UMTS layer 2 of the base station can encrypt and decrypt subsequent control messages and ordinary user layer messages. The main requirement and change in the specification of the UMAN protocol is the presence of the UMTS CK (Cipher Key) encryption key and the UMTS IK (Integrity Key) consistency key in the base station so that encryption and decryption can be performed at the base station. It was proposed that CK and IK values should be received in an additional message received from the UNC controller. Thus, the following two messages have been proposed as an extension for UMA:

<td>Name of the message</td><td>Description</td><td>Content</td>

<td>URR SECURITY KEY REQUEST (KEY REQUEST secured URR)</td><td>Request from the base station that the CK encryption key and IK consistency key be sent to the base station via the network</td><td>Lack</td>

<td>URR SECURITY KEY RESPONSE (SAFETY KEY ANSWER URR)</td><td>A response from the network containing an encryption key and a consistency key</td><td>1. 128-bit key CK UMTS encrypting 2. 128-bit key IK UMTS consistency 2. A word of status indicating whether the request was successful or not.</td>

[0077] When switching from UMTS to UMAN, new CK and IK values are included in the lu-RELOCATION REQUEST message sent from 3G-SGSN to UNC, which are currently not forwarded to the UE or to the base station. The content related to encryption in the lu-RELOCATION REQUEST message must be forwarded to the base station to initiate the encryption process as soon as the switching is completed (as long as encryption is active and enabled after switching).

[0078] In the case of switching from UMAN to UMTS, the CK and IK values have already been forwarded to the base station (via modified SECUIRTY MODE COMMAND messages) during the UMAN encryption configuration procedure. The CK and IK values are forwarded from 3G-SGSN to the target RNS subsystem via the lu-RELOCATION REQUEST message, thus requiring no further modification. [0079] Configuration of UMTS encryption is performed as shown in Figure 10, and in the sequence of steps below:

1001. The backbone 130 sends a RANAP SECURITY MODE COMMAND message to the UNC 152 controller, which contains the CK encryption key and the IE consistency key for UMTS, and the encryption algorithm (s) that should (should) be used by UNC ( and UE device).

1003. UNC 152 sends a URR-SECURITY MODE COMMAND message to base station 110, which indicates whether encryption should be started or not (after switching to UMTS), and if so, which algorithm to use, RAND random number, marker AUTH authentication. The message also indicates whether the UE should include the IMEI in the URR SECURITY MODE COMPLETE message.

1005. Base station 110 requests the value of the CK encryption key and the IK cohesion key for UMTS from the network by sending a proprietary URR-SECURITY KEY REQUEST message (URR SAFETY KEY REQUEST) as described above. 1007. UNC 152 sends the value of the encryption key in the URRSECURITY KEY RESPONSE message, as described above, to base station 110. The encryption key value can be sent by UNC only if the base station - UNC connection is encrypted. If the base station is not assigned CK and IK values, or the link is not encrypted, or the current request is incorrect, then the response message should not contain the encryption key, with the status set as "invalid encryption key", otherwise the status should be set to 'valid encryption key'.

1009. Base station 110 generates and sends a SECURITY MODE COMMAND message to UE 122, indicating whether encryption is enabled or not, and if enabled, which algorithm should be used. The content of this message is based on the URR SECURITY MODE COMMAND message.

1011. The UE 122 returns the SECURITY MODE COMPLETE message, optionally containing an IMEI.

1013. It is calculated by base station 110, MAC from the input values RAND, CK, IK, and IMSI, using the HMAC-SHAI-96 algorithm, and returned together with IMEI, if so indicated, in the URR SECURITY MODE COMPLETE message (FINISHED MODE SAFETY URR).

1015. The UNC 152 controller checks the MAC. If the UNC determines that the MAC is valid, it sends a SECURITY MODE COMPLETE message to the core network 130.

[0080] Base station 110 maps all UMA procedures to GSM / UMTS procedures, and vice versa. The mapping is implemented in the following sections.

Detection and Registration Procedures [0081] UMA detection and registration procedures as shown in figure 11 are performed when the respective mobile station selects base station 110 via PLMN GSM / UMTS selection and cell selection procedures. The mobile station may also make a PLMN reselection that is mapped to the UMA disclosed (rove-in) procedure. The sequence shown in Figure 11 assumes that the UE does not have active voice or packet sessions on GERAN (i.e., it is in rest mode). UE 122 may have IMSI and / or GPRS attached on GSM or UMTS networks. The detection and recording procedures are the same for both GSM and UMTS.

[0082] The following sequence of steps is performed:

[0083] The UE performs the location registration procedure by sending a LOCATION UPDATING REQUEST message 1101 via an Um or Uu interface which also contains the UE's IMSI. The base station can discuss LOCATION UPDATING REQUEST requests early by sending LOCATION UPDATING REJECT 1103 as long as the UE 122 is not registered with the base station due to the wrong IMSI.

[0084] Base station 110 performs UMAN detection and registration procedures 1105 and 1113 to inform the UNC that a specific UE is available at a specific base station. The controller stores a trace of this information to provide services (e.g., terminated cellular connections).

[0085] If detection and logging is rejected by a UNC controller (messages 1107 or 1115), then ZoneGate generates a LOCATION UPDATING REJECT message (1109 or 1117) and sends it to a mobile phone.

[0086] After successful registration (messages 1111 or 1119), base station 110 forwards the original LOCATION UPDATING REQUEST message to the SGSN core network (message 1121).

[0087] The core network 130 performs authentication and encryption procedures during location registration to authenticate the UE 122 in the core network and set the encryption parameters before starting encryption. The backbone signals a successful location registration by sending the LOCATION UPDATING ACCEPT 1123 message to the UE. The UE is now registered in the backbone network and successfully embedded in the base station cell.

The deregistration procedure [0088] The deregistration procedure is illustrated in figure 12. IMSI DETACH message (IMSI DISCONNECTION) 1201 may originate from a mobile phone and be sent to base station 110, where it is mapped to the de-registration element URR 1203 and sent to the UNC controller. The URR DEREGISTER message 1205 can also come from a UNC controller and be sent to base station 110, where it is mapped to an IMSI DETACH message 1207, which is sent from the base station to cell phone 122. The deregistration procedure is same for both GSM and UMTS.

Voice connection procedure originated in a mobile telephone [0089] The voice connection procedure originated in a mobile telephone, shown in figure 13, uses standard GSM signaling between the base station and the portable terminal MS 122, which is mapped to the signaling defined for UMA. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document. The procedure is similar for both GSM and UMTS.

[0090] The sequence of steps shown in figure 13 is detailed below:

[0091] The CM Service Request 1301 is sent from the mobile phone 122 to the controller 152 via the uplink direct transfer wrapper 1303.

[0092] Authentication is performed transparently with direct link send and download link messages 1305, 1307, 1309, 1311.

[0093] For GSM, the URR Ciphering Mode Command 1313 is sent from the UNC 152 to base station 110, which maps it to the Ciphering Mode Command 1315 sent from the base to the mobile phone 122. The Ciphering Mode Complete message 1317 is sent from the mobile phone 122 to the base station which maps it to the URR Ciphering Mode Complete message 1319. For UMTS, Security Mode messages 1321, 1323 , 1325, 1327 replace the Ciphering Mode messages 1313, 1315, 1317, 1319.

[0094] CM Service Accept 1331 is sent from the UNC controller 152 to the base station via a URR downlink direct transfer wrapper message 1329, and forwarded by the base station to cell phone 122.

[0095] The setup 1333 message is sent from the mobile phone 122 to the base station, and is forwarded to the UNC controller in the uplink direct transfer message 1335. The Call Proceeding message 1339 is sent from the UNC to the station the base in the downlink direct transfer wrapper 1337, and forwarded by the base station to the mobile phone.

[0096] The URR Activate Channel message 1341, 1349 sent by the UNC controller to base station 110, is mapped to a Channel Mode message 1343 for GSM, or to Radio Bearer Reconfiguration 1351 for UMTS, and sent to a mobile phone. The Channel Mode Modify Acknowledge 1345 message is sent from a mobile phone to a GSM base station, or a Radio Bearer Reconfiguration Complete message 1353 for UMTS, and is mapped to a URR Activate Channel Ack message URR for channel activation) 1347, 1355, and sent from base station 110 to the UNC.

[0097] Alerting and Connect messages 1361, 1365 are sent from UNC controller 152 to the base station in URR downlink direct transfer wrapper messages 1359, 1363, and forwarded by the base station to the phone phone. A Connect Acknowledge 1367 message is sent from the mobile phone to the base station, and forwarded in a URR uplink transfer message 1369 to the UNC to complete the connection setup procedure initiated by the mobile phone.

Voice call terminated mobile phone procedure [0098] The voice call terminated mobile phone procedure illustrated in figure 14 uses standard GSM signaling between the base station and the MS / UE 122 terminal / device which is mapped to the signaling defined for UMA. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document. The procedure is similar for both GSM and UMTS.

[0099] The message exchange shown in figure 14 is described in the sequence of steps below:

[0100] A URR PAGING REQUEST message 1401 is sent from the UNC to the base station to start a voice call terminated by a mobile phone. The PAGING REQUEST message 1403 is generated by the base station and transmitted to the terminal / MS / US device. The MS PAGING RESPONSE message 1405 is received by the base station that generates and sends the URR PAGING RESPONSE 1407 to the UNC. For UMTS, the base station generates the PAGING TYPE 1 message 1411 to the UE, which corresponds to the CELL UPDATE procedure 1413.

[0101] The UNC controller performs authentication procedures on direct download link and send link messages 1419, 1421, 1423, 1425, and encryption procedures thanks to CIPHERING MODE COMMAND messages and CIPHERING MODE COMPLETE messages 1427, 1429, 1431, 1433 for GSM or SECURITY MODE messages 1435, 1437, 1439, 1441 for UMTS. [0102] The remainder of the connection setup procedure is transparently performed by transmitting and receiving by the UNC controller of direct download link and uplink transfer messages. Base station 110 hides each send and download link message within the required messages of the wireless interface SETUP (1443-1445), CALL CONFIRMED (1447-1449), ALERTING (1451-1453), CONNECT (1455) - 1457), and CONNECT ACKNOWLEDGE (CONFIRMATION OF MERGER) (1459 - 1461).

URLC Transmission Channel Activation Procedure [0103] The procedures for activating the URLC transmission channel shown in Figure 15 are defined by UMA procedures that are mapped to PDP Context Activation procedures for the GPRS wireless interface. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document. The procedures for activating the transmission channel are the same for both GSM and UMTS.

[0104] The message exchange shown in figure 15 is summarized in the sequence of steps below:

[0105] Activation of the URLC transfer channel may be started by the UE initiating the PDP Context Activation procedure. The ACTIVATE PDP CONTEXT REQUEST message 1501 is mapped to the URLC ACTIVATE UTC REQ message 1503, and the URLC message ACTIVATE UTC ACK (UTC ACK CONFIRMATION URLC) is received from the ACTIV controller PDP

CONTEXT ACCEPT 1507. If the URLC ACTIVATE UTC ACK message 1505 contains negative confirmation, an ACTIVATE PDP CONTEXT REJECT message is generated instead of the confirmation message.

[0106] Activation of the URLC transfer channel can be started by a UNC controller by sending an URLC ACTIVATE UTC REQ 1511. This message is mapped to a REQUEST PDP CONTEXT ACTIVATION message 1513 and sent to the EU. In response, the UE generates an ACTIVATE PDP CONTEXT REQUEST message 1515, which the base station maps to both the URLC ACTIVATE UTC ACK 1517 message (ACTIVATE UTC ACK CONFIRMATION) and ACTIVATE PDP CONTEXT ACCEPT ACTION ACTION. In this case, ZAP decides whether the PDP Context Activation procedure is successful and generates an ACTIVATE PDP CONTEXT REJECT message if it is not successful.

Procedure for deactivating the URLC transmission channel [0107] The procedures for deactivating the URLC transmission channel shown in Figure 16 are UMA-defined procedures that are mapped to PDP Context Deactivation procedures for a GPRS wireless link. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document. The procedures for deactivating the transmission channel are the same for both GSM and UMTS.

[0108] The message exchange shown in Figure 16 is summarized in the sequence of steps below.

[0109] Deactivation of the URLC transmission channel may be initiated by the UE or network.

[0110] The UE initiates the deactivation of the URLC transmission channel by sending a DEACTIVATE PDP CONTEXT REQUEST message 1601 to the base station that generates and sends the URLC DEACTIVATE UTC REQ message (URLC DEACTIVATE DEACTIVATE) 1603 to the UNC controller 1603. UNC 152 responds with the URLC DEACTIVATE UTC ACK message 1607 which is mapped by the base station to DEACTIVATE PDP CONTEXT ACCEPT (PDP CONTEXT DEACTIVATION) 1605 and sent to the MS terminal.

[0111] The network initiates the deactivation of the URLC transmission channel by sending the URLC DEACTIVATE UTC REQ message 1609 to the base station that generates and sends the DEACTIVATE PDP CONTEXT REQUEST message 1611. The UE responds with the message DEACTIVATE PDP CONTEXT ACCEPT 1613, which is mapped by the base station to URLC DEACTIVATE UTC ACK (URLC DEACTIVATE CONFIRMATION 1615) and sent to the UNC controller.

Paging procedures [0112] The paging procedures shown in figure 17 include the packet paging procedure for packet switching services, and the usual paging procedure for circuit switching services. Both paging procedures are always initiated by the network. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document.

[0113] The message exchange shown in figure 17 is summarized in the next steps below.

[0114] The packet recall procedure is initiated by the network by sending, from the UNC controller to the base station, URLC PS PAGE messages 1701 from the UNC controller to the base station, which is mapped to PAGING REQUEST 1703 and sent to the MS terminal. MS responds by sending an LLC UNITDATA packet or DATA 1705 packet to the base station which maps this message to a URLC UNITDATA or DATA 1707 message.

[0115] The calling procedure for circuit switching is initiated by the network by sending a URR PAGING REQUEST message from the UNC controller to the base station 1709, which is mapped to PAGING REQUEST 1711 and sent to the MS terminal. MS responds by sending PAGING RESPONSE 1713 to the base station that maps this message to URR. PAGING RESPONSE 1715 and sends it to the UNC controller.

[0116] The UMTS calling procedure is initiated by the network by sending, from the UNC to the base station, a URR PAGING REQUEST message 1717, which is mapped to a PAGING TYPE 1 message (17). The UE responds by sending CELL UPDATE 1721 to the base station that responds with the CELL UPDATE CONFRIM message 1725 and maps this message to the URR message PAGING RESPONSE 1723 and sends it to the controller.

Procedure for switching from GERAN to UMAN [0117] The GERAN to UMAN sequence shown in figure 18 assumes that the MS terminal has an active voice connection to GERAN. The following steps are carried out. It should be noted that the signaling of the network element between the UNC controller and the MSC and between BSS and MSC is only shown for clarification purposes. The contents of all messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document.

[0118] The message exchange shown in figure 18 is summarized in the following steps.

[0119] The MS terminal sends MEASUREMENT REPORTs reports continuously to the BSS subsystem 1801, 1803, 1805 etc. containing {ARFCN radio channel frequency number, BSIC base station identification code} of nearby cells. {ARFCN, BSIC} of base station 110 will be included in these measurement reports as long as the BCCH carrier power transmitted by the base station is sufficient and / or the base station ARFCN is transmitted in the BSC BA list (contained in the SYSTEM INFORMATION information transmitted by the BSS BSCH serving cell ).

[0120] Base station 110 should be reported by the MS terminal as having the highest signal level compared to neighboring and serving GERAN cells.

[0121] BSS internally maps {ARFCN, BSIC} base station 110 to a UMA CGI cell. GERAN decides to switch to a UMA cell by sending a HANDOVER REQUIRED 1807 message to the 130 MSC backbone network.

[0122] The core network 130 requests the target UNC controller 152 to allocate resources for handover using the HANDOVER REQUEST message 1809. UNC 152 should map the IMSI contained in the HANDOVER REQUEST message 1809 to its own base station 110. Destination base station 110 may or may not be base station 110 currently seen by the MS terminal.

[0123] The UNC 152 controller confirms the request using the HANDOVER REQUEST ACKNOWLEDGE 1811 message, indicating that it can handle the requested switch that also contains the content of the HANDOVER COMMAND indicating the radio channel parameters of its own base station 110, to which this MS terminal should be redirected.

[0124] The core network 130 forwards the HANDOVER COMMAND message 1813 to GERAN completing the switchover preparations.

[0125] GERAN sends a HANDOVER COMMAND 1815 message to the MS terminal to signal the switch to the base station. The HANDOVER COMMAND 1815 message contains ARFCN, PLMN color code, and BSIC of the target base station 110. The MS terminal does not switch its audio path from GERAN to UMAN until the switching process is completed.

[0126] The MS terminal accesses base station 110 using the HANDOVER ACCESS message 1817. The switch reference contained in the HANDOVER ACCESS message 1817 is forwarded to the UNC controller in the URR message HANDOVER ACCESS. SWITCHING URR) 1819, which allows the UNC operator to correlate the switching in the message HANDOVER REQUEST ACKNOWLEDGE 1811. [0127] The serving UNC controller 152 sets the transfer path with the base station and the MS terminal.

[0128] Base station 110 transmits the URR HANDOVER COMPLETE message 1827 to signal the completion of the handover procedure. The MS terminal switches from the GERAN user layer to the UMAN user layer.

[0129] Two-way voice traffic 1831, 1833, 1835 begins to flow between the MS 122 terminal and the core network 130 through the supporting UNC 152 controller. [0130] The target UNC signal indicates that the switching has been completed using the HANDOVER COMPLETE message.

SWITCHING) 1837. If you have not already done so, the backbone network switches the user layer from the source GERAN to the destination UMAN.

[0131] As required, the sequential backbone network 130 terminates the connection to the source GERAN using the CLEAR COMMAND message 1839.

[0132] Source GERAN approves the release of the GERAN resources allocated for this connection using the CLEAR COMPLETE message 1845.

Procedure for switching from UMAN to GERAN [0133] The sequence for switching from UMAN to GERAN shown in figure 19 assumes that the MS terminal has an active voice connection on UMAN. MS begins to leave the range of base station 110 according to the invention. The following steps are being taken. Note that the signaling of the network element between UNC and MSC, and between BSS and MSC is only shown for explanatory purposes. The content of the messages are defined in the UMA and 3GPP specifications and therefore will not be explained in this document.

[0134] The message sequence shown in figure 19 is summarized in the sequence of steps below.

[0135] The switch from UMAN to GERAN is triggered by measurement reports 1901, 1905 of carrier power levels for BCCH surrounding GERAN from the MS terminal. The UNC controller can send the optional URR UPLINK QUALITY INDICATION 1903 message based on the signal strength criterion.

[0136] Base station 110 detects that a switch is required and sends a URR HANDOVER REQUIRED message 1907 to the serving UNC 152 indicating the Channel Mode and the list of GERAN cells identified by the CGI in order to favor switching. Base station 110 may obtain a list of these CGIs by decoding System messages [0137] Information in the surrounding GERAN cells alone, or may obtain a list of these CGIs (and their corresponding ARFCN, BSIC) by accessing the appropriate database associated with its current geographical location (via zip code or other device showing geographical position).

[0138] The serving UNC controller 152 begins preparations for switching by signaling to the backbone with the message HANDOVER REQUIRED 1909.

[0139] The backbone network selects the target GERAN cell and requests it to allocate the resources it needs using the HANDOVER REQUEST 1911 message.

[0140] The target GERAN network creates a HANDOVER COMMAND message that provides information about the allocated channel and sends it to the backbone network via the HANDOVER REQUEST ACKNOWLEDGE message (CONFIRMATION OF SWITCH REQUEST) 1913.

[0141] The core network signals the serving UNC controller to switch the MS terminal to GERAN, using the HANDOVER COMMAND message 1915 to complete the switch preparation phase.

[0142] The serving UNC transmits, to base station 110, a URR HANDOVER COMMAND message 1917 containing details sent by GERAN regarding the allocation of destination resources. Base station 110 transmits, to terminal 122, a HANDOVER COMMAND message 1919 indicating that the MS terminal should switch to the GERAN cell.

[0143] The MS terminal transmits the HANDOVER ACCESS 1921 command containing the switch reference parameter to allow the target GERAN network to correlate the switch access with the HANDOVER COMMAND message previously sent to the backbone network in response to the HANDOVER REQUIRED message (REQUIRED SWITCHING).

[0144] The target GERAN confirms the detection of a switch to the backbone using the message HANDOVER DETECT 1923.

[0145] The core network may at this point switch the user layer to the target BSS.

[0146] GERAN provides PHYSICAL INFORMATION 1927 to the MS terminal, ie, time forward to allow the MS terminal to synchronize with GERAN.

[0147] The MS terminal signals to GERAN that switching has been completed using the HANDOVER COMPLETE message 1929.

[0148] GERAN confirms the completion of switching to the core network using the HANDOVER COMPLETE message 1931. If the user layer has not yet been switched, the core network switches the user layer to the target BSS.

[0149] Bi-directional voice traffic 1933, 1935 begins to flow between the MS terminal and the core network, via GERAN.

[0150] The core network signals the serving UNC controller to release all resources allocated to the MS terminal using the CLEAR COMMAND message 1937.

[0151] The serving UNC instructs the base station 110 to release resources using the URR RR RELEASE message 1939.

[0152] The serving UNC confirms the release of the backbone using the CLEAR COMPLETE message 1941.

[0153] Base station 110 confirms to the UNC serving the release of resources using the URR RR RELEASE COMPLETE message 1943.

[0154] Base station 110 may eventually unregister from the serving UNC using the message URR DEREGISTER (URR REGISTRATION) 1945.

Procedure for switching from Inter-RAT UMTS to UMAN-GERAN [0155] The sequence for switching from UMTS to UMAN-GERAN shown in Figure 20 assumes that the MS terminal has an active voice connection in the UMTS network. It is possible to generate a switch between a UMTS macro network and a UNC controller with only the GERAN standard and ZoneGate (Radio Zone Technology) by inter-RAT (Radio Access Technology) switching procedure (radio access technology). The following steps are being taken. It should be noted that the signaling of the network element between the UNC controller and the MSC, and between the BSS and MSC is only shown for clarification purposes. The contents of all messages shown are defined in the UMA and 3GPP specifications and will therefore not be explained in this document.

[0156] The message exchange shown in figure 20 is summarized in the following sequence of steps.

[0157] The MS 122 sends continuously to the RNS node B of the MEASUREMENT REPORTS base station 2001, 2003, 2005 containing (basic encryption code, UARFCN, cell identity) of surrounding UMTS cells, and {ARFCN, BSIC } surrounding GERAN cells, if MS was directed to monitor the surrounding GERAN cells in the "inter-RAT cell info" part of the CELL_INFO_LIST variable. If the BCCH carrier power transmitted by the base station is sufficient, {ARFCN, BSIC} base station 110 will be included in these measurement reports, as long as such inter-RAT measurements are enabled.

[0158] Base station 110 should be reported by the MS terminal as having the highest signal level compared to serving and neighboring UMTS cells.

[0159] RNS internally maps {ARFCN, BSIC} base station 110 to CGI of the UMA cell. The UMTS network decides to switch to a UMA cell by sending a RELOCATION REQUIRED 2007 message to the 3G-MSC backbone network.

[0160] The core network requests the target UNC to allocate resources for the switch using the HANDOVER REQUEST message 2009. The UNC should map the IMSI contained in the HANDOVER REQUEST to its own base station 110. Destination own base station 110 may or may not be the base station currently seen by the MS terminal.

[0161] The UNC target controller confirms the request using the HANDOVER REQUEST ACKNOWLEDGE 2011 message, indicating that it can support the switchover requested, which also contains the content of the HANDOVER COMMAND indicating the radio channel parameters of its own base station, to which he should be redirected.

[0162] The 3G-MSC backbone network forwards the RELOCATION COMMAND 2013 to the RNS, completing the switchover preparations.

[0163] The UMTS network sends HANDOVER FROM UTRAN COMMAND 2015 to the MS terminal to mark the switch towards base station 110. The message HANDOVER FROM UTRAN COMMAND 2015 contains ARFCN, PLMN color code and target BSIC base station 110. MS does not change its audio path from UMTS to UMAN until switching is completed.

[0164] The MS terminal gains access to the base station using the HANDOVER ACCESS 2017 message. The switch reference contained in the HANDOVER ACCESS message 2017 is forwarded to UNA in the URR message HANDOVER ACCESS ) 2019, which allows the operating UNC to correlate the switch with the message HANDOVER REQUEST ACKNOWLEDGE (CONFIRMATION OF SWITCH REQUEST) 2011.

[0165] The serving UNC controller sets the carrier path to base station 110 and MS terminal.

[0166] Base station 110 transmits the URR HANDOVER COMPLETE message 2027 to signal the completion of the handover procedure. The MS terminal switches the UMTS user layer to the UMAN user layer.

[0167] Two-way voice traffic 2031, 2033, 2035 begins to flow between the MS 122 terminal and the backbone network 130 via the supporting UNC 152 controller. [0168] The target UNC controller signals the completion of switching using the HANDOVER COMPLETE message 2037. If this is not yet done, the backbone network switches the user's UMTS source layer to the destination UMAN.

[0169] The backbone network terminates the connection to the source UMTS network using RELEASE COMMAND 2039.

[0170] The source UMTS network confirms the release of resources allocated to this connection using RELEASE COMPLETE 2041.

Procedure for switching Inter-RAT UMAN-GERAN to UMTS [0171] The sequence of switching Inter-RAT UMAN-GERAN to UMTS shown in figure 21 assumes that the MS terminal has an active voice connection on the base station network with UMAN functionality enabled. It is possible to generate a switchover between the base station with enabled UMAN functionality and only GERAN type and UMTS macro network through the Inter-RAT switching procedure. The following steps are carried out. Note that the signaling of the network element between the UNC and the MSC is only shown for clarification purposes. The contents of all messages shown are defined in the UMA and 3GPP specifications and will therefore not be explained in this document.

[0172] The message exchange shown in figure 21 is summarized in the steps below. The inter-RAT switching from UMAN to the UMTS macro-network is triggered by measurement reports 2101, 2105 of the MS terminal for BCCH carrier power levels {ARFCN, BSIC} of the surrounding UMTS macro-network. The UNC controller can send the optional URR UPLINK QUALITY INDICATION 2103 message based on the signal strength criterion.

[0173] Base station 110 detects that a switch is required and sends a URR HANDOVER REQUIRED message 2107 to the serving UNC controller indicating the channel mode and the list of GERAN cells identified by the CGI to favor switching. Base station 110 may obtain a list of these CGIs by decoding System Information messages in the surrounding GERAN cells themselves, or may obtain a list of these CGIs (and their corresponding ARFCNs, BSICs) by accessing the appropriate database associated with its current geographical location (via zip code) or other geographical indication device).

[0174] The serving UNC begins to prepare for switching by signaling this to the backbone network with the message HANDOVER REQUIRED 2109.

[0175] The core network selects the target UMTS cell and requests it to allocate the resources it needs using the RELOCATION REQUEST 2111 message.

[0176] The RNS UMTS target subsystem creates a HANDOVER COMMAND message that provides information about the allocated channel and sends it to the backbone network via the RELOCATION REQUEST ACKNOWLEDGE message 2113.

[0177] The core network signals the serving UNC to switch the MS terminal to the UMTS network, using HANDOVER COMMAND 2115, completing the switching preparation phase.

[0178] The serving UNC transmits to the base station 110 a URR HANDOVER COMMAND message 2117 containing details sent by the UMTS network regarding the allocation of destination resources. Base station 110 transmits HANDOVER TO UTRAN COMMAND 2119 to the MS terminal indicating that the MS should switch to the UMTS cell.

[0179] The MS terminal is detected by the target RNS of the UMTS network as a result of a lower level transmission from the MS. The target RNS confirms the detection of a switch to the backbone network using the RELOCATION DETECT message 2121.

[0180] The core network may, at this point, switch the user layer to the target RNS.

[0181] As soon as the MS terminal is synchronized with the UMTS RNS, the MS signals that switching has been completed using the HANDOVER COMPLETE message 2125.

[0182] The UMTS RNS subsystem confirms the backbone completing switching using the RELOCATION COMPLETE message 2127. If the user layer has not yet been switched, the backbone network switches the user layer to the target RNS.

[0183] Two-way traffic of user layer 2129, 2131 between terminal MS 122 and the core network begins to flow through the UMTS core network.

[0184] The core network signals the serving UNC controller to free all resources allocated to the MS terminal using the CLEAR COMMAND message 2133.

[0185] The serving UNC instructs the base station 110 to release resources using the URR RR RELEASE message 2135.

[0186] The serving UNC confirms the release of the backbone using the CLEAR COMPLETE message 2137.

[0187] Base station 110 confirms the serving UNC controller the release of resources, using the RR URR RELEASE COMPLETE 2139.

[0188] Base station 110 may eventually unregister from the serving UNC using the URR DEREGISTER message (URR REGISTRATION) 2141.

UMTS Switching to UMAN-UMTS [0189] The sequence of UMTS switching to UMAN-UMTS shown in figure 22 assumes that the UE has an active voice connection on the UMTS network. The following steps are carried out.

[0190] The UE sends, in a continuous mode to the RNS of the B-node of the base station, MEASUREMENT REPORTS 2201, 2203 containing {basic encryption code, UARFCN, cell identity} of surrounding UMTS cells.

[0191] Base station 110 should be reported by the UE as having the highest signal level compared to surrounding and serving UMTS cells.

[0192] The RNS subsystem internally maps the {base scramble code, UARFCN, cell identity} of the base station 110 to the CGI of the UMA cell. The UMTS network decides to switch to a UMA cell by sending the RELOCATION REQUIRED message 2205 to the 3GMSC backbone.

[0193] The core network requests the target UNC to allocate resources for handover using the RELOCATION REQUEST 2207. The UNC should map the IMSI contained in RELOCATION REQUEST 2207 to its own base station 110 UE device. The destination own base station may or may not be the base station currently seen by the UE.

[0194] The UNC target controller confirms the request using the RELOCATION REQUEST ACKNOWLEDGE 2209, indicating that it can handle the switchover that was requested, and also contains the RELOCATION COMMAND content indicating the radio channel parameters of its own base station the UE should be redirected.

[0195] The 3G-MSC backbone network forwards the RNOCATION COMMAND message 2211 to RNS, completing the switching preparations. [0196] The UMTS network sends the PHYSICAL CHANNEL RECONFIGURATION message 2213 to the UE to signal a switch towards the base station. PHYSICAL CHANNEL RECONFIGURATION contains information about the physical channel of the destination base station. The UE does not change its audio path from UMTS to UMAN until the switch is completed.

[0197] The UE is detected by the base station 110 by synchronizing Layer 1 and establishing a Layer 2 connection. It is transmitted from the base station to the UNC controller a URR message HANDOVER ACCESS 2215, which allows the UNC operator to correlate the switch with the message RELOCATION REQUEST ACKNOWLEDGE (CONFIRMATION OF RELOCATION REQUEST).

[0198] The serving UNC sets the carrier path for base station 110 and UE. [0199] Upon receipt of PHYSICAL CHANNEL RECONFIGURATION COMPLETE 2219 from the UE, the base station transmits the URR HANDOVER COMPLETE message 2221 to signal the completion of the switching procedure. The UNC controller transmits a RELOCATION DETECT message 2223 to the MSC.

[0200] The UE switches from the UMTS user layer to the UMAN user layer. Two-way voice and data traffic 2225, 2227, 2229 flows between the UE and the backbone network through the operating UNC. [0201] The target UNC indicates that switching has been completed using the RELOCATION COMPLETE message.

RELOCATION) 2231. If this has not already been done, the backbone network switches the user layer from the source UMTS to the destination UMAN.

[0202] The backbone network terminates the connection to the source UMTS network using RELEASE COMMAND 2235.

[0203] The source UMTS network confirms the release of resources allocated to this connection, using RELEASE COMPLETE 2237.

Switching from UMAN-UMTS to UMTS [0204] The sequence of switching from UMAN-UMTS to UMTS shown in figure 23 assumes that the UE has an active voice or data connection on UMAN in UMTS mode. The UE begins to leave the range of the base station 110. The following steps are performed.

[0205] The message exchange shown in figure 23 is summarized in the steps below.

[0206] Switching from UMAN to a UMTS macro-network is triggered by measurement reports 2301, 2305 BCCH carrier power levels {basic encryption code, UARFCN, cell identity} of the surrounding UMTS macro network. The UNC controller can optionally send URR UPLINK QUALITY INDICATION 2303 based on the signal strength criterion.

[0207] Base station 110 detects that handover is required, and sends a URR HANDOVER REQUIRED message 2307 to the serving UNC indicating a list of surrounding UMTS cells, identified by CGI in order to preferential handover. Base station 110 may obtain a list of these CGIs by decoding System Information messages in the surrounding UMTS cells themselves, or may obtain a list of these CGIs (and their corresponding UARFCN codes, basic encryption codes) by accessing the appropriate database associated with its current geographical location (by by postal code or other geographical indication device).

[0208] The serving UNC controller begins preparing for switching by signaling to the backbone using the RELOCATION REQUIRED message 2309.

[0209] The backbone network selects the target UMTS cell and requests, using RELOCATION REQUEST 2311, that it allocate the required resources.

[0210] The target RNS UMTS subsystem creates a RELOCATION COMMAND message providing information about the allocated channel and sends it to the backbone via the RELOCATION REQUEST ACKNOWLEDGE message 2313. [0211] The core network signals the serving UNC to switch the UE to the UMTS network using the RELOCATION COMMAND 2315 message, completing the switching preparation phase.

[0212] The serving UNC transmits, to base station 110, a URR HANDOVER COMMAND message 2317 containing details sent by the UMTS network regarding the allocated destination resources. Base station 110 transmits PHYSICAL CHANNEL RECONFIGURATION 2319 to the UE indicating that the UE should switch to the UMTS cell.

[0213] The UE is detected by the target RNS subsystem of the UMTS network as a result of the lower layer transmission from the UE. The target RNS confirms the detection of a switch to the backbone network using the RELOCATION DETECT message 2321.

[0214] The core network may at this point switch the user layer to the target RNS.

[0215] As soon as the UE device is synchronized with the UMTS RNS subsystem, the UE indicates that the handover has been completed using PHYSICAL CHANNEL RECONFIGURATION COMPLETE.

RECONFIGURATION OF THE PHYSICAL CHANNEL) 2325.

[0216] The UMTS RNS subsystem confirms the completion of the switchover using the RELOCATION COMPLETE message 2327. If the user layer has not yet been switched, the core network switches the user layer to the target RNS.

[0217] Bi-directional user layer traffic 2329, 2331 flows through the UMTS backbone between the UE and the backbone network.

[0218] The backbone network instructs the serving UNC controller to release all resources allocated to the UE using RELEASE COMMAND 2333.

[0219] The serving UNC controller instructs the base station to release resources by invoking the URR RR RELEASE message 2335.

[0220] A serving UNC confirms the release of the backbone using the RELEASE COMPLETE message 2337.

[0221] The base station confirms the UNC serving the resource release using the URR RR RELEASE COMPLETE message 2339.

[0222] Base station 110 may eventually unregister from the serving UNC using the URR DEREGISTER message 2341.

Switching from Inter-RAT GERAN to UMAN-UMTS [0223] The sequence of switching from GERAN to UMAN-UMTS shown in figure 24 assumes that the UE has an active voice connection to GERAN. The following steps are carried out.

[0224] The UE's multi-band device sends to BSS continuously MEASUREMENT REPORTs 2401, 2403, 2405 containing {ARFCN, BSIC} surrounding GERAN cells and {basic encryption code, UARFCN, cell identity} surrounding UMTS cells.

[0225] Base station 110 should be reported by the UE as having the highest signal level compared to the serving and surrounding GERAN cells.

[0226] The BSS internally maps the {base scrambling code, UARFCN, cell identity} of the base station 110 to the CGI of the UMA cell. GERAN decides to switch to the UMA cell by sending the message HANDOVER REQUIRED to the MSC backbone 2407.

[0227] The backbone network requests the target UNC to allocate resources for switching using the RELOCATION REQUEST message 2409. The UNC should map the IMSI contained in the RELOCATION REQUEST to its own base station of the UE. Destination own base station 110 may or may not be base station 110 currently seen by the UE.

[0228] The UNC target controller confirms the request by using the RELOCATION REQUEST ACKNOWLEDGE 2411 message, indicating that it is able to handle the switchover requested, which also contains the HANDOVER COMMAND content specifying the base channel radio channel parameters to which the EU should be redirected.

[0229] The backbone forwards HANDOVER COMMAND 2413 to GERAN, completing the preparation for switching.

[0230] The GERAN network sends HANDOVER TO UTRAN COMMAND 2415 to the UE to signal switching to base station 110. HANDOVER TO UTRAN COMMAND contains the UARFCN channel number and the basic encryption code of the target base station 110 The UE does not change its audio path from GERAN to UMAN until the switch is completed.

[0231] The UE accesses the base station 110 using the HANDOVER TO UTRAN COMPLETE message 2417. The switch reference contained in this message is forwarded to the UNC controller in the URR message HANDOVER ACCESS 2419 , which allows the UNC operator to correlate the switch to the RELOCATION REQUEST ACKNOWLEDGE message.

[0232] The serving UNC controller sets the carrier path with the base station 110 and the UE.

[0233] The base station transmits the URR HANDOVER COMPLETE message 2423 to signal the completion of the handover procedure. The UE switches from the GERAN user layer to the UMAN user layer.

[0234] Bidirectional voice and / or data traffic 2427, 2429, 2431 flows through the serving UNC controller between the UE and the backbone network.

[0235] The target UNC indicates that the switchover is completed using the RELOCATION COMPLETE message 2433. If this has not been done yet, the backbone network switches the user layer from the source GERAN network to the destination UMAN.

[0236] The backbone network terminates the connection to the source GERAN using CLEAR COMMAND 2435.

[0237] The source GERAN network confirms the release of the GERAN resources allocated to this connection, using CLEAR COMPLETE 2441.

Switching UMTS to UMAN-UMTS [0238] The sequence of switching UMTS to UMAN-UMTS shown in figure 25 assumes that the UE has an active voice connection in the UMTS network. The following steps are carried out.

[0239] The UE sends in a continuous mode to the Node-B base station of the RNS MEASUREMENT REPORTs subsystem 2501, 2503 containing {basic encryption code, UARFCN, cell identity} of surrounding UMTS cells.

[0240] Base station 110 should be reported by the UE as having the highest signal level compared to serving and surrounding UMTS cells.

[0241] The RNS subsystem internally maps the {base scramble code, UARFCN, cell identity} of the base station 110 to the CGI of the UMA cell. The UMTS network decides to switch to a UMA cell by sending a RELOCATION REQUIRED message 2505 to the 3GMSC backbone.

[0242] The core network requests the target UNC to allocate resources for switching using the RELOCATION REQUEST message 2507. The UNC should map the IMSI contained in the RELOCATION REQUEST to its own UE base station. Destination own base station 110 may or may not be base station 110 currently seen by the UE.

[0243] The UNC target controller confirms the request using the RELOCATION REQUEST ACKNOWLEDGE 2509 signaling that it is able to handle the switch that was requested, which also contains the RELOCATION COMMAND content specifying the radio channel parameters to which the EU should be redirected.

[0244] The 3G-MSC core network center forwards the RELOCATION COMMAND 2511 to RNS, completing the switchover preparations.

[0245] The UMTS network sends PHYSICAL CHANNEL RECONFIGURATION 2513 to the UE to indicate the switch towards base station 110. PHYSICAL CHANNEL RECONFIGURATION 2513 contains the destination station information of the physical channel. The UE does not switch its audio path from UMTS to UMAN until switching is complete.

[0246] The UE is detected by the base station 110 by synchronizing Layer 1 and establishing a Layer 2 link. It is transmitted from the base station to the UNC controller the URR message HANDOVER ACCESS 2515, which allows the UNC operator to correlate the switch with the message RELOCATION REQUEST ACKNOWLEDGE (CONFIRMATION OF RELOCATION REQUEST).

[0247] The serving UNC controller sets the carrier path with the base station 110 and the UE.

[0248] Upon receipt of PHYSICAL CHANNEL RECONFIGURATION COMPLETE 2519 from the UE, the base station transmits the URR HANDOVER COMPLETE message 2521 to signal the completion of the switching procedure. The UNC controller transmits the RELOCATION DETECT message 2523 to the MSC.

[0249] The UE switches from the UMTS user layer to the UMAN user layer. Bidirectional voice and data traffic 2525, 2527, 2529 flows between the UE and the backbone network through the UNC service controller.

[0250] The UNC target controller signals that the switchover is completed using the RELOCATION COMPLETE message 2531. If this has not already been done, the core network switches the user layer from the source UMTS network to the destination UMAN.

[0251] The core network terminates the connection to the source UMTS using RELEASE COMMAND 2533.

[0252] The UMTS source network confirms the release of resources allocated to this connection, using RELEASE COMPLETE 2535.

Switching from UMAN-UMTS to UMTS [0253] The sequence of switching from UMAN-UMTS to UMTS shown in Figure 26 assumes that the UE has an active voice or data connection on UMAN in UMTS mode. The following steps are carried out. The UE begins to leave the range of the base station 110. The message exchange shown in Figure 26 is summarized in the sequence of steps below:

[0254] The switch from UMAN to the UMTS macro-network is triggered by measurement reports 2601, 2605, from the UE, BCCH carrier power levels {basic encryption code, UARFCN, cell identity} of the surrounding UMTS macro-network. The UNC controller can send the optional URR UPLINK QUALITY INDICATION 2603 based on the signal strength criterion.

[0255] Base station 110 detects that a switch is required and sends a URR HANDOVER REQUIRED message 2607 to the serving UNC controller indicating the list of UMTS cells identified by the CGI to favor the switch. The base station may obtain a list of these CGIs by decoding System Information messages in the surrounding UMTS cells themselves, or may obtain a list of these CGIs (and their corresponding UARFCN, basic encryption codes) by accessing the appropriate database related to its current geographical location (via zip code or other geographical positioning device).

[0256] The serving UNC begins preparation for switching by sending a RELOCATION REQUIRED message 2609 to the backbone.

[0257] The backbone network selects the destination UMTS cell and requests it to allocate the necessary resources using the RELOCATION REQUEST message 2611.

[0258] The target RNS UMTS subsystem creates a RELOCATION COMMAND message that provides information about the allocated channel and sends it to the backbone network via the RELOCATION REQUEST ACKNOWLEDGE message (Confirms the network controller) UNC to switch the UE to the UMTS network using the RELOCATION COMMAND 2615 message to complete the switch-over phase.

[0260] The serving UNC transmits, to base station 110, a URR HANDOVER COMMAND message 2617 containing details sent by UMTS regarding the allocation of destination resources. Base station 110 transmits, to the UE, a PHYSICAL CHANNEL RECONFIGURATION 2619 message indicating that the UE should switch to the UMTS cell.

[0261] The UE is detected by the target RNS of the UMTS network as a result of the lower layer transmission from the UE. The target RNS confirms the detection of backbone switching using the RELOCATION DETECT message 2621.

[0262] The core network may at this point switch the user layer to the target RNS subsystem.

[0263] As soon as the UE is synchronized with the RNS subsystem of the UMTS network, the UE signals that the handover has been completed using PHYSICAL CHANNEL RECONFIGURATION COMPLETE.

RECONFIGURATION OF THE PHYSICAL CHANNEL) 2625.

[0264] The UMTS RNS subsystem confirms the completion of the switch over the core network using the RELOCATION COMPLETE message 2627. If the user layer has not yet been switched, the core network switches the user layer to the target RNS.

[0265] Bidirectional traffic at user layer 2629, 2631 begins to flow between the UE and the backbone network through the UMTS backbone network.

[0266] The core network signals the serving UNC to release all resources allocated to the UE using the RELEASE COMMAND command 2633.

[0267] The serving UNC controller instructs the base station 110 to release resources using the URR RR RELEASE message 2635.

[0268] A serving UNC confirms the release of the backbone using the RELEASE COMPLETE message 2637.

[0269] The base station confirms the serving UNC controller the release of resources using the URR RR RELEASE COMPLETE message 2639.

[0270] Base station 110 may eventually unregister from the serving UNC using the URR DEREGISTER message (URR REGISTRATION) 2641.

Switching Inter-RAT GERAN to UMAN-UMTS [0271] The sequence of switching from GERAN to UMAN-UMTS shown in figure 27 assumes that the UE has an active voice connection in the GERAN network. The message exchange shown in Figure 27 is summarized in the following sequence of steps: [0272] The multi-band UE sends continuously to BSS MEASUREMENT REPORTs 2701, 2703, 2705 containing {ARFCN, BSIC} surrounding GERAN cells and values { basic encryption code, UARFCN, cell identity} of surrounding UMTS cells.

[0273] Base station 110 should be reported by the UE as having the highest signal level compared to the serving and surrounding GERAN cells.

[0274] The BSS internally maps the {base scrambling code, UARFCN, cell identity} of the base station 110 to the CGI of the UMA cell. GERAN decides to switch to a UMA cell by sending HANDOVER REQUIRED 2707 to the MSC backbone.

[0275] The core network requests the target UNC to allocate resources for switching using the RELOCATION REQUEST message 2709. The UNC should map the IMSI contained in the RELOCATION REQUEST to its own user base station 110. Destination own base station 110 may or may not be the base station currently seen by the UE.

[0276] The target UNC confirms the request using the RELOCATION REQUEST ACKNOWLEDGE 2711, indicating that it can handle the switch that was requested and also contains the HANDOVER COMMAND content indicating the radio channel parameters of its own base station to which it should be redirected.

[0277] The backbone network forwards HANDOVER COMMAND 2713 to the GERAN network, completing the switchover preparation.

[0278] The GERAN network sends the HANDOVER TO UTRAN COMMAND message 2715 to the UE to signal switching to base station 110. The HANDOVER TO UTRAN COMMAND message contains the UARFCN number and the basic encryption code destination base station. The UE does not switch its audio path from GERAN to UMAN until the switch is completed. [0279] The UE accesses base station 110 using the HANDOVER TO UTRAN COMPLETE message 2717. The switch reference contained in this message is forwarded to UNA in the URR message HANDOVER ACCESS 2719, which allows the UNC operator to correlate the switch with the RELOCATION REQUEST ACKNOWLEDGE message.

[0280] The serving UNC controller sets the carrier path with the base station 110 and the UE.

[0281] Base station 110 transmits the URR HANDOVER COMPLETE message 2723 to signal the completion of the handover procedure. The UE switches from the GERAN user layer to the UMAN user layer.

[0282] Two-way voice and / or data traffic 2727, 2729, 2731 flows between the UE and the backbone network through the serving UNC.

[0283] The UNC target controller indicates that the switch has been completed using the RELOCATION COMPLETE message 2733. If it has not already been done, the backbone network switches the user layer from the source GERAN to the destination UMAN.

[0284] The backbone network breaks connection to the source GERAN network using CLEAR COMMAND 2735.

[0285] The source GERAN network confirms the release of the GERAN resources allocated for this connection using the CLEAR COMPLETE message 2741.

[0286] Base station 110 is designed for use as a "public access" system for use in stores, bars, restaurants and other public places, and as a limited access system for use in homes and offices.

[0287] In public access applications, base station 110 will identify with the same identifier as the public land mobile network (PLMN) of the operator owning the network - base station 110 appears to be another base station in the network, that the cell phone will connect to when the signal strength received from base station 110 exceeds the signal strength of other base stations.

[0288] In home or office applications, it is often very desirable to limit access to base station 110 to only those subscribers who pay for this base station 110 and the associated DSL line. The present invention includes a base access control scheme 110 by modifying the telephone SIM card itself, without requiring a costly modification of the standard GSM / UMTS telephone set. Using this scheme, the operator's devices owned by this base station 110 all share a common PLMN identifier, but different from the operator's wide area network identifier. When a different PLMN is set as its own PLMN for a specific mobile phone in its SIM card, then this phone will be privileged to connect to base station 110 whenever a sufficient signal level is detected, regardless of the signal strength of other operator's PLMN base stations.

[0289] Standard UE GSM / UMTS devices, when they do not make voice or data connections - which is referred to as rest mode - will automatically PLMN select in the following order of priority:

i) MNO HPLMN (Home PLMN) network defined by the SIM card ii) other PLMN network defined by the SIM card specified by the MNO supplying the SIM card iii) other detected PLMN networks with sufficient signal strength [0290] In rest mode, MS periodically attempts to obtain services in your HPLMN network. To do this, the T minutes value can be stored on the SIM card, in the range of 6 minutes to 8 hours (in 6-minute steps). Therefore, by making HPLMN the identifier of the MNO ZoneGate network, logging in from the macro-network to the base station 110 and will be done automatically within a minimum of 6 minutes from the moment the user enters the coverage range of his own base station 110. Logging out should be done automatically as soon as the user will leave the coverage area of its own base station 110. To ensure proper logout behavior, the MNO PLMN network identifier should have the highest PLMN priority on the SIM card after HPLMN.

[0291] Note that PLMN selection and re-selection are only performed in rest mode. In connection mode, PLMN re-selection is not carried out unless it has been initiated by the network between PLMN switching.

[0292] In general, network users unable to use base station 110 would already be in their HPLMN network or other PLMN network when roaming, and would not attempt to access PLMN of base station 110 unless there was no macro-network coverage . For authorized users, access to a specific base station 110 is restricted to a small number of users who have been provided services on this particular device. Because base station 110 operates on the UE as a standalone GSM / UMTS network, it is able to obtain the International Mobile Station Identifier (IMSI) from standard GSM / UMTS messages exchanged with the UE, and thus make a decision whether the UE is allowed to make calls via base station 110 or not.

[0293] In normal macro-cell operation, the UE registers to the cell via location registration (LR) if the selected or re-selected cell has a different registration area (LA / RA, registration area) or PLMN. If this is not the case, then the UE will use the procedure for attaching the IMSI identifier or attaching the GPRS to register in the cell. Base station 110 will configure itself to have a different Location Area (and hence a different Routing Area) relative to the macro-network, so that a location registration procedure will always be necessary. IMSI attachment can also be performed during the location registration procedure.

[0294] During the location registration procedure, the UE sends to the base station 110 a standard LOCATION UPDATING REQUEST message which contains the IMSI. Base station 110 may reject this request if the IMSI does not match those users provided the service without having to contact the backbone, thereby reducing possible network traffic. If the IMSI identifier is not sent in LOCATION UPDATING REQUEST and the TMSI / P-TMSI is not known by base station 110, then IMSI is obtained from the EU via the IDENTITY REQUEST procedure.

[0295] It is important to note that base station 110 is directly connected to the operator's backbone network it owns, and no user switched from the operator's macro network to base station 110 will not be recorded by the HLR as which has left the operator's network. Base station 110 appears to be a separate network only for mobile devices whose hardware identifiers (IMSI) are disclosed by standard GSM / UMTS signaling procedures when devices cross the network boundary. This allows you to limit access to base station 110 only to defined users.

[0296] The PLMN selection and the location registration procedures are mapped by the base station 110 to the detection and registration procedures for both UMA and SIP:

[0297] For base station 110 connected to the core network via UMA, the UMA detection procedure is performed when the UE first attempts to access the service to establish the identity of the default serving UNC. Then, after completing the UMA detection procedure, a UMA registration procedure is performed between the UE and UNC to inform UMC that this specific UE is connected and available to services that terminate by the mobile device.

[0298] UMA detection and registration procedures are performed when a UE successfully selects a specific base station 110 that is required to validate it through GERAN PLMN selection and cell selection procedures. These procedures are described and shown in figure 11.

[0299] For base station 110 with SIP enabled, the SIP registration procedure shown in Figure 28 is performed during the UE device location registration procedure to register SIP location information in the Location Service via the SIP Registrar Server ). SIP authentication can also be enabled during this procedure. The network location service stores the location of SIP user agents so that they are available to services that can be terminated by the mobile device.

[0300] SIP registration in the SIP proxy server (SIP proxy server) should be triggered by successful location update (GERAN) or by updating the registration area (UTRAN) for registered UE ZAP devices.

[0301] Both SIP and UMA registration are only performed if the GSM / UMTS location registration procedure is successful. Therefore, access to both UMA and SIP is limited to authenticated users only. A subset of UEs exchanged during location recording is also mapped to SIP and UMA registration procedures.

[0302] As mentioned above, base station 110 includes an Ethernet port 208 that allows the base station to connect to home or office LANs. In this configuration, Ethernet LAN provides connection to the owner's operator network.

[0303] When deployed in areas where a single base station 110 is not able to provide sufficient coverage, such as large houses or multi-storey offices, multiple base stations 110 may be used to provide adequate coverage. Users moving around the office will require that their ongoing conversations be served between base stations 110 providing uninterrupted coverage. Base station 110 can provide this functionality as long as all base stations within the office space will be connected using a single, common Ethernet LAN.

[0304] Call forwarding procedures use proprietary messages transmitted between base stations 110 to implement and coordinate forwarding. The elements of mobility management at two base stations, namely the source base station ZG1 and the destination base station ZG2, communicate with each other via a LAN connection using restricted messages. These messages contain information on GSM / UMTS settings at each base station, as well as information related to moving the current SIP session.

[0305] Each access point for base station 110 is uniquely identified by the SIM. This can be done as a physical SIM card or as a piece of downloaded software, referred to as "softSIM". Each base station 110 must have a Primary User identified by the SIM card provided by the operator of his cell phone. The base station management system 160 will be provided with SIM identifiers for base stations 110 and basic users and will specify user groups for which there is an association between at least one base station SIM and a basic user SIM. The basic user will be able to add other user SIM cards to the base station users group using various mechanisms of any base station within the base stations of the user group, such as authenticated phone call / email from / to the management system or interaction with the network server.

[0306] The base station user group will allow the association of multiple base station SIM cards with the same primary user SIM card. All access points within the base station user group will allow access to the same list of user SIM cards (as defined by the primary user) and will be able to transfer each other using the proprietary mechanisms described below. Communication between base stations within the user base stations will be enabled by systematically reporting public or private IP addresses back to the management system; the management system will match the IP address with the information of the authorized user and will periodically broadcast it to all base stations within the base stations of the user group.

[0307] The new access point that will be installed in the office environment will obtain an IP address from the Ethernet LAN, connect to the management system 160 and complete authentication using information from the base station SIM and the basic user SIM. It will then be added to the base station user group for this primary user that is stored on the 160 management system. The newly installed base station will then report its IP address to management system 160; management system 160 will update the IP address tables stored for a specific group of base station users and broadcast the updated table and list of users to all base stations in the user group, including the newly installed access point. This newly installed access point will complete the remaining steps described above in the self-configuration process and then attempt to connect to each of the IP addresses on the list broadcast by the management system; if the connection is successful, both access points exchange further required information so that they can add to each other's BA lists the information transmitted on the broadcast channel of each access point. (GSM / UMTS standards require that the parameters of the surrounding base stations be included in the System Information message broadcast by the broadcast channel from each base station, so that UE devices can monitor neighboring base stations in preparation for potential switching.) The exchange of information is described in the table 1 below:

Table 1: GSM / UMTS information exchanged between access points in

<td>within the user group</td><td colspan="2">base station angles</td>

<td>Parameter</td><td>Link</td><td>Description</td>

<td>ARFCN, BSIC</td><td>GSM / GPRS</td><td>The contents of the BA list are the ARFCN list of base stations 110, and the base station identification codes. A single base station 110 should have one ARFCN and one BSIC.</td>

<td>CI</td><td>GSM / GPRS / UMTS</td><td>Base station cell ID 110.</td>

<td>LAI</td><td>GSM / GPRS / UMTS</td><td>Location area identifier that is broadcast by base station 110.</td>

<td>RAI</td><td>GPRS / UMTS</td><td>The routing area identifier that is broadcast by base station 110.</td>

<td>Basic encryption</td><td>UMTS</td><td>The basic encryption code that is used</td>

<td>Code</td><td></td><td>At base station 110 basic CPICH.</td>

<td>UARFCN</td><td>UMTS</td><td>Broadcast frequency for UMTS base station 110.</td>

[0308] The switching mechanism between access points described here is for use with SIP connections only. With this approach, uninterrupted wide area network switching cannot be supported. UE / MS IP addresses are requested from the DHCP server of the LAN to which these access points are connected; the access point to which MS / UE connects first will act as an intermediary for the UE / MS IP address and will request the IP address on behalf of the MS / UE that will be connected to that UE / MS. As MS / UE terminals / devices are switched between access points, the IP address of this MS / UE is kept until the intermediary function of the IP address transfers to the new access point together with the switched MS / UE. For more complex networks where there is no single DHCP server, mobile IP techniques can be used to preserve the MS / UE IP address for the duration of the connection.

[0309] Switching signaling is shown in Figure 29, where base station 110 functionality is further divided into RNS and MSC 3GPP standard elements, where RNS means elements of UMTS Access Stratum and MSC means elements of Non-Access Stratum. All signaling with the prefixes Uu and lu is signaling with the 3GPP standard, and all signaling with the prefix ZG is reserved: [0310] The following sequence of steps is performed:

[0311] The source base station ZG1 determines that switching is required, due to measurement reports 2901, 2903 received from the UE. Measurement reports indicate that the receiver power level in the UE for the target ZG2 base station is high, and the receiver power level in the UE for the current ZG1 base station is low. [0312] The ZG1 base station initiates the handover by sending an internal RELOCATION REQUIRED message 2905. ZG1 sends a proprietary ZG-Handover-Request message 2907 via LAN to the destination ZG2 base station to inform her that a switch has been requested. The ZG2 IP address is already known by ZG1 during self-management of base stations in the LAN.

[0313] The target ZG2 base station determines whether a handover can take place, and returns a ZG-Handover-Response message 2913 to signal that the request has been accepted. ZG2 generates internal RELOCATION REQUEST 2909 and RELOCATION REQUEST ACKNOWLEDGE signaling 2911.

[0314] ZG-Handover-Information-Request 2915 is transmitted from the first ZG1 base station to the target ZG2 base station to transfer the current switch parameters and SIP client settings to the ZG2 base station as preparation for switching . It is transmitted, to the ZG1 base station, ZGHandover-Information-Response 2917 in response to the transmission of target GSM / UMTS radio access settings.

[0315] The switching is initiated by the ZG1 base station by sending a PHYSICAL CHANNEL RECONFIGURATION message 2921 via a UMTS wireless link to the UE. The message also includes GSM / UMTS radio access settings from the target ZG2. The UE attempts to register with the target ZG2 base station via standard Layer-1 and Layer-2 signaling. The UE is detected by the ZG2 base station that generates an internal RELOCATION DETECT 2925 message.

[0316] ZG-Handover-Detect-Request message 2927 is transmitted from the ZG2 base station to the source ZG1 base station to indicate that the UE switching procedure was successful.

[0317] The ZG1 base station stops receiving SIP call signaling and traffic packets, and the ZG2 base station begins receiving (ie processing) SIP call signaling and traffic packets. No re-routing of SIP packets for UE / MS is required because the destination IP address is the UE / MS address that has remained unchanged due to switching. The LAN connection should provide both base stations with the ability to receive IP packets for UE / MS.

[0318] The completion of the switching process is indicated by the base station ZG2 by generating an internal RELOCATION COMPLETE message 2931 and sending a ZG-HandoverComplete-Request message 2933 to the ZG1 base station. ZG1 releases the connection internally by transmitting an internal RELEASE COMMAND 2935 signaling message and RELEASE COMPLETE 2937 signaling.

[0319] Thus, a base station is disclosed that allows access to the cellular network of the network operator using a standard cellular telephone.

137 members in 9 offices

This recordMember, by publication datePriority claim

Priority claims8

Priority claims
Document	Office	Kind	Date
0515888	United Kingdom	A	2005-08-01
0515888	United Kingdom	A	2005-08-01
06765134	European Patent Office (EPO)	A	2006-07-28
06765134	European Patent Office (EPO)	A	2006-07-28
10184563	European Patent Office (EPO)	A	2006-07-28
EP20060765134	–	–	–
EP20100184563	–	–	–
GB20050015888	–	–	–

Members137

Family members, oldest first
Document	Office	Kind
GB0515888D0	United Kingdom	D0	2005-09-07
GB0610650D0	United Kingdom	D0	2006-07-05
GB0625660D0	United Kingdom	D0	2007-01-31
GB0625661D0	United Kingdom	D0	2007-01-31
GB0625662D0	United Kingdom	D0	2007-01-31
GB0625663D0	United Kingdom	D0	2007-01-31
GB2428937A	United Kingdom	A	2007-02-07
GB2428942A	United Kingdom	A	2007-02-07
WO2007015066A2	World Intellectual Property Organization (WIPO)	A2	2007-02-08
WO2007015067A2	World Intellectual Property Organization (WIPO)	A2	2007-02-08
WO2007015068A1	World Intellectual Property Organization (WIPO)	A1	2007-02-08
WO2007015071A2	World Intellectual Property Organization (WIPO)	A2	2007-02-08
WO2007015075A1	World Intellectual Property Organization (WIPO)	A1	2007-02-08
GB2430120A	United Kingdom	A	2007-03-14
GB2430121A	United Kingdom	A	2007-03-14
GB2430839A	United Kingdom	A	2007-04-04
GB2432082A	United Kingdom	A	2007-05-09
WO2007015067A3	World Intellectual Property Organization (WIPO)	A3	2007-05-10
WO2007015066A3	World Intellectual Property Organization (WIPO)	A3	2007-05-18
WO2007015071A3	World Intellectual Property Organization (WIPO)	A3	2007-05-24
GB2430120B	United Kingdom	B	2007-10-17
GB2430839B	United Kingdom	B	2007-10-17
GB2432082B	United Kingdom	B	2007-10-17
EP1911306A2	European Patent Office (EPO)	A2	2008-04-16
EP1911307A1	European Patent Office (EPO)	A1	2008-04-16
EP1911310A2	European Patent Office (EPO)	A2	2008-04-16
EP1911311A2	European Patent Office (EPO)	A2	2008-04-16
EP1911316A1	European Patent Office (EPO)	A1	2008-04-16
US2008102794A1	United States of America	A1	2008-05-01
GB0807815D0	United Kingdom	D0	2008-06-04
GB0807816D0	United Kingdom	D0	2008-06-04
GB0807818D0	United Kingdom	D0	2008-06-04
GB2447159A	United Kingdom	A	2008-09-03
GB2447365A	United Kingdom	A	2008-09-10
CN101278575A	China	A	2008-10-01
CN101278576A	China	A	2008-10-01
CN101278577A	China	A	2008-10-01
CN101278586A	China	A	2008-10-01
CN101278590A	China	A	2008-10-01
US2008254833A1	United States of America	A1	2008-10-16
GB2449531A	United Kingdom	A	2008-11-26
GB2447365B	United Kingdom	B	2008-12-03
US2008304439A1	United States of America	A1	2008-12-11
US2009017864A1	United States of America	A1	2009-01-15
JP2009504047A	Japan	A	2009-01-29
JP2009504048A	Japan	A	2009-01-29
JP2009504049A	Japan	A	2009-01-29
JP2009504050A	Japan	A	2009-01-29
JP2009504051A	Japan	A	2009-01-29
GB2447159B	United Kingdom	B	2009-03-25
GB2449531B	United Kingdom	B	2009-05-27
GB0909125D0	United Kingdom	D0	2009-07-01
US2009190550A1	United States of America	A1	2009-07-30
GB2428942B	United Kingdom	B	2009-08-12
GB2458041A	United Kingdom	A	2009-09-09
GB2458041B	United Kingdom	B	2010-02-10
GB201001514D0	United Kingdom	D0	2010-03-17
GB201001515D0	United Kingdom	D0	2010-03-17
GB2464860A	United Kingdom	A	2010-05-05
GB2464861A	United Kingdom	A	2010-05-05
US2010190495A1	United States of America	A1	2010-07-29
GB2464861B	United Kingdom	B	2010-08-11
GB2428937B	United Kingdom	B	2010-08-18
GB2464860B	United Kingdom	B	2010-08-18
US2010227645A1	United States of America	A1	2010-09-09
US2010317405A1	United States of America	A1	2010-12-16
US2010322426A1	United States of America	A1	2010-12-23
JP2011019247A	Japan	A	2011-01-27
EP2288198A2	European Patent Office (EPO)	A2	2011-02-23
EP2337393A2	European Patent Office (EPO)	A2	2011-06-22
EP2337394A2	European Patent Office (EPO)	A2	2011-06-22
DE202005021930U1	Germany	U1	2011-09-29
DE202006020960U1	Germany	U1	2011-09-29
DE202006020961U1	Germany	U1	2011-09-29
EP2375798A2	European Patent Office (EPO)	A2	2011-10-12
DE202006020957U1	Germany	U1	2011-10-27
DE202006020958U1	Germany	U1	2011-10-27
EP2288198A3	European Patent Office (EPO)	A3	2011-12-07
EP2337393A3	European Patent Office (EPO)	A3	2012-03-07
US8204543B2	United States of America	B2	2012-06-19
JP4965568B2	Japan	B2	2012-07-04
JP2012151887A	Japan	A	2012-08-09
JP5021644B2	Japan	B2	2012-09-12
US2012238324A1	United States of America	A1	2012-09-20
EP2506655A2	European Patent Office (EPO)	A2	2012-10-03
EP2506656A2	European Patent Office (EPO)	A2	2012-10-03
EP2506657A2	European Patent Office (EPO)	A2	2012-10-03
EP2506658A2	European Patent Office (EPO)	A2	2012-10-03
JP5043998B2	Japan	B2	2012-10-10
JP2012213163A	Japan	A	2012-11-01
CN101278586B	China	B	2013-01-23
JP5140590B2	Japan	B2	2013-02-06
EP1911310B1	European Patent Office (EPO)	B1	2013-02-27
EP2288198B1	European Patent Office (EPO)	B1	2013-03-06
US2013089055A1	United States of America	A1	2013-04-11
EP2337393B1	European Patent Office (EPO)	B1	2013-04-17
JP2013093894A	Japan	A	2013-05-16
ES2405682T3	Spain	T3	2013-06-03
CN103152842A	China	A	2013-06-12
JP5209475B2	Japan	B2	2013-06-12

Showing 100 of 137

Self-configuring cellular basestation

Abstract

Term

Priority claims8

Members137

Numbers

Titles2

Classification