RLAN wireless telecommunication system with RAN IP gateway and methods

CROSS REFERENCE TO RELATED APPLICATION(S)

0001This application claims priority from U.S. Provisional Application No. 60/367,949, filed Mar. 26, 2002; U.S. Provisional Application No. 60/367,975, filed Mar. 26, 2002; U.S. Provisional Application No. 60/367,946, filed Mar. 26, 2002; U.S. Provisional Application No. 60/367,945, filed Mar. 26, 2002; U.S. Provisional Application No. 60/367,950, filed Mar. 26, 2002; and U.S. Provisional Application No. 60/367,948, filed Mar. 26, 2002, which are incorporated herein by reference as if fully set forth.

FIELD OF INVENTION

0002The present invention relates to wireless telecommunication systems and in particular to Time Division Duplex-Radio Local Area Network (TDD-RLAN) Code Division Multiple Access (CDMA) systems and connection and communication of such systems with the Internet.

BACKGROUND

0003Wireless telecommunication systems are well known in the art. Wireless systems require an available bandwidth in which to operate. Typically, the permission to use a portion of the available spectrum for wireless communication for a particular geographic region is obtained from an appropriate governmental unit of the physical territory in which the wireless communications are to be conducted. In order to make efficient use of limited spectrum available for operation of a wireless telecommunication system, Code Division Multiple Access (CDMA) systems have been developed which include Time Division Duplex (TDD) modes which provide a very flexible framework for providing concurrent wireless communication services. Supported wireless communication services can be any of a variety of types including voice, fax, and a host of other data communication services.

0004In order to provide global connectivity for CDMA systems, standards have been developed and are being implemented. One current standard in widespread use is known as Global System for Mobile Telecommunications (GSM). This was followed by the so-called Second Generation mobile radio system standards (2G) and its revision (2.5G). Each one of these standards sought to improve upon the prior standard with additional features and enhancements. In Jan. 1998, the European Telecommunications Standard Institute-Special Mobile Group (ETSI SMG) agreed on a radio access scheme for Third Generation Radio Systems called Universal Mobile Telecommunications Systems (UMTS). To further implement the UMTS standard, the Third Generation Partnership Project (3GPP) was formed in Dec. 1998. 3GPP continues to work on a common third generational mobile radio standard.

0005A typical UMTS system architecture in accordance with current 3GPP specifications is depicted in <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. The UMTS network architecture includes a Core Network (CN) interconnected with a UMTS Terrestrial Radio Access Network (UTRAN) via an interface known as IU which is defined in detail in the current publicly available 3GPP specification documents.

0006The UTRAN is configured to provide wireless telecommunication services to users through User Equipments (UEs) via a radio interface known as UU. The UTRAN has base stations, known as Node Bs in 3GPP, which collectively provide for the geographic coverage for wireless communications with UEs. In the UTRAN, groups of one or more Node Bs are connected to a Radio Network Controller (RNC) via an interface known as Iub in 3GPP. The UTRAN may have several groups of Node Bs connected to different RNCs, two are shown in the example depicted in <figref idref="DRAWINGS">FIG. 1</figref>. Where more than one RNC is provided in a UTRAN, inter-RNC communication is performed via an lur interface.

0007A UE will generally have a Home UMTS Network (HN) with which it is registered and through which billing and other functions are processed. By standardizing the Uu interface, UEs are able to communicate via different UMTS networks that, for example, serve different geographic areas. In such case the other network is generally referred to as a Foreign Network (FN).

0008Under current 3GPP specifications, the Core Network of a UE's HN serves to coordinate and process the functions of Authentication, Authorization and Accounting (AAA functions). When a UE travels beyond its Home UMTS Network, the HN's Core Network facilitates the UE's use of a Foreign Network by being able to coordinate the AAA functions so that the FN will permit the UE to conduct communications. To assist in implementing this activity, the Core Network includes a Home Location Register (HLR) which tracks the UEs for which it is the HN and a Visitor Location Register (VLR). A Home Service Server (HSS) is provided in conjunction with the HLR to process the AAA functions.

0009Under current 3GPP specifications, the Core Network, but not the UTRAN, is configured with connectivity to external systems such as Public Land Mobile Networks (PLMN), Public Switch Telephone Networks (PSTN), Integrated Services Digital Network (ISDN) and other Real Time (RT) services via an RT service interface. A Core Network will also support Non-Real Time services with the Internet. External connectivity of the Core Network to other systems, enables users using UEs to communicate via their Home UMTS Network, beyond the area served by the HN's UTRAN. Visiting UEs can likewise communicate via a visited UMTS Network, beyond the area served by the visited UMTS's UTRAN.

0010Under current 3GPP specifications, the Core Network provides RT service external connectivity via a Gateway Mobile Switching Center (GMSC). The Core Network provides NRT service, known as General Packet Radio Service (GPRS), external connectivity via a Gateway GPRS Support Node (GGSN). In this context, a particular NRT service may actually appear to a user to be a real time communication due to the communication speed and associated buffering of the TDD data packets forming the communication. One example of this is voice communication via the Internet which can appear to the user as a normal telephone call conducted by a switching network, but is actually being conducted using an Internet Protocol (IP) connection which provides Packet data Service.

0011A standard interface known as GI is generally used between a CN's GGSN and the Internet. The GI interface can be used with Mobile Internet Protocols, such as Mobile IP v4 or Mobile IP v6 as specified by the Internet Engineering Task Force (IETF).

