US20140198754A1 - Mobile telecommunications architecture - Google Patents
Mobile telecommunications architecture Download PDFInfo
- Publication number
- US20140198754A1 US20140198754A1 US14/162,379 US201414162379A US2014198754A1 US 20140198754 A1 US20140198754 A1 US 20140198754A1 US 201414162379 A US201414162379 A US 201414162379A US 2014198754 A1 US2014198754 A1 US 2014198754A1
- Authority
- US
- United States
- Prior art keywords
- base stations
- small scale
- scale base
- radio network
- gateway
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H04W72/0413—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/12—Access point controller devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
Definitions
- MSC mobile switching center
- Each MSC server traditionally connected via network connections to a relatively limited number of radio network controllers (RNC), in UMTS parlance, or base station controllers (BSC) in GSM network terminology.
- RNC radio network controller
- BSC base station controllers
- Each such controller typically connected to and controlled a number of macrocellular bases stations, referred to as “node B” in UMTS terminology and as base transceiver stations (BTS) in a GSM network.
- BTS base transceiver stations
- Each controller typically had a T-1 or similar connection to each base station.
- Each base station included a large tower or other structure on which one or more transceivers were mounted to provide coverage for users who transited a coverage area or “cell” with which the base station was associated. Since a relatively few number of base station controllers (e.g., RNC or BSC) could support collective a relatively large number of base stations, typically MSC servers (and other MSC's) have been configured to support at most a limited number of controllers (e.g., RNC or BSC), e.g., on the order of 4,000.
- RNC base station controllers
- femtocells and other small scale base stations have been developed and deployed.
- UMTS access point UMTS access point
- UAP small scale base station
- small scale base station are used interchangeably to refer to a base station that is small in size relative to a traditional macrocellular base station.
- Each such base station typically provides coverage for a relatively small geographic coverage area, compared to a traditional macrocellular base station, and/or for a restricted and/or otherwise limited set of subscribers.
- FIG. 1 is a block diagram illustrating an embodiment of a mobile telecommunications system.
- FIG. 2 is a flow diagram illustrating an embodiment of a process for providing connectivity to a mobile telecommunications network.
- FIG. 4 is a block diagram illustrating an embodiment of a mobile telecommunications system.
- FIG. 5 is a flow diagram illustrating an embodiment of a process for configuring mobile telecommunication base stations subsystem elements.
- FIG. 6 is a flow diagram illustrating an embodiment of a process for deploying a femtocell.
- FIG. 7 is a flow diagram illustrating an embodiment of a process for establishing at a femto gateway a mapping usable to route signaling messages to the RNC's with which they are associated.
- FIG. 8 is a block diagram illustrating an embodiment of a data structure for storing a mapping data usable to route signaling messages to the RNC's with which they are associated.
- FIG. 9 is a flow diagram illustrating an embodiment of a process for routing downlink messages to RNC's.
- FIG. 10 is a flow diagram illustrating an embodiment of a process for processing uplink messages sent to the MSC server.
- the invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
- these implementations, or any other form that the invention may take, may be referred to as techniques.
- the order of the steps of disclosed processes may be altered within the scope of the invention.
- a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
- the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- Radio network controller Projecting multiple radio network controllers (RNC) or other base station controllers to an MSC server or other MSC as a single logical controller is disclosed.
- the UMTS term “radio network controller” or “RNC” is used generically to reference to a UMTS RNC or a corresponding base station controller or other corresponding entity in a non-UMTS network.
- each of a plurality of femtocells or other base stations is configured to operation at least in part as a radio network (or other base station) controller.
- Signaling messages and/or voice/data traffic from a plurality of such base stations is received via an IP or other public or private network and aggregated at a femtocells (or other) gateway (FGW) and provide upstream to an MSC server (or other MSC) via a single, shared RNC connection to the MSC.
- FGW femtocell gateway
- MSC server or other MSC
- Downlink messages from the MSC server are mapped to individual femtocells (or other base stations) and each message is provided via the aforementioned network to the femtocell (or other base station) with which the message is associated.
- FIG. 1 is a block diagram illustrating an embodiment of a mobile telecommunications system.
- each of a plurality of femto access points (FAP) 102 - 110 connects via the Internet 112 (or another IP or other public or private network) with a corresponding one of femto gateways 114 and 116 .
- the femto gateways connect via a private network (or other network) 118 to an MSC server 120 .
- FAP femto access points
- improved performance is provided by integrating into the femtocells or other small scale base stations, such as FAP's 102 - 110 , the Node B functions together with functions traditionally performed by an RNC (or other base station controller).
- RNC or other base station controller
- an MSC server such as MSC server 120 of FIG. 1 is configured to support at most on the order of 4,000 RNC's, while within an area typically served by an MSC server potentially hundreds of thousands of femtocells could be deployed.
- projecting to the MSC server as a single logical RNC multiple femtocells into which RNC functionality has been integrated is disclosed.
- each femto gateway such as femto gateways 114 and 116 , is configured to establish with the MSC server a single (or some other number fewer than the number of base stations the femto gateway supports) RNC connection to the MSC server.
- Uplink messages received from the femtocells the femto gateway supports e.g., FAP's 102 , 104 , and 106 , in the case of femto gateway 114 in the example shown in FIG. 1
- femto gateway 116 would aggregate uplink messages from FAP 108 and FAP 110 (any other femtocells it supports) and provide them to MSC server 120 as if they were from a single logical RNC.) For downlink messages, each message is mapped, as described more fully below, to the femtocells (FAP) to which it corresponds and sent via a corresponding network connection to that femtocell.
- FAP femtocells
- FIG. 2 is a flow diagram illustrating an embodiment of a process for providing connectivity to a mobile telecommunications network.
- the process of FIG. 2 is implemented by a femto or other gateway, such as gateways 114 and 116 of FIG. 1 .
- each of a plurality of small scale or other base stations into which RNC (or other base station controller) functionality has been integrated is associated with a single RNC connection to an MSC server (or other MSC) ( 202 ).
- the single RNC connection to the MSC server is used to communicate with the MSC server on behalf of the plurality of base stations/RNC's in such a manner that to the MSC server the single RNC connection only appears to be associated with a single logical RNC ( 204 ).
- FIG. 3 is a block diagram illustrating an embodiment of a mobile telecommunications system.
- RNC's 302 connect via the Internet 304 to a femto gateway 306 .
- each of at least a subset of the RNC's 302 comprises a femtocell or other small scale base station configured to serve as both a base station (e.g., node b) and as an RNC. While three RNC's are shown in FIG. 3 , any number up to a maximum number of base stations that an associated MSC server can support may be included in some embodiments.
- a second plurality of RNC's 312 connects via the Internet 304 with an associated femto gateway 316 .
- Each femto gateway 306 , 316 is configured to aggregate uplink messages (SCTP streams) from the femtocells/RNCs it supports and provide such uplink messages via a single RNC connection (single MTP3 over ATM connection) to MSC server 320 .
- Downlink messages are mapped to the particular RNC (femtocells) to which they correspond and each is sent via the Internet 304 by being included in the RNC/femtocell-specific SCTP stream to which the downlink message corresponds.
- the femto gateways 306 , 316 are configured to learn and store a mapping that enables downlink messages to be routed to the correct RNC, as described more fully below.
- FIG. 4 is a block diagram illustrating an embodiment of a mobile telecommunications system.
- the example shown in FIG. 4 is similar to the system shown in FIG. 3 except that connectivity to the MSC server is provided via a private IP network.
- a plurality of RNC's 402 connect via the Internet 404 to a femto gateway 406 .
- a second plurality of RNC's 412 connects via the Internet 404 with an associated femto gateway 416 .
- Femto gateways 406 and 416 connect via a private network 418 with an MSC server 420 via SCTP over IP connections to the MSC server 420 .
- each of the RNC's 402 , 412 is configured to establish with its corresponding femto gateway an SCTP over IP connection.
- each establishes with the MSC server 420 via its serving femto gateway 406 or 416 one or more traditionally RNC-associated protocol connections or sessions, e.g., RANAP, signaling connection control protocol (SCCP), and M3UA in the example shown in FIG. 4 .
- Each femto gateway 406 , 416 establishes with MSC server 420 a single RNC connection via network 418 , which in the example shown comprises an IP network.
- Each femto gateway 406 , 416 is configured to aggregate uplink messages (SCTP streams) from the femtocells/RNCs it supports and provide such uplink messages via a single RNC connection (single SCTP uplink stream) to MSC server 420 .
- Downlink messages are mapped to the particular RNC (femtocells) to which they correspond and each is sent via the Internet 404 by being included in the RNC/femtocell-specific SCTP stream to which the downlink message corresponds.
- FIG. 5 is a flow diagram illustrating an embodiment of a process for configuring mobile telecommunication base stations subsystem elements.
- one or more femto gateways are configured and deployed ( 502 ).
- each femto gateway is configured to communicate with an MSC server on behalf of a plurality of RNC's, such as femtocells configured to perform at least some RNC functions, in a manner that makes the plurality of RNC's appear to the MSC server to be a single logical RNC.
- RNC's such as femtocells configured to perform at least some RNC functions, in a manner that makes the plurality of RNC's appear to the MSC server to be a single logical RNC.
- One or more femtocells are configured and deployed ( 504 ).
- each femtocell is configured to perform one or more RNC functions.
- each femtocell is configured to establish an SCTP over IP, or other, network connection to a serving femto gateway.
- Each is further configured to communicate via the femto gateway with a serving MSC server, including by establishing with the MSC server, via the femto gateway, communication sessions under one or more communication protocols traditionally used by a typical macrocellular RNC to communicate with the MSC server.
- FIG. 6 is a flow diagram illustrating an embodiment of a process for deploying a femtocell.
- a femtocell is configured to perform the process of FIG. 6 upon initially being powered up and connected to the Internet or another public or private network.
- the femtocell upon deployment ( 602 ) the femtocell establishes an IP connection to a serving femto gateway ( 604 ).
- the femtocell establishes with the femto gateway a signaling control protocol communication session and/or connection suitable for sending and receiving mobile telecommunication signaling messages, e.g., an SCTP connection or session ( 606 ).
- the femtocell then establishes with a serving MSC server, via the femto gateway, communication under one or more signaling protocols traditionally used by macrocellular RNC's to communicate with the MSC server on a per base station basis, e.g., an SCCP connection or session ( 608 ).
- a serving MSC server via the femto gateway, communication under one or more signaling protocols traditionally used by macrocellular RNC's to communicate with the MSC server on a per base station basis, e.g., an SCCP connection or session ( 608 ).
- FIG. 10 is a flow diagram illustrating an embodiment of a process for processing uplink messages sent to the MSC server.
- the process of FIG. 10 is implemented by each of one or more femto gateways, each configured to present to the MSC server as a single logical RNC a plurality of femtocells or other FAP's configured to perform one or more RNC functions.
- uplink messages are received on a plurality of SCTP streams, e.g., SCTP over IP connections, each associated with a corresponding FAP configured to perform at least some RNC functions ( 1002 ).
- the uplink messages are aggregated and sent via a single RNC connection to the MSC server ( 1004 ).
- the process continues until messages are no longer being received, e.g., the femto gateway is taken out of service ( 1006 ).
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 12/290,870, filed Nov. 3, 2008, now allowed, which claims priority to U.S. Provisional Patent Application No. 61/001,749 entitled MOBILE TELECOMMUNICATIONS ARCHITECTURE filed Nov. 2, 2007 which is incorporated herein by reference for all purposes.
- Traditionally connectivity to a mobile telecommunications network, such as a mobile telephone network, has been provided via a mobile switching center (MSC), e.g., an MSC server. Each MSC server traditionally connected via network connections to a relatively limited number of radio network controllers (RNC), in UMTS parlance, or base station controllers (BSC) in GSM network terminology. Each such controller typically connected to and controlled a number of macrocellular bases stations, referred to as “node B” in UMTS terminology and as base transceiver stations (BTS) in a GSM network. Each controller typically had a T-1 or similar connection to each base station. Each base station included a large tower or other structure on which one or more transceivers were mounted to provide coverage for users who transited a coverage area or “cell” with which the base station was associated. Since a relatively few number of base station controllers (e.g., RNC or BSC) could support collective a relatively large number of base stations, typically MSC servers (and other MSC's) have been configured to support at most a limited number of controllers (e.g., RNC or BSC), e.g., on the order of 4,000.
- In recent years, femtocells and other small scale base stations have been developed and deployed. As used herein the terms “femto access point”, “UMTS access point” or “UAP”, and small scale base station are used interchangeably to refer to a base station that is small in size relative to a traditional macrocellular base station. Each such base station typically provides coverage for a relatively small geographic coverage area, compared to a traditional macrocellular base station, and/or for a restricted and/or otherwise limited set of subscribers.
- Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
-
FIG. 1 is a block diagram illustrating an embodiment of a mobile telecommunications system. -
FIG. 2 is a flow diagram illustrating an embodiment of a process for providing connectivity to a mobile telecommunications network. -
FIG. 3 is a block diagram illustrating an embodiment of a mobile telecommunications system. -
FIG. 4 is a block diagram illustrating an embodiment of a mobile telecommunications system. -
FIG. 5 is a flow diagram illustrating an embodiment of a process for configuring mobile telecommunication base stations subsystem elements. -
FIG. 6 is a flow diagram illustrating an embodiment of a process for deploying a femtocell. -
FIG. 7 is a flow diagram illustrating an embodiment of a process for establishing at a femto gateway a mapping usable to route signaling messages to the RNC's with which they are associated. -
FIG. 8 is a block diagram illustrating an embodiment of a data structure for storing a mapping data usable to route signaling messages to the RNC's with which they are associated. -
FIG. 9 is a flow diagram illustrating an embodiment of a process for routing downlink messages to RNC's. -
FIG. 10 is a flow diagram illustrating an embodiment of a process for processing uplink messages sent to the MSC server. - The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
- Projecting multiple radio network controllers (RNC) or other base station controllers to an MSC server or other MSC as a single logical controller is disclosed. As used herein the UMTS term “radio network controller” or “RNC” is used generically to reference to a UMTS RNC or a corresponding base station controller or other corresponding entity in a non-UMTS network. In some embodiments, each of a plurality of femtocells or other base stations is configured to operation at least in part as a radio network (or other base station) controller. Signaling messages and/or voice/data traffic from a plurality of such base stations is received via an IP or other public or private network and aggregated at a femtocells (or other) gateway (FGW) and provide upstream to an MSC server (or other MSC) via a single, shared RNC connection to the MSC. Downlink messages from the MSC server are mapped to individual femtocells (or other base stations) and each message is provided via the aforementioned network to the femtocell (or other base station) with which the message is associated.
-
FIG. 1 is a block diagram illustrating an embodiment of a mobile telecommunications system. In the example shown, each of a plurality of femto access points (FAP) 102-110, for example femtocells, connects via the Internet 112 (or another IP or other public or private network) with a corresponding one of femtogateways MSC server 120. Note that while five FAP's are shown inFIG. 1 , femtocells configured to be deployed in homes or other locations, such as offices or small businesses, could easily number in the many thousands in a relatively concentrated geographic area. In some embodiments, improved performance is provided by integrating into the femtocells or other small scale base stations, such as FAP's 102-110, the Node B functions together with functions traditionally performed by an RNC (or other base station controller). However, typically as noted above an MSC server such asMSC server 120 ofFIG. 1 is configured to support at most on the order of 4,000 RNC's, while within an area typically served by an MSC server potentially hundreds of thousands of femtocells could be deployed. To address this need without requiring changes in legacy MSC servers, projecting to the MSC server as a single logical RNC multiple femtocells into which RNC functionality has been integrated is disclosed. In some embodiments, each femto gateway, such as femtogateways femto gateway 114 in the example shown inFIG. 1 ) are aggregated and sent to the MSC server as a single stream, so as to appear to the MSC server as a single stream received from a single logical RNC. (Likewise, in the example shown inFIG. 1 , femtogateway 116 would aggregate uplink messages from FAP 108 and FAP 110 (any other femtocells it supports) and provide them toMSC server 120 as if they were from a single logical RNC.) For downlink messages, each message is mapped, as described more fully below, to the femtocells (FAP) to which it corresponds and sent via a corresponding network connection to that femtocell. -
FIG. 2 is a flow diagram illustrating an embodiment of a process for providing connectivity to a mobile telecommunications network. In various embodiments, the process ofFIG. 2 is implemented by a femto or other gateway, such asgateways FIG. 1 . In the example shown inFIG. 2 , each of a plurality of small scale or other base stations into which RNC (or other base station controller) functionality has been integrated is associated with a single RNC connection to an MSC server (or other MSC) (202). The single RNC connection to the MSC server is used to communicate with the MSC server on behalf of the plurality of base stations/RNC's in such a manner that to the MSC server the single RNC connection only appears to be associated with a single logical RNC (204). -
FIG. 3 is a block diagram illustrating an embodiment of a mobile telecommunications system. In the example shown, RNC's 302 connect via the Internet 304 to afemto gateway 306. In some embodiments, each of at least a subset of the RNC's 302 comprises a femtocell or other small scale base station configured to serve as both a base station (e.g., node b) and as an RNC. While three RNC's are shown inFIG. 3 , any number up to a maximum number of base stations that an associated MSC server can support may be included in some embodiments. Similarly, a second plurality of RNC's 312 connects via the Internet 304 with an associatedfemto gateway 316. Femtogateways private network 318 with an MSC server 320. In the example shown, each of the RNC's 302, 312 is configured to establish with its corresponding femto gateway an stream control transmission protocol (SCTP) over IP connection. In addition, each establishes with the MSC server 320 via its servingfemto gateway FIG. 3 . Eachfemto gateway network 318, which in the example shown comprises an ATM network. Eachfemto gateway Internet 304 by being included in the RNC/femtocell-specific SCTP stream to which the downlink message corresponds. In various embodiments, thefemto gateways -
FIG. 4 is a block diagram illustrating an embodiment of a mobile telecommunications system. The example shown inFIG. 4 is similar to the system shown inFIG. 3 except that connectivity to the MSC server is provided via a private IP network. In the example shown inFIG. 4 , a plurality of RNC's 402 connect via theInternet 404 to afemto gateway 406. Similarly, a second plurality of RNC's 412 connects via theInternet 404 with an associatedfemto gateway 416.Femto gateways private network 418 with anMSC server 420 via SCTP over IP connections to theMSC server 420. In the example shown, each of the RNC's 402, 412 is configured to establish with its corresponding femto gateway an SCTP over IP connection. In addition, each establishes with theMSC server 420 via its servingfemto gateway FIG. 4 . Eachfemto gateway network 418, which in the example shown comprises an IP network. Eachfemto gateway MSC server 420. Downlink messages are mapped to the particular RNC (femtocells) to which they correspond and each is sent via theInternet 404 by being included in the RNC/femtocell-specific SCTP stream to which the downlink message corresponds. -
FIG. 5 is a flow diagram illustrating an embodiment of a process for configuring mobile telecommunication base stations subsystem elements. In the example shown, one or more femto gateways are configured and deployed (502). In various embodiments, each femto gateway is configured to communicate with an MSC server on behalf of a plurality of RNC's, such as femtocells configured to perform at least some RNC functions, in a manner that makes the plurality of RNC's appear to the MSC server to be a single logical RNC. One or more femtocells are configured and deployed (504). In various embodiments, each femtocell is configured to perform one or more RNC functions. In various embodiments, each femtocell is configured to establish an SCTP over IP, or other, network connection to a serving femto gateway. Each is further configured to communicate via the femto gateway with a serving MSC server, including by establishing with the MSC server, via the femto gateway, communication sessions under one or more communication protocols traditionally used by a typical macrocellular RNC to communicate with the MSC server. -
FIG. 6 is a flow diagram illustrating an embodiment of a process for deploying a femtocell. In various embodiments a femtocell is configured to perform the process ofFIG. 6 upon initially being powered up and connected to the Internet or another public or private network. In the example shown, upon deployment (602) the femtocell establishes an IP connection to a serving femto gateway (604). The femtocell establishes with the femto gateway a signaling control protocol communication session and/or connection suitable for sending and receiving mobile telecommunication signaling messages, e.g., an SCTP connection or session (606). The femtocell then establishes with a serving MSC server, via the femto gateway, communication under one or more signaling protocols traditionally used by macrocellular RNC's to communicate with the MSC server on a per base station basis, e.g., an SCCP connection or session (608). -
FIG. 7 is a flow diagram illustrating an embodiment of a process for establishing at a femto gateway a mapping usable to route signaling messages to the RNC's with which they are associated. In the example shown, a new connection from a femtocell or other FAP is received, e.g., at a femto gateway (702). SCCP or other messages exchanged between the FAP and a serving MSC server are snooped to determine an SCCP identifier for the new FAP (704). The SCCP (or other) identifier is mapped to a connection to the associated FAP, e.g., by storing data mapping the SCCP identifier to an SCTP over IP connection to the FAP (706). -
FIG. 8 is a block diagram illustrating an embodiment of a data structure for storing a mapping data usable to route signaling messages to the RNC's with which they are associated. In various embodiments, the mapping data shown is stored in a memory or other storage on a femto gateway. In the example shown, thedata structure 800 includes a first column for listing a snooped SCCP identifier and a second column for listing an identifier associated with an SCTP stream (e.g., SCTP over IP connection) with which the SCCP identifier stored in the first column is associated. In some embodiments, on receiving a downlink message from the MSC server the femto gateway reads an SCCP identifier from the message and uses that value to look up in data structure 800 a corresponding SCTP stream with which the downlink message is associated. -
FIG. 9 is a flow diagram illustrating an embodiment of a process for routing downlink messages to RNC's. In various embodiments the process ofFIG. 9 is implemented by each of one or more femto gateways, each configured to present to the MSC server as a single logical RNC a plurality of femtocells or other FAP's configured to perform one or more RNC functions. In the example shown, downlink messages received at the femto gateway from the MSC server are monitored (902). For each downlink message that is received (904), an SCCP or other identifier is read (906) and mapped to a corresponding downlink SCTP (or other) stream (908). Each message is then sent to the RNC with which it is associated via the SCTP (or other) connection to which it has been mapped (910). The process continues as subsequent downlink messages are received (904) until done (912), e.g., until the femto gateway is taken out of service. -
FIG. 10 is a flow diagram illustrating an embodiment of a process for processing uplink messages sent to the MSC server. In various embodiments the process ofFIG. 10 is implemented by each of one or more femto gateways, each configured to present to the MSC server as a single logical RNC a plurality of femtocells or other FAP's configured to perform one or more RNC functions. In the example shown, uplink messages are received on a plurality of SCTP streams, e.g., SCTP over IP connections, each associated with a corresponding FAP configured to perform at least some RNC functions (1002). The uplink messages are aggregated and sent via a single RNC connection to the MSC server (1004). The process continues until messages are no longer being received, e.g., the femto gateway is taken out of service (1006). - Using the approach disclosed herein each of a very large number of femtocells or other FAP's in the service area of an MSC server may be configured to perform at least some functions traditionally performed by an RNC, potentially exceeding by large margin a maximum number of RNC connections the MSC server may be configured to support, thereby supporting in home or other deployment of a large number of femtocells or other base stations without requiring changes to legacy MSC servers.
- Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/162,379 US20140198754A1 (en) | 2007-11-02 | 2014-01-23 | Mobile telecommunications architecture |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US174907P | 2007-11-02 | 2007-11-02 | |
US12/290,870 US8638764B2 (en) | 2007-11-02 | 2008-11-03 | Mobile telecommunications architecture |
US14/162,379 US20140198754A1 (en) | 2007-11-02 | 2014-01-23 | Mobile telecommunications architecture |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/290,870 Continuation US8638764B2 (en) | 2007-11-02 | 2008-11-03 | Mobile telecommunications architecture |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140198754A1 true US20140198754A1 (en) | 2014-07-17 |
Family
ID=40591389
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/290,870 Active 2030-08-04 US8638764B2 (en) | 2007-11-02 | 2008-11-03 | Mobile telecommunications architecture |
US14/162,379 Abandoned US20140198754A1 (en) | 2007-11-02 | 2014-01-23 | Mobile telecommunications architecture |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/290,870 Active 2030-08-04 US8638764B2 (en) | 2007-11-02 | 2008-11-03 | Mobile telecommunications architecture |
Country Status (4)
Country | Link |
---|---|
US (2) | US8638764B2 (en) |
EP (1) | EP2208318B1 (en) |
CN (1) | CN101836404B (en) |
WO (1) | WO2009058401A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017142588A1 (en) * | 2016-02-15 | 2017-08-24 | Spidercloud Wireless, Inc. | Ue-measurement assisted closed loop learning approach for real-time optimization of system metrics |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8224291B2 (en) * | 2007-11-15 | 2012-07-17 | Airwalk Communications, Inc. | System, method, and computer-readable medium for mobile-to-mobile calls within femtocell network |
US8437762B2 (en) * | 2008-08-20 | 2013-05-07 | Qualcomm Incorporated | Adaptive transmission (Tx)/reception (Rx) pulse shaping filter for femtocell base stations and mobile stations within a network |
US8452332B2 (en) * | 2008-08-20 | 2013-05-28 | Qualcomm Incorporated | Switching between different transmit/receive pulse shaping filters for limiting adjacent channel interference |
WO2010045264A1 (en) * | 2008-10-13 | 2010-04-22 | Spidercloud Wireless | Method for encapsulating femtocell traffic |
US20100130230A1 (en) * | 2008-11-21 | 2010-05-27 | Qualcomm Incorporated | Beacon sectoring for position determination |
US20100135178A1 (en) | 2008-11-21 | 2010-06-03 | Qualcomm Incorporated | Wireless position determination using adjusted round trip time measurements |
US9645225B2 (en) * | 2008-11-21 | 2017-05-09 | Qualcomm Incorporated | Network-centric determination of node processing delay |
US8892127B2 (en) | 2008-11-21 | 2014-11-18 | Qualcomm Incorporated | Wireless-based positioning adjustments using a motion sensor |
US9125153B2 (en) * | 2008-11-25 | 2015-09-01 | Qualcomm Incorporated | Method and apparatus for two-way ranging |
US8768344B2 (en) | 2008-12-22 | 2014-07-01 | Qualcomm Incorporated | Post-deployment calibration for wireless position determination |
US8750267B2 (en) * | 2009-01-05 | 2014-06-10 | Qualcomm Incorporated | Detection of falsified wireless access points |
JP2011166432A (en) * | 2010-02-09 | 2011-08-25 | Mitsubishi Electric Corp | Packet transfer device, communication system, and packet transfer method |
US8781492B2 (en) | 2010-04-30 | 2014-07-15 | Qualcomm Incorporated | Device for round trip time measurements |
US8718656B2 (en) * | 2011-03-30 | 2014-05-06 | Fujitsu Limited | Method and system for evaluating a wireless service network |
US9369171B2 (en) * | 2013-04-19 | 2016-06-14 | Key2mobile LLC | Multi-standard in building mobile radio access network |
CN104902451B (en) * | 2014-03-06 | 2018-07-24 | 鼎桥通信技术有限公司 | The signaling message transmission method and IUB interfaces of IUB interfaces |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020089958A1 (en) * | 1997-10-14 | 2002-07-11 | Peretz Feder | Point-to-point protocol encapsulation in ethernet frame |
US20030185190A1 (en) * | 2002-03-26 | 2003-10-02 | Interdigital Technology Corporation | TDD-RLAN wireless telecommunication system with RAN IP gateway and methods |
US20040199660A1 (en) * | 2003-02-14 | 2004-10-07 | Nokia Corporation | Method of multiplexing compressed and uncompressed internet protocol packets |
US20040252660A1 (en) * | 1998-03-31 | 2004-12-16 | Kalle Ahmavaara | Method for controlling connections to a mobile station |
US20050021616A1 (en) * | 2001-07-03 | 2005-01-27 | Jarno Rajahalme | Method for managing sessions between network parties, methods, network element and terminal for managing calls |
US20060193295A1 (en) * | 2004-11-19 | 2006-08-31 | White Patrick E | Multi-access terminal with capability for simultaneous connectivity to multiple communication channels |
US20090003263A1 (en) * | 2007-06-26 | 2009-01-01 | Motorola, Inc. | Network for a cellular communication system and a method of operation therefor |
US7551920B1 (en) * | 2003-09-18 | 2009-06-23 | Sprint Spectrum L.P. | Signal strength-based call forwarding for wireless phones |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FI105993B (en) * | 1997-08-20 | 2000-10-31 | Nokia Mobile Phones Ltd | Procedures and systems for controlling radio communication systems and radio network controllers |
US6246878B1 (en) * | 1997-11-26 | 2001-06-12 | Telefonaktiebolaget Lm Ericsson | Magnetoresistive device having a highly smooth metal reflective layer |
GB2389749B (en) * | 1999-05-28 | 2004-02-25 | Nec Corp | Mobile telecommunications system |
FI110738B (en) * | 2000-05-22 | 2003-03-14 | Nokia Corp | Data transmission in a packet switched radio system implementing a subscriber terminal location service |
FI20001544A (en) * | 2000-06-29 | 2001-12-30 | Nokia Networks Oy | Network support for abnormal terminal |
US6990089B2 (en) * | 2000-12-12 | 2006-01-24 | Telelec | Methods and systems for routing messages in a radio access network |
US20030216140A1 (en) * | 2002-05-17 | 2003-11-20 | Georg Chambert | Universal identification system for access points of wireless access networks |
US7885644B2 (en) * | 2002-10-18 | 2011-02-08 | Kineto Wireless, Inc. | Method and system of providing landline equivalent location information over an integrated communication system |
US20040198344A1 (en) * | 2003-01-14 | 2004-10-07 | Pitt Randall E. | Integrated wireless voice and data services using mobile switching centers |
US7340250B2 (en) * | 2003-05-22 | 2008-03-04 | Nokia Corporation | Method for choosing a network element of mobile telecommunication network |
JP4217544B2 (en) * | 2003-06-05 | 2009-02-04 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication system, control apparatus, and communication method |
GB2402845A (en) * | 2003-06-14 | 2004-12-15 | Agilent Technologies Inc | Service usage records for mobile data communications |
CN100546414C (en) * | 2004-02-27 | 2009-09-30 | 诺基亚西门子通信系统技术(北京)有限公司 | In a kind of mobile communication system to operation or the test data method and apparatus handling and analyze |
ATE370575T1 (en) * | 2004-03-08 | 2007-09-15 | Ericsson Telefon Ab L M | UNLICENSED RADIO ACCESS NETWORKS IN CELLULAR MOBILE NETWORKS |
US8103279B2 (en) * | 2004-04-21 | 2012-01-24 | Alcatel Lucent | Restrictive and preferential routing in a distributed mobile switching center environment with media gateway clusters |
AU2005279575B2 (en) * | 2004-08-29 | 2009-05-21 | Huawei Technologies Co., Ltd. | A method for implementing dual-homing |
JP4499526B2 (en) * | 2004-10-19 | 2010-07-07 | 富士通株式会社 | Data transmission path establishment system between mobile phone terminals |
KR100639239B1 (en) * | 2004-11-10 | 2006-10-26 | 엘지노텔 주식회사 | Method for processing of handover in media gateway |
JP2009510972A (en) * | 2005-10-04 | 2009-03-12 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Calling a radio access network with a pico base station |
KR100726184B1 (en) * | 2005-11-28 | 2007-06-11 | 한국전자통신연구원 | Method for discovering wireless network for inter-system handover, multi mode terminal unit and interlock service server thereof |
US8089938B2 (en) * | 2005-12-28 | 2012-01-03 | Alcatel Lucent | Method of synchronizing with an uplink channel and a method of determining a propagation delay in a wireless communications system |
CN101005633B (en) * | 2006-07-21 | 2010-07-21 | 华为技术有限公司 | Method and system for realizing mobile exchange central pool |
US20080089309A1 (en) * | 2006-10-17 | 2008-04-17 | Rejean Groleau | H-FDD scheduling in a wireless network |
US20080186927A1 (en) * | 2007-02-07 | 2008-08-07 | Mavenir Systems, Inc. | Switching within a communication network |
JP5074584B2 (en) * | 2007-06-22 | 2012-11-14 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Service area in CS domain service |
-
2008
- 2008-11-03 EP EP08844739.6A patent/EP2208318B1/en active Active
- 2008-11-03 WO PCT/US2008/012446 patent/WO2009058401A1/en active Application Filing
- 2008-11-03 CN CN200880113834.6A patent/CN101836404B/en not_active Expired - Fee Related
- 2008-11-03 US US12/290,870 patent/US8638764B2/en active Active
-
2014
- 2014-01-23 US US14/162,379 patent/US20140198754A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020089958A1 (en) * | 1997-10-14 | 2002-07-11 | Peretz Feder | Point-to-point protocol encapsulation in ethernet frame |
US20040252660A1 (en) * | 1998-03-31 | 2004-12-16 | Kalle Ahmavaara | Method for controlling connections to a mobile station |
US20050021616A1 (en) * | 2001-07-03 | 2005-01-27 | Jarno Rajahalme | Method for managing sessions between network parties, methods, network element and terminal for managing calls |
US20030185190A1 (en) * | 2002-03-26 | 2003-10-02 | Interdigital Technology Corporation | TDD-RLAN wireless telecommunication system with RAN IP gateway and methods |
US20040199660A1 (en) * | 2003-02-14 | 2004-10-07 | Nokia Corporation | Method of multiplexing compressed and uncompressed internet protocol packets |
US7551920B1 (en) * | 2003-09-18 | 2009-06-23 | Sprint Spectrum L.P. | Signal strength-based call forwarding for wireless phones |
US20060193295A1 (en) * | 2004-11-19 | 2006-08-31 | White Patrick E | Multi-access terminal with capability for simultaneous connectivity to multiple communication channels |
US20090003263A1 (en) * | 2007-06-26 | 2009-01-01 | Motorola, Inc. | Network for a cellular communication system and a method of operation therefor |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017142588A1 (en) * | 2016-02-15 | 2017-08-24 | Spidercloud Wireless, Inc. | Ue-measurement assisted closed loop learning approach for real-time optimization of system metrics |
Also Published As
Publication number | Publication date |
---|---|
WO2009058401A1 (en) | 2009-05-07 |
EP2208318A4 (en) | 2014-04-09 |
US20090135797A1 (en) | 2009-05-28 |
EP2208318A1 (en) | 2010-07-21 |
CN101836404B (en) | 2016-06-01 |
CN101836404A (en) | 2010-09-15 |
EP2208318B1 (en) | 2019-02-20 |
US8638764B2 (en) | 2014-01-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8638764B2 (en) | Mobile telecommunications architecture | |
US8750271B2 (en) | Adaptation of portable base stations into cellular networks | |
US9215098B2 (en) | System and method to control wireless communications | |
US8688111B2 (en) | System, method, and device for providing communications using a distributed mobile architecture | |
US7840230B2 (en) | Communications using a distributed mobile architecture | |
US20070202847A1 (en) | System, method, and device for providing communications using a distributed mobile architecture | |
US20040219914A1 (en) | Convergent wireless communication system | |
US6711417B1 (en) | Interface using an ISH and a service manager | |
US9955405B1 (en) | Base station subsystem multiplexer with support for local switching | |
CN102726101B (en) | Method and device for soft handoff | |
EP1410664A1 (en) | Ip-based gsm and umts system | |
JP4436240B2 (en) | Using mobile control channels to roam across networks | |
US20070253351A1 (en) | Automatically Discovering Devices Of A Wimax Network System | |
JP3746040B2 (en) | Method and system for managing the connection of mobile elements to a network | |
US8953588B2 (en) | Mobile network with packet data network backhaul | |
CN101998519B (en) | Method and device for applying radio network subsystem application part (RNSAP) protocol to stream control transmission protocol (SCTP) connection | |
CN102388655B (en) | Base station controller (BSC), mobile switching center (MSC) and switch method for calling mode | |
WO2002098154A1 (en) | Connecting the bsc of a gsm base station subsystem to an rnc of a umts system to achieve support for the iu interface in the gsm base station subsystem | |
KR20090043226A (en) | Method, device and system providing gprs using intergrated bts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RADIOFRAME NETWORKS, INC.;REEL/FRAME:035718/0028 Effective date: 20090715 Owner name: RADIOFRAME NETWORKS, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, YAN;TARIQ, AHMED;SIGNING DATES FROM 20090110 TO 20090113;REEL/FRAME:035718/0021 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001 Effective date: 20170119 |