0012Under current 3GPP specifications, to provide support for both RT and NRT services from external sources for radio linked UEs in a 3GPP system, the UTRAN must properly interface with the CN which is the function of the Iu interface. To do this, the Core Network includes a Mobile Switching Centre (MSC) that is coupled to the GMSC and a Serving GPRS Support Node (SGSN) that is coupled to the GGSN. Both are coupled with the HRL and the MSC is usually combined with the Visitor Location Register (VLR).

0013The Iu interface is divided between an interface for Circuit Switched communications (Iu-CS) and an interface for packet data via Packet Switched communications (Iu-PS). The MSC is connected to the RNCs of the UTRAN via the Iu-CS interface. The Serving GPRS Support Node (SGSN) is coupled to the UTRAN's RNCs via the Iu-PS interface for Packet Data Services.

0014The HLR/HSS is typically interfaced with the CS side of the Core Network, MSC and GMSC via an interface known as Gr which supports AAA functions through a Mobile Application Part (MAP) Protocol. The SGSN and the GGSN of the CN are connected using interfaces known as Gn and Gp.

0015Common to 3GPP systems and other systems which utilize TDD-CDMA telecommunications, such as some GSM systems, is the aforementioned division of connectivity between the radio network and the Core Network. In general, the radio network, i.e. the UTRAN in 3GPP, communicates via a wireless interface with UEs and the Core Network communicates with external systems via RT and NRT service connections. Applicants have recognized this standardized type of architecture is most likely the result of the processing of the AAA functions in the Core Network. However, applicants have further recognized that even if the AAA functions are to be maintained in the Core Network, significant advantages and benefits can be obtained by providing direct connectivity from a TDD-CDMA radio network to the Internet.

0016In particular, Applicants have recognized that the existing separation of functions of the Iu interface defined in 3GPP for Circuit Switched (CS) communications used with Real Time services (Iu-CS interface) and defined in 3GPP for Packet Switch (PS) service used with Non-Real Time services (Iu-PS interface), enables one to easily provide an IP Gateway in the UTRAN for enabling the UTRAN to direct connectivity to the Internet bypassing use of a Core Network for this function. Moreover, as a result, Applicants have recognized that by permitting direct access to the Internet from the UTRAN, a Radio Local Area Network is defined that can provide significant benefits and advantages for use with or without a Core Network.

0017Further detail of a typical 3GPP system is illustrated in <figref idref="DRAWINGS">FIG. 3</figref>. The UTRAN segment of a conventional UMTS architecture is split it into two traffic planes known as the C- and U-planes. The C-plane carries control (signaling) traffic, and the U-plane transports user data. The over-the-air segment of the UTRAN involves two interfaces: the Uu interface between UE and Node B, and the Iub interface between the Node B and RNC. As noted above, the back-end interface between the RNC and core network is referred to as the Iu interface, split into the Iu-CS for the circuit-switched connection into the MSC, and the Iu-PS for the packet-switched connection into the SGSN.

0018The most significant signaling protocol on the over-the-air segment of the UTRAN is Radio Resource Control (RRC). RRC manages the allocation of connections, radio bearers and physical resources over the air interface. In 3GPP, RRC signaling is carried over the Radio Link Control (RLC) and Medium Access Control (MAC) UMTS protocols between the UE and RNC. Overall, the RNC is responsible for the allocation/de-allocation of radio resources, and for the management of key procedures such as connection management, paging and handover. Over the Iub interface, RRC/RLC/MAC messaging is typically carried on a Transport Layer via Asynchronous Transfer Mode (ATM), using the ATM Adaptation Layer Type 5 (AAL5) protocol over the ATM physical layer with intermediary protocols, such as Service Specific Co-ordination Function (SSCF) and the Service Specific Connection Oriented Protocol SSCOP, being used above AAL5.

0019U-plane data (e.g. speech, packet data, circuit-switched data) uses the RLC/MAC layers for reliable transfer over the air interface (between UE and RNC). Over the Iub segment, this data flow (user data/RLC/MAC) occurs over UMTS-specified frame protocols using the ATM Adaptation Layer Type 2 (AAL2) protocol over the ATM physical layer running (AAL2/ATM).

0020The Iu interface carries the Radio Access Network Application Part (RANAP) protocol. RANAP triggers various radio resource management and mobility procedures to occur over the UTRAN, and is also responsible for managing the establishment/release of terrestrial bearer connections between the RNC and SGSN/MSC. RANAP is carried over AAL5/ATM, with intermediary Signaling System 7 (SS7) protocols, such as Signaling Connection Control Part, Message Transfer Part (SCCP/MTP) on top of SSCF and the Service Specific Connection Oriented Protocol (SSCOP), being used above AAL5. Internet Protocol is typically used over AAL5/ATM for the Iu-PS interface so that the intermediate Stream Control Transmission Protocol (SCTP) is then used over IP. Where multiple RNCs exist in a UTRAN which have an Iur interface, IP is also commonly used over ATM and intermediate protocols include SSCP, SCTP and the Message Transfer Part level 3 SCCP adaptation layer of SS7 (M3UA) that have been developed by IETF.

0021For the U-Plane, between the UTRAN and the CN, circuit-switched voice/data traffic typically flows over AAL5/ATM, via the Iu-CS interface, between the RNC and MSC. Packet-switched data is carried over the Iu-PS interface between the RNC and SGSN, using the GPRS Tunneling Protocol (GTP) running over the User Data Protocol for the Internet Protocol (UDP/IP) over AAL5/ATM.

0022Applicants have recognized that this architecture can be improved upon in connection with providing direct IP connectivity for the UTRAN.

SUMMARY

0023The present invention provides for a Radio Local Area Network (RLAN) which includes a Radio Access Network Internet Protocol (RAN IP) gateway that enables connectivity to the public Internet. The system may serve as a stand-alone system or be incorporated into a UMTS used with a conventional Core Network, particularly for tracking and implementing AAA functions in the Core Network.

0024The RLAN provides concurrent wireless telecommunication services for a plurality of user equipments (UEs) between UEs and/or the Internet. The RLALN includes at least one base station that has a transceiver configured to conduct code division multiple access (CDMA) wireless communications preferably time division duplex (TDD) CDMA wireless communications, with UEs in a selected geographic region. The RLAN also has at least one controller that is coupled with a group of base stations, which includes the base station. The controller controls the communications of the group of base stations. A novel Radio Access Network Internet Protocol (RAN IP) Gateway (RIP GW) is coupled with the controller. The RAN IP Gateway has a Gateway General Packet Radio Service (GPRS) Support Node (GGSN) with access router functions for connection with the Internet.

0025The RLAN can include a plurality of base stations, each having a transceiver configured with a Uu interface preferably configured to conduct time division duplex (TDD) wideband code division multiple access (W-CDMA) wireless communications with UEs in a selected geographic region. The RLAN can also include a plurality of controllers that are each coupled with a group of base stations.

0026Preferably, the RAN IP Gateway has a Serving GPRS Support Node (SGSN) that is coupled with one or more controllers in the RLAN. Preferably, the controllers are Radio Network Controller (RNCs) in accordance with 3GPP specification. Preferably, the RNCs are coupled with the base stations using a stacked, layered protocol connection having a lower transport layer configured to use Internet Protocol (IP). Where the RLAN has multiple RNCs, the RNCs are preferably coupled to each other using a stacked, layered protocol connection having a lower transport layer configured to use Internet Protocol (IP)

0027Methods of mobility management using a radio local area network (RLAN) are disclosed for providing concurrent wireless telecommunication services for a plurality of UEs where an associated core network (CN) supports Authentication, Authorization and Accounting (AAA) functions of UEs. A RLAN conducts TDD-CDMA wireless communications with UEs in a RLAN service region. The RLAN has a RAN IP Gateway that has a GPRS connection with the Internet and is configured to communicate AAA function information to the associated CN.

0028In one method, a wireless connection is established between a first UE within the RLAN service region and a second UE outside of the RLAN service region for conducting a communication of user data. AAA functions for said communication between said first and second UEs are conducted using the Core Network. The GPRS connection with the Internet is used for transporting user data of the communication between the first and second UEs. The method may include continuing the wireless communication between the first and second UEs as the second UE moves from outside to within the RLAN service region, where use of the GPRS connection with the Internet for transporting user data is discontinued. The method can further include continuing the wireless communication between the first and second UEs as either the first or second UE moves from within to outside the RLAN service region by resuming use of the GPRS connection with the Internet for transporting user data.

0029In another method, a wireless connection is established between first and second UEs within the RLAN service region for conducting a communication of user data. AAA functions for the communication between the first and second UEs are conducted using the Core Network. The wireless communication between the first and second UEs is continued as either the first or second UE moves from within to outside the RLAN service region by using the GPRS connection with the Internet for transporting user data of the continued communication.

0030A further method of mobility management is provided where the associated CN supports AAA functions of home UEs and the GPRS connection of the RAN IP Gateway is configured to tunnel AAA function information through the Internet to the Core Network. A wireless connection is established between a home UE and a second UE for conducting a communication of user data. AAA functions for the communication are conducted using the Core Network by using the GPRS connection with the Internet to tunnel AAA function information through the Internet to the Core Network.

0031This method may be used where the wireless connection is established when either the home UE or the second UE is within or outside the RLAN service region. Where one is within and the other is outside of the RLAN service region, the GPRS connection with the Internet is used for transporting user data of the communication between the home and second UEs.

0032This method may further include continuing the wireless communication between the home and second UEs as one moves such that both are outside or both are within the RLAN service region, where the use of said General Packet Radio Service (GPRS) connection with the Internet for transporting user data is discontinued. The method may further include continuing the wireless communication between the home and second UEs as either the home or second UE moves so that one is within and the other is outside the RLAN service region by using the GPRS connection with the Internet for transporting user data for the continued communication.

0033In one aspect of the invention, the RLAN has as control means one or more U-Plane and C-Plane Servers coupled with base stations. The U-Plane Server(s) are configured to control user data flow of base station communications. The C-Plane Server(s) are configured to control signaling for base stations communication. Preferably, the RAN IP Gateway has a SGSN that is coupled with the U-plane Servers and at least one C-Plane Server. Preferably, the U-Plane Servers and C-Plane Servers are coupled with each other, the base stations, and the RAN IP Gateway using stacked, layered protocol connections having a lower transport layer configured to use Internet Protocol (IP).

0034Optionally, a Voice Gateway having a Pulse Code Modulation (PCM) port for external connection may be provided for the RLAN. The Voice Gateway is preferably coupled with a U-plane and a C-Plane Server (or an RNC where RNCs are used) using stacked, layered protocol connections having a lower transport layer configured to use Internet Protocol (IP).

0035In another aspect of the invention, the RLAN has one or more Radio Network Controllers (RNCs) coupled with base stations and a RAN IP Gateway to which at least one RNC is coupled via an Iu-PS interface using a stacked, layered protocol connection having a lower transport layer configured to use Internet Protocol (IP). Preferably, the RNCs are coupled the base stations and each other using stacked, layered protocol connections having a lower transport layer configured to use Internet Protocol (IP). Preferably, each base station has a transceiver configured with a Uu interface for conducting time division duplex (TDD) wideband code division multiple access (W-CDMA) wireless communications with UEs in a selected geographic region and the RAN IP Gateway has a SGSN that is coupled with the RNCs.

0036In another aspect of the invention, the RLAN supports voice communications over IP and has a RAN IP Gateway having a GGSN for connection with the Internet that passes compressed voice data. The RLAN is preferably connected to the Internet via an internet service provider (ISP) that has a voice gateway that converts compressed voice data and Pulse Code Modulation (PCM) signaling using a known compression protocol, which may or may not be the type of voice compression data used by UEs conducting wireless communications with the RLAN.

0037Where the UEs use one compression protocol and the RLAN is connected with the Internet via an ISP having a voice gateway that converts compressed voice data and PCM signaling using a different compression protocol, the RLAN includes a voice data converter for converting between compressed voice data of the two different compression protocols. Preferably, the RAN IP Gateway includes the voice data converter which is, for example, configured to covert between AMR compressed voice data and G.729 compressed voice data. The RLAN may be configured with U-Plane and C-Plane Servers or RNCs, but preferably all component interfaces within the RLAN use stacked, layered protocol connections having a lower transport layer configured to use Internet Protocol (IP).

0038The invention further provides a telecommunication network having one or more radio network for providing concurrent wireless telecommunication services for a plurality of UEs and an associated CN for supporting AAA functions of UEs for which the telecommunication network is a Home Network. One or more of the radio networks is a RLAN having a RAN IP Gateway that has a GGSN configured with a GI interface for connection with the Internet and is configured to communicate AAA function information to the CN. Preferably, the RLANs each have one or more base stations that have a transceiver for conducting TDD-CDMA wireless communications with UEs in a selected geographic region. Preferably, the RLANs have controllers coupled with the base stations. Preferably, the RLANs' RAN IP Gateways have a SGSN that is coupled with the respective controllers.

0039The RLAN may be configured without a direct CN connection where the RAN IP Gateway is configured for communication of AAA function information with the CN by tunneling data through an Internet connection. Alternatively, the RAN IP Gateway has a coupling with the CN for communication of AAA function information with the CN via a limited connection, such as a Radius/Diameter or MAP supporting connection or a conventional Iu-CS interface, or a full conventional Iu interface.

0040Preferably, the RAN IP Gateways have GGSNs configured for connection with the Internet via a GI interface. For mobile support, the GI interface is preferably configured with Mobile IP v4 or Mobile IP v6.

0041Other objects and advantages of the present invention will be apparent to those skilled in the art from the following detailed description and the drawings.

BRIEF DESCRIPTION OF THE DRAWING(S)

0042<figref idref="DRAWINGS">FIG. 1</figref> is a graphic illustration of a conventional UMTS network in accordance with current 3GPP specification.

0043<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram showing various components and interfaces of the network illustrated in <figref idref="DRAWINGS">FIG. 1</figref>.

0044<figref idref="DRAWINGS">FIG. 3</figref> is a schematic diagram of the conventional network illustrated in <figref idref="DRAWINGS">FIGS. 1 and 2</figref> indicating layered stacked protocols of the various component interfaces in both signaling and user data planes.

0045<figref idref="DRAWINGS">FIG. 4</figref> is a graphic illustration of a UMTS network including a RLAN with a direct Internet link in accordance with the teachings of the present invention.

0046<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram showing various components of the network shown in <figref idref="DRAWINGS">FIG. 4</figref>.

0047<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram showing a variation of the network where the RLAN has no direct connection with the UMTS Core Network.

0048<figref idref="DRAWINGS">FIG. 7</figref> is a schematic illustration of signaling data flow in the UMTS network illustrated in <figref idref="DRAWINGS">FIG. 6</figref>.

0049<figref idref="DRAWINGS">FIG. 8</figref> is a graphic illustration of a second variation of the UMTS network illustrated in <figref idref="DRAWINGS">FIG. 4</figref> wherein the RLAN has a first type of limited connection with the UMTS Core Network.

0050<figref idref="DRAWINGS">FIG. 9</figref> is a graphic illustration of a second variation of the UMTS network illustrated in <figref idref="DRAWINGS">FIG. 4</figref> wherein the RLAN has a second type of limited connection with the UMTS Core Network.

0051<figref idref="DRAWINGS">FIGS. 10A and 10B</figref> illustrate two variations of IP packet data flow for the networks shown in <figref idref="DRAWINGS">FIGS. 4</figref>, <b>8</b> and <b>9</b> wherein Mobile IP v4 protocol is implemented by the RLAN.

0052<figref idref="DRAWINGS">FIGS. 11A and 11B</figref> illustrate two variations of IP packet data flow for the networks shown in <figref idref="DRAWINGS">FIGS. 4</figref>, <b>8</b> and <b>9</b> wherein Mobile IP v6 protocol is implemented by the RLAN.

0053<figref idref="DRAWINGS">FIG. 12</figref> is a schematic illustration of preferred signaling plane and user plane interfaces within a RLAN made in accordance with the teachings of the present invention.

0054<figref idref="DRAWINGS">FIG. 13</figref> is a schematic illustration of a RLAN having a single Radio Network Controller in accordance with the teachings of the present invention.

0055<figref idref="DRAWINGS">FIG. 14</figref> is a schematic illustration of a RLAN having multiple Radio Network Controllers made in accordance with the teachings of the present invention.

0056<figref idref="DRAWINGS">FIG. 15</figref> is an illustrated diagram of an alternate configuration of an RLAN having separate servers for user data and control signals and also an optional voice gateway made in accordance with the teachings of the present invention.

0057<figref idref="DRAWINGS">FIG. 16</figref> is a block diagram of components of the RLAN illustrated in <figref idref="DRAWINGS">FIG. 15</figref>.

0058<figref idref="DRAWINGS">FIG. 17</figref> is a schematic diagram illustrating a preferred protocol stack for the control plane interfaces of a RLAN made in accordance with the teachings of the present invention.

0059<figref idref="DRAWINGS">FIG. 18</figref> is a schematic diagram illustrating a preferred protocol stack for the user plane interfaces of a RLAN made in accordance with the teachings of the present invention.

0060<figref idref="DRAWINGS">FIGS. 19</figref>, <b>20</b> and <b>21</b> are schematic diagrams illustrating three variations of interface protocol stacks in the user plane for supporting voice communication between a UE having a wireless connection with an RLAN and an ISP connected to the RLAN which has a voice gateway.

0061<figref idref="DRAWINGS">FIG. 22</figref> is a schematic diagram illustrating a variation of interface protocol stacks in the control plane for supporting voice communication between a UE having a wireless connection with an RLAN and an ISP connected to the RLAN which has a voice gateway.

0062<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>TABLE OF ACRONYMS</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="63pt" align="left" /><colspec colname="2" colwidth="140pt" align="left" /><tbody valign="top"><row><entry /><entry>2G</entry><entry>Second Generation</entry></row><row><entry /><entry>2.5G</entry><entry>Second Generation Revision</entry></row><row><entry /><entry>3GPP</entry><entry>Third Generation Partnership Project</entry></row><row><entry /><entry>AAA functions</entry><entry>Authentication, Authorization and</entry></row><row><entry /><entry /><entry>Accounting functions</entry></row><row><entry /><entry>AAL2</entry><entry>ATM Adaptation Layer Type 2</entry></row><row><entry /><entry>AAL5</entry><entry>ATM Adaptation Layer Type 5</entry></row><row><entry /><entry>AMR</entry><entry>A type of voice data compression</entry></row><row><entry /><entry>ATM</entry><entry>Asynchronous Transfer Mode</entry></row><row><entry /><entry>CDMA</entry><entry>Code Division Multiple Access</entry></row><row><entry /><entry>CN</entry><entry>Core Network</entry></row><row><entry /><entry>CODECs</entry><entry>Coder/Decoders</entry></row><row><entry /><entry>C-RNSs</entry><entry>Control Radio Network Subsystems</entry></row><row><entry /><entry>CS</entry><entry>Circuit Switched</entry></row><row><entry /><entry>ETSI</entry><entry>European Telecommunications Standard</entry></row><row><entry /><entry /><entry>Institute</entry></row><row><entry /><entry>ETSI SMG</entry><entry>ETSI - Special Mobile Group</entry></row><row><entry /><entry>FA</entry><entry>Forwarding Address</entry></row><row><entry /><entry>FN</entry><entry>Foreign Network</entry></row><row><entry /><entry>G.729</entry><entry>A type of voice data compression</entry></row><row><entry /><entry>GGSN</entry><entry>Gateway GPRS Support Node</entry></row><row><entry /><entry>GMM</entry><entry>GPRS Mobility Management</entry></row><row><entry /><entry>GMSC</entry><entry>Gateway Mobile Switching Center</entry></row><row><entry /><entry>GPRS</entry><entry>General Packet Radio Service</entry></row><row><entry /><entry>GSM</entry><entry>Global System for Mobile Tele-</entry></row><row><entry /><entry /><entry>communications</entry></row><row><entry /><entry>GTP</entry><entry>GPRS Tunneling Protocol</entry></row><row><entry /><entry>GW</entry><entry>Gateway</entry></row><row><entry /><entry>H.323/SIP</entry><entry>H.323 Format for a Session</entry></row><row><entry /><entry /><entry>Initiated Protocol</entry></row><row><entry /><entry>HLR</entry><entry>Home Location Register</entry></row><row><entry /><entry>HN</entry><entry>Home Network</entry></row><row><entry /><entry>HSS</entry><entry>Home Service Server</entry></row><row><entry /><entry>IP</entry><entry>Internet Protocol</entry></row><row><entry /><entry>ISDN</entry><entry>Integrated Services Digital</entry></row><row><entry /><entry /><entry>Network</entry></row><row><entry /><entry>ISP</entry><entry>Internet Service Provider</entry></row><row><entry /><entry>Iu-CS</entry><entry>Iu sub Interface for Circuit</entry></row><row><entry /><entry /><entry>Switched service</entry></row><row><entry /><entry>Iu-PS</entry><entry>Iu sub Interface for Packet</entry></row><row><entry /><entry /><entry>Switched service</entry></row><row><entry /><entry>IWU</entry><entry>Inter Working Unit</entry></row><row><entry /><entry>M3UA</entry><entry>Message Transfer Part Level 3</entry></row><row><entry /><entry /><entry>SCCP SS7 Adaptation Layer</entry></row><row><entry /><entry>MAC</entry><entry>Medium Access Control</entry></row><row><entry /><entry>MAP</entry><entry>Mobile Application Part</entry></row><row><entry /><entry>MSC</entry><entry>Mobile Switching Centre</entry></row><row><entry /><entry>NRT</entry><entry>Non-Real Time</entry></row><row><entry /><entry>PCM</entry><entry>Pulse Code Modulation</entry></row><row><entry /><entry>PLMN</entry><entry>Public Land Mobile Network</entry></row><row><entry /><entry>PS</entry><entry>Packet Switched</entry></row><row><entry /><entry>PSTN</entry><entry>Public Switch Telephone Network</entry></row><row><entry /><entry>RANAP</entry><entry>Radio Access Network Application</entry></row><row><entry /><entry /><entry>Part</entry></row><row><entry /><entry>RAN IP</entry><entry>Radio Access Network Internet Protocol</entry></row><row><entry /><entry>RIP GW</entry><entry>RAN IP Gateway</entry></row><row><entry /><entry>RLAN</entry><entry>Radio Local Area Network</entry></row><row><entry /><entry>RLC</entry><entry>Radio Link Control</entry></row><row><entry /><entry>RNC</entry><entry>Radio Network Controller</entry></row><row><entry /><entry>RRC</entry><entry>Radio Resource Control</entry></row><row><entry /><entry>RT</entry><entry>Real Time</entry></row><row><entry /><entry>SCCP/MTP</entry><entry>Signaling Connection Control Part,</entry></row><row><entry /><entry /><entry>Message Transfer Part</entry></row><row><entry /><entry>SGSN</entry><entry>Serving GPRS Support Node</entry></row><row><entry /><entry>SCTP</entry><entry>Stream Control Transmission Protocol</entry></row><row><entry /><entry>SM</entry><entry>Session Management</entry></row><row><entry /><entry>SMS</entry><entry>Short Message Service</entry></row><row><entry /><entry>S-RNS</entry><entry>Serving Radio Network Subsystems</entry></row><row><entry /><entry>SS7</entry><entry>Signaling System 7</entry></row><row><entry /><entry>SSCF</entry><entry>Service Specific Coordination Function</entry></row><row><entry /><entry>SSCOP</entry><entry>Service Specific Connection Oriented</entry></row><row><entry /><entry /><entry>Protocol</entry></row><row><entry /><entry>TDD</entry><entry>Time Division Duplex</entry></row><row><entry /><entry>UDP/IP</entry><entry>User Data Protocol for the Internet</entry></row><row><entry /><entry /><entry>Protocol</entry></row><row><entry /><entry>UE</entry><entry>User Equipment</entry></row><row><entry /><entry>UMTS</entry><entry>Universal Mobile Telecommunications</entry></row><row><entry /><entry /><entry>System</entry></row><row><entry /><entry>UTRAN</entry><entry>UMTS Terrestrial Radio Access Network</entry></row><row><entry /><entry>VLR</entry><entry>Visitor Location Register</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

0063With reference to <figref idref="DRAWINGS">FIG. 4</figref> there is shown a modified Universal Mobile Terrestrial System (UMTS) network having a Radio Local Area Network (RLAN) with a direct Internet connections. As shown in <figref idref="DRAWINGS">FIG. 5</figref>, the RLAN employs base stations to communicate via a wireless radio interface with the various types of User Equipments (UEs). Preferably the base stations are of the type specified in 3GPP as node Bs. A radio controller is coupled to the base station to control the wireless interface. Preferably the radio controller is a Radio Network Controller (RNC) made in accordance with 3GPP specification. Various combinations of Node Bs and RNCs may be employed as used in a conventional 3GPP UTRAN. Collectively, the geographic range of the wireless communications conducted with the base station of the RLAN defines the RLAN's service coverage area.

0064Unlike a conventional UTRAN, the RLAN of the present invention includes a Radio Access Network Internet Protocol (RAN IP) gateway which provides connectivity for the RLAN outside its service coverage area, i.e. the geographic area served by the wireless communication with its base stations. As illustrated in <figref idref="DRAWINGS">FIGS. 4 and 5</figref>, the RAN IP gateway has a direct Internet connection and may have the standard direct UMTS network connected through an Iu interface with an associated Core Network. Alternatively, as illustrated in <figref idref="DRAWINGS">FIG. 6</figref>, the direct interface between an associated Core Network and the RAN IP gateway may be omitted so that the RAN IP Gateway can have only a direct connection with the Internet. In such case, as illustrated in <figref idref="DRAWINGS">FIG. 7</figref>, the RLAN of the present invention may still form a part of a UMTS by the tunneling of control and AAA function information to a Core Network which serves as its Home CN.

0065<figref idref="DRAWINGS">FIGS. 8 and 9</figref> illustrate two separate versions of an RLAN made in accordance with the teachings of the present invention wherein the RAN IP Gateway is configured with a control signal port for establishing a limited direct connection with its Home UMTS Core Network. In particular, the limited connectivity transports information needed to provide AAA function support for the CN.

0066The RAN IP Gateway control signal port may be configured, as illustrated in <figref idref="DRAWINGS">FIG. 8</figref>, to provide control signal data using radius/diameter based access in which case the core network includes an Inter Working Unit (IWU) as specified in 3GPP which converts AAA function information into conventional Mobile Application Part (MAP) signaling for connection with the HSS/HLR of the Core Network. Alternatively, as illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, the RAN IP Gateway control signal port can be configured as a subset of a standard Gr interface which supports MAP signaling which can be directly used by the HSS/HLR of the CN.

0067Preferably, the RAN IP Gateway employs a standard GI interface with the Internet and can be utilized as a stand-alone system without any association with a Core Network of a UMTS. However, in order to support mobility management with roaming and hand-over services available for subscriber UEs of the RLAN, an AAA function connection with a Core Network, such as by way of the various alternatives illustrated in <figref idref="DRAWINGS">FIGS. 7</figref>, <b>8</b> and <b>9</b>,is desirable. In such case, in addition to a standard GI interface between the RAN IP Gateway of the RLAN and the Internet, a mobile IP protocol is supported. Preferred examples of such mobile IP protocols are the Mobile IP v4 protocol and the Mobile IP v6 protocol as specified by IETF.

0068<figref idref="DRAWINGS">FIG. 10A</figref> illustrates IP packet data flow for a communication between a first UE having a wireless connection with the RLAN and a second UE outside the wireless service region of the RLAN where Mobile IP v4 is implemented on the GI interface between the RAN IP Gateway and the Internet. In such case, user data from the first UE is sent in IP packet format from the RAN IP Gateway of the RLAN through the Internet to the address provided by the second UE. The second UE communications are directed to the Home Address of the first UE which is maintained at the Core Network since in this example the first UE has the CN as its Home CN. The CN receives the IP data packets from the second UE and then the CN forwards the IP packets to the current location of the first UE which is maintained in the CN's HLR as the Forwarding Address (FA) of the first UE.

0069In this example, since the first UE is “home”, the CN tunnels the IP Packets through the Internet to the RAN IP gateway for communication to the first UE. In the case of the first UE traveling outside of the RLAN, its location will be registered with the Core Network and the data packets directed to the address where the first UE is currently located be used by the core network to direct the IP packet data to the current location of the first UE.

0070<figref idref="DRAWINGS">FIG. 10B</figref> illustrates an alternate approach where Mobile IP v4 is implemented on the GI interface using with reverse path tunneling such that the RLAN directs the IP packets of the first UE's user data to the Home CN where they are relayed to the second UE in a conventional manner.

0071When the RLAN has connectivity using a GI interface that implements Mobile IP v6, the IP packet data exchange between the first UE and the second UE will contain binding updates, as illustrated in <figref idref="DRAWINGS">FIG. 11A</figref>, which will reflect any redirection of the IP packets needed for hand-over. <figref idref="DRAWINGS">FIG. 11B</figref> illustrates an alternative approach using a GI interface implementing mobile IP v6 that includes tunneling between the RLAN and the Home CN. In such case, the CN directly tracks location information of the first UE and the second UE may communicate with the first UE's Home CN in any type of conventional manner.

0072With reference to <figref idref="DRAWINGS">FIG. 12</figref>, there is shown the construction of preferred interfaces between the components of the RLAN of the present invention. The UE interface between the RLAN via the base station, Node B, is preferably a standard Uu interface for connection with UEs as specified by 3GPP. An Iub interface between each Node B and RNC is preferably implemented both in the control plane and the user data plane as a layered stacked protocol having Internet Protocol (IP) as the transport layer. Similarly at least a subset of an Iu-PS interface is preferably provided between an RNC and the RAN IP Gateway that is a layered stacked protocol having IP as the transport layer.

0073In a conventional UMTS where SS7 is implemented over ATM, the MTP3/SSCF/SSCOP layers help SCCP, which is the top layer of the SS7 stack, to plug onto an underlying ATM stack. In the preferred IP approach used in conjunction with the present invention, the M3UA/SCTP stack helps SCCP connect onto IP. Essentially, the M3UA/SCTP stack in the preferred IP-based configuration replaces the MTP3/SSCF/SSCOP layers that are used in the conventional SS7-over-ATM approach. The specific details of these standard protocol stack architecture are defined in the IETF (Internet) standards. The use of IP in lieu of ATS enables cost-savings as well as PICO cells for office and campus departments.

0074Where the RLAN has multiple RNCs, the RNCs can be interfaced via an Iur interface having layered stacked protocols for both the signaling plane and user plane using an IP transport layer. Each RNC is connected to one or more Node Bs which in turn serve in plurality of UEs within respective geographic areas that may overlap to enable intra-RLAN service region handover.

0075Handover of a UE communication with one Node B within the RLAN to another Node B within the RLAN, intra-RLAN handover, is conducted in the conventional manner specified in 3GPP for intra-UTRAN handover. However, when a UE communicating with a Node B of the RLAN moves outside the RLAN service region, handover is implemented via the RAN IP gateway utilizing IP packet service, preferably, implemented with Mobile IP v4 or Mobile IP v6 as discussed above.

0076<figref idref="DRAWINGS">FIG. 13</figref> illustrates the subcomponents of a preferred RLAN in accordance with the present invention. The RNC can be divided into standard Control and Serving Radio Network Subsystems (C-RNSs and S-RNSs) connected by an internal Iur interface. In such a configuration, the S-RNS functions are coupled to a SGSN subcomponent of the RAN IP gateway which supports a subset of the standard SGSN functions, namely, GPRS Mobility Management (GMM), Session Management (SM) and Short Message Service (SMS). The SGSN subcomponent interfaces with a GGSN subcomponent having a subset of a standard GGSN functions including an access router and gateway functions support for the SGNS subcomponent functions and a GI interface with mobile IP for external connectivity to the Internet. The SGSN subcomponent interface with the GGSN subcomponent is preferably via modified Gn/Gp interface, being a subset of the standard Gn/Gp interface for a CN's SGNS and GGSN.

0077Optionally, the RAN IP Gateway has an AAA function communication subcomponent that is also connected to the SGSN subcomponent and provides a port for limited external connectivity to an associated CN. The port supporting either a Gr interface or a Radius/Diameter interface as discussed above in connection with <figref idref="DRAWINGS">FIGS. 8 and 9</figref>.

0078As shown in <figref idref="DRAWINGS">Fig. 14</figref>, multiple RNCs of the RLAN can be provided coupled with the SGSN subcomponent by an Iu-PS interface which includes sufficient connectivity to support the functions of the SGSN subcomponent. Where multiple RNCs are provided, they are preferably coupled by a standard Iur interface which utilizes an IP transprot layer.

0079The use of IP for the transport layer of the various components of the RLAN readily lends itself to implementing the RNC functions in separate computer servers to independently process the user data of communications and the signaling as illustrated in <figref idref="DRAWINGS">FIG. 15</figref>. Referring to <figref idref="DRAWINGS">FIG. 16</figref>, there is a component diagram where the radio control means is divided between U-plane and C-plane servers. In addition to the basic RLAN components, an optional Voice Gateway is also illustrated in <figref idref="DRAWINGS">FIGS. 15 and 16</figref>.

0080Each Node B of the RLAN has a connection using an IP transport layer with a U-plane server which transports user data. Each Node B of the RLAN also has a separate connection with a C-plane server via a standard Iub signal control interface having an IP transport layer. Both the U-plane server and C-plane server are connected to the IP gateway using layered stacked protocols, preferably having IP as the transport layer.

0081For multiple C-plane server configurations, each can be coupled to each other via a standard Iur interface, but only one is required to be directly connected to the RIP GW. This allows the sharing of resources for control signal processing which is useful when one area of the RLAN becomes much busier in other areas to spread out the signal processing between C-plane servers. A plurality of C-plane and U-plane servers can be connected in a mesh network for sharing both C-plane and U-plane resources via stacked layer protocols preferably having an IP transport layer.

0082Where the optional voice gateway having external connectivity via PCM circuit is provided, the U-plane server and C-plane server are coupled to the voice gateway via a stacked layer protocols preferably having an IP transport layer. The C-plane server is then coupled to the U-plane server via a Media gateway control protocol gateway (Megaco) over an IP transport layer. Megaco is a control plane protocol that sets up the bearer connection(s) between a Voice gateway elements, as part of call establishment.

0083Referring to <figref idref="DRAWINGS">FIGS. 17 and 18</figref>, there are shown, respectively, preferred C-plane and U-plane protocol stacks which are implemented between the Node Bs, RNCs (or U- and C-plane servers) and the RAN IP Gateway of the RLAN. In each drawing, the preferred over air protocol stack implemented via the Uu interface with UEs is also shown.

0084The RLAN can be configured with voice support over its external IP connection. In such case, the RIP gateway is connected with an Internet Service Provider (ISP) which in turn has a PCM voice gateway. The PCM voice gateway converts voice compression data into a Pulse Code Modulation (PCM) format for external voice communications.

0085Vocoders are provided that use Coder/Decoders (CODECs) for compression of voice data. Two common types vocoder formats are the AMR vocoder format and G.729 compression format. <figref idref="DRAWINGS">FIGS. 19 and 21</figref> show preferred U-plane protocol stacks which are implemented where the voice gateway of the ISP to which the RLAN is connected uses the same type of voice compression interface as the UE. AMR vocoder format being illustrated in <figref idref="DRAWINGS">FIG. 19</figref>; G.729 vocoder format being illustrated in <figref idref="DRAWINGS">FIG. 21</figref>. The voice over IP is simply transferred as regular packet data over the IP interface without change.

0086Where the UE utilizes a different voice compression protocol than the voice gateway of the ISP, a converter is provided in the RNC or the RAN IP Gateway. <figref idref="DRAWINGS">FIG. 20</figref> shows preferred U-plane protocol stacks, where the UE utilizes an AMR vocoder and the ISP voice gateway utilizes a G.729 vocoder. Preferably, the RAN IP Gateway (RIP GW) includes the AMR/G.729 converter. In the case illustrated in <figref idref="DRAWINGS">FIG. 20</figref>, the converter converts AMR compressed data received from the node B to G.729 format compressed voice format for output by the RIP GW. Where the RLAN utilizes separate U-plane and C-plane servers, the compressed voice data is transported by a U-plane server and the converters may be located in either the U-plane servers or the IP gateway.

0087With reference from <figref idref="DRAWINGS">FIG. 22</figref>, there is shown preferred control plane protocol stack architecture for supporting voice using standard H.323 format for a Session Initiated Protocol (H.323/SIP) over TCP/UDP carry by IP. The control signaling is essentially the same irrespective of the type of voice data compression conducted in the U-Place.

0088Although the present invention has been described based on particular configurations, other variations will be apparent to those of ordinary skill in the art and are within the scope of the present invention.