RU2476022C2 - Concentrator for multiplexing of access point connections with wireless network - Google Patents

Abstract

FIELD: radio engineering, communication.

SUBSTANCE: method is carried out by means of using a component-concentrator establishing a single connection of transport level with MME together with multiple connections of applied level along a single connection of transport level for each of many subordinate points of access and/or related mobile devices. Subordinate points of access and/or mobile devices may provide identifiers to the component-concentrator, which may use identifiers to track transfers with MME. MME may send paging messages, and the component-concentrator may detect subordinate points of access related to paging messages, on the basis of a stored association with a tracking identifier in a paging message.

EFFECT: multiplexing of access point connections to objects of mobility control.

18 cl, 21 dwg

Description

§119 Priority Claim

[0001] This Patent Application claims the priority of Provisional Application No. 61 / 074,978 entitled “SYSTEMS AND METHODS TO REDUCE ASSOCIATIONS AND / OR PORTS REQUIRED AT A MOBILITY MANAGEMENT ENTITY (MME) TO SUPPORT A NUMBER OF eNBs / HeNBs IN WIRELESS NET” June 23, 2008, which is assigned to the assignee of this application and thus expressly incorporated into this description by reference, Provisional Application No. 61 / 079,393, entitled “SYSTEMS AND METHODS TO REDUCE ASSOCIATIONS / PORTS AND MULTIPLEX CONNECTIONS BETWEEN eNBs / HeNBs / RELAYS IN WIRESS SYSTEMS ”, filed July 9, 2008, which is transferred to the assignee and thus explicitly included in toyaschee herein by reference, № Provisional Application 61 / 087.145, entitled "CONCENTRATOR / DISTRIBUTOR FOR A CONTROL PLANE TO HOME BASE STATIONS", filed on August 7, 2008, which is assigned to the assignee and hereby expressly incorporated herein by reference.

FIELD OF THE INVENTION

[0002] The following description generally relates to wireless communications and, more specifically, to control plane communications with upstream network components and between access points.

State of the art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as: speech, data, etc. Typical wireless communication systems can be multiple access systems configured to support communication for multiple users by sharing available system resources (eg, bandwidth, transmit power, ...). Examples of such multiple access systems may include: code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems ) and the like. In addition, systems can meet specifications such as a third-generation partnership project (3GPP), 3GPP long-term development project (LTE), mobile broadband access (UMB) and / or multi-carrier wireless specifications such as Evolved Optimized Data Transfer ( EV-DO), one or more versions thereof, etc.

[0004] Generally, multiple access wireless communication systems can simultaneously support communication for multiple mobile devices. Each mobile device can communicate with one or more access points (for example, base stations) through transmissions on the forward and reverse links. A forward communication line (or downlink) refers to a communication line from access points to mobile devices, and a reverse communication line (or uplink) refers to a communication line from mobile devices to access points. Additionally, communication between mobile devices and access points can be created through single-input, single-output (SISO) systems, multi-input, single-output (MISO) systems, multi-input, multi-output (MIMO) systems, etc. In addition, mobile devices can communicate with other mobile devices in peer-to-peer wireless network configurations.

[0005] Access points may communicate with additional upstream wireless network components to facilitate mobile device access to the wireless network. In some configurations, access points may create a connection with mobility management (MME) entities to provide session and mobility management in a wireless network. MMEs can additionally communicate with additional upstream network components to authenticate / allow mobile devices to communicate over the network and / or to facilitate transmission / reception of data over the network.

[0006] Small-scale access points, such as femtocell access points, picocell access points, relay nodes, etc., have been introduced into conventional wireless networks, enabling heterogeneous unregulated deployment of new access points. These small-scale access points likewise create an MME connection to provide session and mobility management in wireless networks. However, MMEs can be limited in terms of the number of supported connections, both at the transport and application levels. Similarly, some access points may support other small-scale access points, giving them access to the MME, and similarly, may have limitations on the number of simultaneously supported connections, especially when, for example, the supporting access point is a pico cell or femto cell access point.

SUMMARY OF THE INVENTION

[0007] The following is a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This brief description is not an extensive overview of all aspects considered, and as it is not intended to indicate key or critical elements of all aspects, it is not intended to outline the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that is presented later.

[0008] In accordance with one or more aspects and their respective disclosures, various aspects are described with respect to facilitating multiplexing access point connections to mobility management entities (MMEs) or other access points using a hub component. A hub component can connect to downstream access points and one or more MMEs or upstream access points. In this regard, a hub component can support many downstream access point connections through a single MME or upstream access point connection. In one example, a hub component may associate downstream access points with an MME or an upstream access point (or a combination thereof) and forward data received from downstream access points to an MME or upstream access points.

[0009] In another example, for transmissions of a particular mobile device, the hub component can, for example, create an identifier for a mobile device that is locally unique within the hub component (for example, based on the mobile device’s own identifier and the identifier associated with the downstream point access). The hub component can replace in packets related to this mobile device, the identifier of the mobile device with a new identifier before forwarding the MME packets or to a higher access point. Therefore, when a hub component receives a response from an MME or an upstream access point, the hub component can, from the identifier, determine the appropriate downstream access point, replace the identifier in the response with the originally received identifier of the mobile device and forward the response to the downstream access point for distribution to the appropriate mobile device . In yet another example, a hub component may associate downstream access points with a tracking zone, which may be a group of downstream points that are close to each other. In this regard, the hub component can broadcast data received from the MME to the snoop to avoid complex routing support in the MME.

[0010] In accordance with related aspects, a method is provided that includes receiving a paging call from an MME comprising a tracking area identifier, and determining one or more access points associated with the tracking area identifier based at least in part stored correspondence of access points with tracking zone identifiers. The method also includes transmitting a paging call to one or more access points.

[0011] Another aspect relates to a wireless communication device. A wireless communication device may include at least one processor configured to receive a paging call from an MME containing a tracking area identifier. At least one processor is further configured to distinguish one or more access points associated with a tracking area identifier based at least in part on a stored association of access points with tracking area identifiers and transmit a paging call to one or more access points . The wireless communication device also comprises a memory coupled to at least one processor.

[0012] Another other aspect relates to a device that includes means for receiving a paging call from an MME comprising a tracking area identifier, and means for determining one or more access points associated with the tracking area identifier based on at least partially stored correspondence of access points with tracking zone identifiers. The device further includes means for transmitting a paging to one or more access points.

[0013] Another aspect relates to a computer program product, which may have a computer-readable storage medium including code for instructing at least one computer to receive a paging call from an MME containing a tracking area identifier. The computer-readable storage medium may also comprise code instructing the at least one computer to determine one or more access points associated with the tracking area identifier based, at least in part, on the stored correspondence of the access points with the tracking area identifiers. Moreover, a computer-readable storage medium may comprise code instructing at least one computer to transmit a paging call to one or more access points.

[0014] Moreover, an additional aspect relates to a device. The device may include an upstream communication component that receives a paging call from an MME containing a tracking area identifier. The device further includes a paging component that determines (detects) one or more access points associated with the tracking area identifier based, at least in part, on the stored correspondence of the access points with tracking area identifiers, and a downstream communication component transmitting the search Calling one or more access points.

[0015] To the accomplishment of the foregoing and related objects, one or more aspects comprise the features fully described below and specifically set forth in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of one or more aspects. However, these features are merely some of the various ways in which the principles of various aspects can be used, and this description is intended to include all such aspects and their equivalents.

LIST OF DRAWINGS FIGURES

[0016] FIG. 1 is an illustration of an example wireless communication system that facilitates multiplexing wireless network transmissions.

[0017] FIG. 2 is an illustration of an example wireless communication system that facilitates communicating multiple access points with an upstream network component.

[0018] FIG. 3 is an illustration of an example wireless communication system that facilitates the process of identifying access points related to communicating with a superior network component.

[0019] FIG. 4 is an illustration of an example wireless communication system that facilitates identification of an access point.

[0020] FIG. 5 is an illustration of an example wireless network for providing multiplexed communication between an access point and a mobility management entity (MME).

[0021] FIG. 6 is an illustration of an example wireless network for providing multiplexed communication between an access point and an upstream access point.

[0022] FIG. 7 is an illustration of an example method that transmits packets to an access point based on an identifier in packets.

[0023] FIG. 8 is an illustration of an example method that replaces identifiers in packets with identifiers of mobile devices and forwards packets to associated access points.

[0024] FIG. 9 is an illustration of an example method that transmits uplink packets to corresponding upstream network components.

[0025] FIG. 10 is an illustration of an example method that replaces identifiers in packets with identifiers of mobile devices and forwards packets to the corresponding upstream network components.

[0026] FIG. 11 is an illustration of an example method that implements paging in a multiplexing environment to communicate with an access point.

[0027] FIG. 12 is an illustration of an example method that receives and inserts identifiers related to access points when communicating with a hub component.

[0028] FIG. 13 is an illustration of an example method that transmits unique identifiers in messages to upstream network components.

[0029] FIG. 14 is an illustration of a wireless communication system in accordance with various aspects set forth herein.

[0030] FIG. 15 is an illustration of a wireless communication network in accordance with aspects described herein.

[0031] FIG. 16 is an illustration of an example wireless network environment that can be used with the various systems and methods described herein.

[0032] FIG. 17 is an illustration of an example system that facilitates multiplexing communication of an access point with an MME.

[0033] FIG. 18 is an illustration of an example system that facilitates multiplexing communication of an access point with a higher access point.

[0034] FIG. 19 is an illustration of an example system that provides paging functionality with multiplexed access point communications.

[0035] FIG. 20 is an illustration of an example system that receives and uses access point identifiers when communicating with associated access points.

[0036] FIG. 21 is an illustration of an example system that provides identifiers in messages to upstream network components.

DETAILED DESCRIPTION

[0037] Hereinafter, various aspects are described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is obvious that such aspect (s) can (gut) be implemented (s) in practice without these specific details.

[0038] Used in this application, the concepts of “component”, “module”, “system” and the like are intended to include a computer related object, such as, but not limited to, hardware, firmware, a combination of hardware and software, software or runtime software. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a control thread, a program, and / or a computer. By way of illustration, both an executable application on a computing device and a computing device can be a component. One or more components may reside within a process and / or control flow, and the component may be localized on one computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable storage media having various data structures stored thereon. Components can communicate through local and / or remote processes, such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system and / or network, such like the Internet, with other systems through a signal.

[0039] In addition, various aspects are described herein with reference to a terminal, which may be a wired terminal or a wireless terminal. A terminal may also be referred to as a system, device, subscriber module, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user device, or user equipment (UE ) A wireless terminal may be a cell phone, satellite phone, cordless phone, Session Initiation Protocol (SIP) telephone, Wireless Local Area Station (WLL) station, personal digital assistant (PDA), portable device with wireless capabilities, a computing device or other device processing connected to a wireless modem. Moreover, various aspects are described herein in relation to a base station. The base station may be used to communicate with the wireless terminal (s) and may also be referred to as an access point, Node B, or in accordance with some other terminology.

[0040] Moreover, the term “or” is intended to mean an inclusive “or” instead of an exclusive “or”. That is, unless otherwise indicated, or out of context, the phrase “X uses A and B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X uses A and B” will be satisfied with any of the following cases: X uses A; X uses B; or X uses both A and B. In addition, the singular as a whole used in this application and the accompanying claims should be construed as meaning “one or more” unless otherwise indicated or it is not clear from the context that singular is indicated.

[0041] The methods described herein can be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The concepts of “system” and “network” are often used interchangeably. A CDMA system may implement radio access technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA technology includes Broadband CDMA (WCDMA) and other CDMA options. Additionally, cdma2000 technology covers IS-2000, IS-95, and IS-856 standards. A TDMA system may implement a radio access technology such as Global System for Mobile Object Communications (GSM). An OFDMA system can implement radio access technology such as Advanced UTRA (E-UTRA), Ultra Broadband Mobile Access (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. .d. UTRA and E-UTRA technologies are part of the Universal Mobile Communications System (UMTS). 3GPP Long Term Evolution (LTE) Project is a version of UMTS that uses E-UTRA, which in turn uses OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). In addition, cdma2000 and UMB are described in documents from an organization called the Third Generation Partnership Project 2 (3GPP2). Additionally, such wireless communication systems may further include: peer-to-peer (eg, mobile to mobile) ad hoc networks often using unpaired unlicensed spectra; wireless local area network (LAN) according to the standard 802.XX, BLUETOOTH and any other technologies of wireless communication of short or long range.

[0042] Various aspects or features will be presented in terms of systems, which may include a number of devices, components, modules, and the like. It should be understood and taken into account that various systems may include additional devices, components, modules, etc. and / or may not include all devices, components, modules, etc., considered in relation to the drawings. A combination of these approaches may also be used.

[0043] Turning to FIG. 1, a communication system 100 is illustrated that facilitates multiplexing the connections of multiple access points to the connection of a single mobility management entity (MME) or a single upstream access point. A hub component 102 is provided that connects to the MME or access point 104, as well as to the downstream access points 106, 108, and 110, to facilitate communication between them. The MME or access point 104 may be an MME or access point that communicate with the MME. In addition, although not shown, the hub component 102 can connect to multiple MMEs or to upstream access points, allowing access points 106, 108 and 110 (or other downstream access points) to communicate with one or more MMEs or upstream access points. In addition, as described hereinafter, the hub component 102 may be transparent to the MME or access point 104, as well as to access points 106, 108, and 110.

[0044] In accordance with one example, a hub component 102 may create a transport layer connection (eg, via a flow control protocol (SCTP)) along with a plurality of related application layer connections (eg, using the S1 application protocol (S1-AP , X2, etc.)) for each access point 106, 108 and 110 with an MME or access point 104. In addition, each of the access points 106, 108, and 110 can create a transport layer connection and corresponding application layer connections with the hub component 102. The hub component 102 can receive packets from the access points 106, 108 and 110 at the transport and application level and forward packets to the MME or access point 104 along with the identifier of the access point 106, 108 or 110 over the corresponding application layer connection created over a single transport layer connection. In addition, the MME or access point 104 may indicate the identifiers of the access points in packets transmitted to the hub component 102, and the hub component may forward the packets to a suitable access point 106, 108 or 110.

[0045] In another example, the hub component 102 may communicate with a plurality of upstream MMEs or access points (eg, MME or access point 104 and others). In this example, the hub component 102 may support routing information such as a routing table related to access points 106, 108, 110 and a plurality of upstream MMEs or access points. Moreover, in this example, access points 106, 108, and 110 can connect to multiple MMEs, and the hub component 102 can maintain routing information for each MME and forward packets from access points 106, 108, or 110 to a suitable MME using routing information.

[0046] In addition, the hub component 102 can act as an MME, in some cases processing communications from an access point to an access point, such as handover commands, a reset message, and / or the like. For example, a handover command may be received with respect to access points 106 and 108. When access points 106 and 108 are associated with the same upstream MME or access point (eg, MME or access point 104), in some cases it is not necessary to notify the upstream MME or access point of the handover. In this example, the hub component 102 may facilitate handoff from the access point 106 to the access point 108 (or vice versa), as indicated in the handover command. However, in another example, the hub component 102 can replace the access point identifiers in the handover command with its own identifier created using the MME or access point 104, forcing the MME or access point 104 to act as if a handover between access point and to her. However, where the access points involved in the handover command communicate with disparate MMEs, the hub component 102 may forward the command to a superior MME or access point related to suitable access points to facilitate handover.

[0047] Similarly, the hub component 102 can act as an MME in processing initialization messages sent from access points 106, 108, or 110. In this example, the hub component 102 may send a reset message to the MME or access point 104 serving the access point 106, 108, or 100, as well as essentially all access points served by the MME or access point 104. In addition or as an alternative, the hub component 102 can transmit the reset message to the initial state, in fact, to all mobile devices served by the reset point access point 106, 108 or 110, as described hereinafter. Moreover, the hub component 102 may transmit the reset message to the MME or access point 104, separately for all mobile devices served by one or more of the reset points 106, 108, or 110, as described hereinafter.

[0048] In addition or as an example, the hub component 102 may create an application layer connection with an MME or access point 104 for each mobile device (not shown) connected to a predetermined access point 106, 108, or 110. In this example, the hub component 102 may receive uplink packets from the access point 106, 108 or 110 related to the connected mobile device, and may generate an identifier for the mobile device that is unique within the hub component 102. For example, the identifier may include the identifier of the mobile device determined from the package (for example, or previously performed registration) along with the identifier of the associated access point 106, 108 or 110. The hub component 102 may replace in the received packet the identifier of the mobile device with a locally unique identifier and transmit the packet to the MME or access point 104.

[0049] The downlink packets received from the MME or the access point 104 may include a unique identifier used in the uplink packets, allowing the hub component 102 to identify the associated mobile device and the serving access point. In one example, the hub component 102 may determine the access point serving the mobile device based on the state information stored in relation to the unique identifier. In another example, the hub component 102 may determine a serving access point based on information stored in or indicated by a unique identifier. In either case, the hub component may replace the unique identifier in the downlink packet with a mobile device identifier received earlier from the serving access point and may forward the packet to the serving access point for transmission to a suitable mobile device. In another example, the hub component 102 may determine information of a serving access point in a downlink packet and forward the packet to a serving access point without changing / changing identifiers in the packet for transmission to a suitable mobile device.

[0050] In addition, the hub component 102 may implement a paging call for the tracking zones defined by access points 106, 108, and 110. For example, access points 106, 108, and 110 may indicate tracking zones when creating a connection with a hub component 102 (and / or a hub component 102 may otherwise adopt or define associated tracking zones). In the case where the hub component 102 encounters a new tracking area from a connecting access point, it can forward the tracking area information to the MME or access point 104 in a configuration update message. The MME or access point 104 may utilize a paging call by transmitting to the concentrator component 102 paging calls containing a tracking identifier. The hub component 102 may subsequently transmit the paging call to essentially all access points associated with the tracking area, allowing the access points to perform the paging function of suitable mobile devices identified in the paging call, in one example.

[0051] Turning now to FIG. 2, an example of a wireless communication system 200 is illustrated that facilitates maintaining the connections of multiple access points to a given MME or upstream access point. A hub component 102 is provided that, as described, can connect to a plurality of access points 106, 108 and 110, facilitating communication with one or more MMEs 202 or with one or more upstream access points 204. The upstream access points 204 can connect to the MME 202 or other upstream network components, for example, facilitating communication, however, for access points 106, 108 and 110 through the hub component 102. In addition, mobile devices 206 and 208 can communicate with access point 106 to access the wireless network. It should be appreciated that in this way more mobile devices, for example, can communicate with the access point 106 and / or one or more upstream access points 108 or 110.

[0052] The hub component 102 may include an upstream connection component 210 that manages one or more transport layer connections and a plurality of application layer connections to an MME or an upstream access point, downstream connection component 212 that controls the transport and application layer with a set of access points, component 214 routing access points that supports status information for a set of access points associated with MM or another superior access point, a mobile device routing component 216 that supports status information for a plurality of mobile devices connected to one or more of a plurality of access points, a message between access points component 218 that processes messages or packets transmitted between access points connected with the concentrate component 102, and the paging component 220, which sends paging for mobile devices to serving access points based on the relative Tracking area

[0053] According to an example, the parent component 210 can create a connection to the MME 202 and / or access point 204. For example, the parent component 210, in one example, can create an SCTP association with the MME and / or access point 204, allowing a number of connections or application level threads (e.g., S1-AP, X2, etc.). During connection creation, for example, the parent component 210 can receive a unique identifier MME 202 (e.g., a global unique identifier MME (GUMMEI)) or access points 204 (e.g., a global eNB identifier (EGI)) for later use in identification packets sent from them. It should be understood that the use of such identifiers can be useful when the parent connection component 210 supports multiple parent connections to different MMEs or access points.

[0054] In addition, for example, downstream connection component 212 can create connections to access points 106, 108 and 110 upon receipt of a corresponding access request to the hub component 102 or to the MME 202 or upstream access point 204 (for example, as described , the hub component may be transparent to access points). For example, points 106, 108, and 110 may establish SCTP association with a downstream connection component 212 for which the hub component 102 does not take any action with respect to the MME 202 or the upstream access point 204. The downstream connection component 212, in one example, can transmit the identifier MME 202 (e.g., GUMMEI) or upstream access point (e.g., EGI) 204 to access points 106, 108 and 110, as if the access points had established a connection directly to the MME 202 or a higher access point 204. Subsequently, the access points 106, 108, and 110 may send an application layer initialization message (eg, S1-AP or X2 message) received by the downstream connection component 212 to facilitate the connection to the hub component 102. The upstream connection component 210 may forward the message S1-AP / X2 to the MME 202 and / or a higher access point; in one example, this may be based on information in the message, such as identified in the message MME or a superior access point. MME 202 or upstream access point 204 can establish an application layer connection over an SCTP connection with upstream connection component 210. Therefore, for example, if the connection between the access points 106, 108 or 110 and the downstream connection component 212 fails (for example, at the application or transport level), the downstream connection component 212 can close the associated application level connection with the MME 202 or higher access point 204.

[0055] Moreover, as described, the hub component 102 may connect to a plurality of MMEs or upstream access points. In this example, the hub component 102 can open access to various MMEs or upstream access points, allowing downstream access points, such as access points 106, 108, and 110, to select the desired MME or upstream access point. Information regarding the selected MMEs or superior access points may be stored in the routing table in the routing component 214 of the access points, for example. In addition, one or more downstream access points can connect to multiple MMEs or upstream access points, in which case the downstream access point can negotiate the connection through the hub component 102 using a different IP or other address for each connection. Access point routing component 214 may store multiple associations, as described further below, based on IP or other address and other information.

[0056] In addition, the access point routing component 214 may store an association between an access point 106, 108 or 110 and a suitable MME or access point, such as an MME 202 or an access point 204. An association can be stored, with GUMMEI for MME 202 or EGI for the upstream access point 204 received by the parent connection component 210 (and / or indicated in the access point initialization request) and the identifier associated with the appropriate access point 106, 108 or 110 that can be received by the downstream connection component 212 mi in the request to set the transport layer and / or application layer. This may be an EGI, as described, which locally identifies the access point 106, 108 or 110. In addition, access point routing component 214 can associate an access point identifier with an IP address of an access point. In one example, the downstream connection component 212 may receive packets from access points 106, 108, and 110, which include an access point identifier, for example, in each packet, and the access point routing component 214 can determine the destination MME or upstream access point based on the information in the packet and / or based on the association between the access point identifier or IP address and the MME identifier stored in the access point routing component 214. In any case, the access point routing component 214 may forward the packet to the downstream connection component 210 for transmission to a suitable MME or upstream access point, for example.

[0057] Upon receiving packets from the MME 202 or the access point 204, the parent connection component 210 may request the access point routing component 214 to determine one or more suitable access points to receive the packets. In one example, the parent connection component 210 may obtain an identifier of an MME or an upstream access point related to the packet and / or an access point identifier related to a downstream access point (such as an EGI, as described below) that locally identifies the access point for receiving packets. In one example, the identifier of the downstream access point may be determined based on another identifier in the downlink packet as received by the MME 202 or access point 204, and an entry in the routing table of the access point routing component 214 that associates the other identifier with the identifier of the access point received in installation time. The downstream connection component 212 may forward packets to a suitable access point based on the identifier. In the case where the downstream access point is associated with a plurality of MMEs or upstream access points, the downstream connection component 212 may further forward packets to the downstream access point based on the ID of the MME or upstream access point. Therefore, for example, a downstream access point, such as access points 106, 108, or 110, can initialize multiple transport and / or application layer connections to the downstream connection component 212 — one or more for each MME connection or upstream access point. In this regard, the access point routing component 214 can determine which connection to forward packets to the downstream access point based on the MME identifier or upstream access point and downstream access point identifier.

[0058] In another example, access point 106 may provide network access to mobile devices 206 and 208. In this regard, downstream component 212 may receive packets of a specific mobile device from access point 106. Upon receipt of the source packet, the parent connection component 210 can create an application layer connection on the transport layer connection to the MME 202 or the parent access point 204 for the mobile device 206 or 208. In addition, the mobile device routing component 216 can retrieve an identifier related to the device 206 or 208, and / or an identifier relating to access point 106. In one example, a mobile device identifier may be assigned by an access point 106 indicated in an uplink packet from a mobile device 206 or 208 and / or the like. The mobile device routing component 216 can generate a unique identifier related to the identifier of the access point 106 and the mobile device 206 or 208 - of course the unique identifier can contain both identifiers - and replace the identifier in the received packet with a unique identifier. Then, the parent connection component 210 may transmit the packet to a suitable MME 202 or parent access point 204 using the created application layer connection. Similarly, the desired MME or upstream access point may be indicated in a packet from the access point 106, in one example, and / or the parent connection component 210 may transmit the MME packet or upstream access point previously associated with the access point 106.

[0059] In addition, the parent connection component 210 may receive downlink packets from the MME 202 or the parent access point 204 related to mobile devices 206 and 208 or other mobile devices. The mobile device routing component 216 can determine the access point and the attached mobile device to which the downlink packets belong based on the unique identifier of the mobile device in the packet. For example, in the case when it is stored as an association (for example, added or inserted into the routing table), the mobile device routing component 216 may map a unique identifier to an identifier of a mobile device, such as for a mobile device 206 or 208, and an identifier of an associated access point, such as for access point 106. In another example, where the unique identifier is composed of the identifiers of the mobile device and the access point, the mobile device routing component 216 may recognize the identifiers from the unique identifier. In any case, the mobile device routing component 216 may further replace the unique identifier in the packet with a specific identifier of the mobile device, and the downstream connection component 212 may forward the packet to a suitable access point based on the identifier of the access point.

[0060] In yet another example, the message component 218 between the access points may perform functions similar to those performed by the MME when transmitting messages between access points served by the hub component 102. For example, in the case where two access points, such as the access point 106 and 108 associated with the same MME 202 or the superior access point 204, the message component 218 between the access points can facilitate transfers between the access points 106 and 108. In one example, the access point 106 may transmit a handover or cell reselection command that is received by the downstream connection component 212 to facilitate handoff from the mobile device 206. The downstream connection component 212 can detect the downlink command and determine the starting point 106 access and target access point 108. If the access points 106 and 108 are associated with the same MME or a higher access point that can be determined, as described, by the access point routing component 214, then the message component 218 between the access points can send the handover command to the access point 108 through component 212 connections to children. Therefore, it is not required to involve MME or a higher access point in the handover; however, it should be appreciated that the hub component 102 may notify the MME or a higher access point (eg, MME 202 or access point 204) of the handover, in the example.

[0061] However, in another example, in a handover command, a message component between access points can replace the identifiers of the source access point and the target access point with the identifier of the hub component 102 and send the command to the appropriate MME or higher access point. In this regard, an MME (e.g., MME 202) or a superior access point (e.g., access point 204) can consider the hub component 102 as if it were handing off to itself, instructing the hub component 102 to forward the handover information from / to suitable (them) access points (cams) 106 and 108. In another example, the message component 218 between the access points may suitably control the initial reset messages received from the access points 106, 108, or 110 through the downstream connection component 212. For example, downstream connection component 212 may receive a reset command from access point 106 and message component 218 between access points, in one example, may forward a message to associated MMEs and / or upstream access points, as indicated by access point routing component 214 using component 210 connections to parent objects. In addition, the message component 218 between the access points can relay the reset message to the initial state, in fact, to all access points associated with the same MME or upstream access point, as determined by the access point routing component 214. Moreover, the downstream connection component 212, in one example, can send associated reset messages to mobile devices served by the access point, as indicated in the routing component 216 by the mobile devices. Alternatively, for example, downstream connection component 212 may receive a reset command from access point 106, and mobile device routing component 216, in one example, may send a reset message to each UE served by point 106 access to associated MME 202 and / or parent access points 204.

[0062] It should be appreciated that the MME 202 or the upstream access point 204 can also send a reset message that can be received by the upstream connection component 210. Accordingly, the access point routing component 214 can notify the associated access points by sending a reset message to the initial state using the downstream connection component 212, for example. In yet another example, the paging component 220 may transmit paging messages related to served mobile devices, access points 106, 108, or 110 based on their associated tracking zones. In this example, when creating a connection with the hub component 102, access points 106, 108, and 110 may transmit tracking zone information in connection creation requests. The paging component 220 may store tracking area information associated with access points 106, 108, and 110. If a new tracking zone is determined (for example, one that is not stored with information in the paging component 220), the paging component 220 may send a configuration update message to associated MMEs, such as MME 202, or upstream access points, such as access point 204 . In this regard, the MME 202 and / or the upstream access point 204 can send paging messages to essentially all mobile devices in the tracking area by sending a message to the upstream connection component 210. The paging component 220 may forward the message to access points based on the tracking area indicated in the message and access points related to the tracking area as stored in the paging component 220, for example. It should be appreciated that the paging component 220 can also additionally or alternatively implement execution without storing the state in which it forwards the received paging message to essentially all access points connected to the hub component 102, and the access points can determine whether to apply the message based on the tracking identifier stored in the message.

[0063] Turning to FIG. 3, an example wireless communication system 300 is illustrated that facilitates providing multiple access points with communication with an MME or a superior access point over a single transport layer connection. A hub component 102 is provided that creates a transport layer connection to an MME or upstream access point 104 to facilitate communication with them, and establishes transport and application layer connections with a plurality of access points 106, 108 and 110. As described, the hub component 102 creates application layer connections with the MME or upstream access point 104 for access points 106, 108 and 110 to facilitate access to the wireless network. In addition, the hub component 102, as described, can support multiple MMEs or upstream access points. Access point 106 may create a connection to a hub component 102 and provide an identifier for use in subsequent communication with an MME or access point 104, as described.

[0064] An MME or access point 104 may comprise: an uplink receive component 302 that can receive requests from a hub component 102 (for example, on behalf of an access point 106, 108, or 110, and / or a mobile device with them communication); access point identifier component 304, which determines an identifier associated with uplink packets from the hub component 102; a core network communication component 306 that can transmit and receive data to / from a core wireless network; and a downlink transmission component 308 that can transmit data to a hub component 102 for transmission to one or more access points.

[0065] According to an example, the hub component 102 may establish a connection to the MME or access point 104, taking the identifier associated with them, in one example. One or more access points 106, 108, and 110 may create a connection with a hub component 102 to ultimately access the MME or access point 104 as described, and the hub component 102 may establish an application layer connection with the MME or access point 104 for access points 106, 108 and 110. Subsequently, access points 106, 108 and 110 may transmit packets to the hub component 102 containing the identifier specified during installation. As described, this may be an access point identifier (eg, EGI), part of an identifier of a served mobile device, and / or the like. In addition, as described in one example, the hub component 102 may, in one example, replace the identifier with an identifier unique to the hub component 102, such as the association of the access point identifier with the identifier of the mobile device in which both are present.

[0066] In any case, the hub component 102 may send an uplink packet to the MME or access point 104, and the uplink receive component 302 may receive an uplink packet. The access point identifier component 304 may, for example, determine the identifier associated with the packet, and the core network communication component 306 may transmit a request to a core wireless network (not shown). It will be appreciated that the identifier may be included in the request or otherwise associated so that the communication component 306 with the core network may associate response packets with the identifier. Additionally, it should be appreciated that no request is required to receive packets in the communication component 306 of the core network (e.g., from the core wireless network) for transmission to one or more access points 106, 108, or 110. For example, the core network may send paging message packets to the core network communication component 306 for forwarding to access points 106, 108, or 110 without first receiving the request.

[0067] Upon receiving the downlink packet from the core network, the communication component 306 with the core network can determine the access point associated with the downlink packet. This can be done based on the identifier or context of the downlink packet, which may be the identifier or context sent in the corresponding uplink packet by the communication component 306 of the core network, as described. The downlink component 308 may associate a suitable access point identifier with a downlink packet if, for example, it differs from the identifier indicated in the downlink packet from the core network and can provide a response to the hub component 102. For example, the component The downlink transmission 308 can verify that, in fact, all packets transmitted to the hub component 102 have associated access point identifiers. As described, the hub component 102 can also replace the identifier in the packet, for example, where the packets relate to the mobile device served by the access point. The hub component 102 may provide a downlink packet to a suitable access point 106, 108 and / or 110 based on the identifier, as described previously.

[0068] The MME or access point 104 can support not only systematic direct connections of the transport layer from access points, but also the connection of the transport layer from the hub component 102. It should be appreciated that the connection of the transport layer from the hub component 102 may differ from conventional direct connections to access points in that the connection to the hub component 102 can support multiple application layer connections over a single connection or transport association a ram, as described.

[0069] Turning to FIG. 4, an example of a wireless communication system 400 is illustrated that multiplexes access point connections to an MME or an upstream access point over a single transport layer connection. System 400 includes a hub component 102 that can provide access to an MME or an upstream access point 104 for multiple access points, such as access point 106, as described. In particular, the access point 106 may associate an identifier during installation and for use in each subsequent transmission of the packet to the hub component 102. As described, this allows the hub component 102 to associate packets with the access point 106 when transmitting or receiving from the MME or point 104 access. In the case where the MME or the access point 104 sends downlink packets to the hub component 102, for example, in this regard, the identifier can be used in the same way to associate the downlink packets with the access point 106.

[0070] The access point 106 may include an identifier specification component 402 that can generate or otherwise obtain an identifier that will be used when transmitting uplink packets to the hub component 102, a connection request component 404 that creates a connection with the hub component 102 as described, the uplink transmission component 406, which can transmit the uplink packets to the hub component 102, the downlink reception component 408 which can receive downlink packets from a hub component 102 and a mobile device communication component 410 that can provide access to a wireless network to one or more mobile devices (not shown).

[0071] According to an example, a hub component 102, as described, can create a transport layer connection with an MME or access point 104. As described, for example, the hub component 102 may be transparent to the access point 106, so that the access point 106 functions as if it were connected directly to the MME or upstream access point 104. The identifier specification component 402 may generate or obtain an identifier related to the access point 106, for example, and the connection request component 404 may formulate an access request to the MME or the access point 104 indicating the identifier. Connection request component 404 can transmit an access request to hub component 102, which can store the identifier and / or association associated with the identifier as described, and establish an application layer connection with the MME or access point 104 related to access point 106.

[0072] The uplink transmission component 406 may provide uplink packets to the hub component 102 and may set an access point identifier from the identifier component 402 in each packet. As described, this allows the hub component 102 to identify the access point for subsequent transmission of the uplink packet to the corresponding MME or access point 104 and to identify any responses received from the MME or access point 104 related to the downlink packet. In an example, such a response may be received by the hub component 102 in a downlink packet. As described, the hub component 102 may determine the packet-related access point 106 and forward the downlink packet to the downlink receive component 408. The downlink receive component 408 can verify that the packet has been delivered properly based on a variety of factors, including: identifier used; whether the contents of the package are an acceptable or expected response to a previously created request; and / or the like.

[0073] In addition, the mobile device communication component 410 can provide wireless access to one or more mobile devices through the access point 106. In this example, the mobile device communication component 410 may receive uplink packets from the mobile device. The identifier specification component 402 may assign an identifier to a mobile device, for example, which is locally unique to access point 106. This assignment can occur, for example, when creating a connection with a mobile device. The uplink transmission component 406 may transmit the uplink packets to the hub component 102 along with the identifier assigned to the mobile device by the identifier specification component 402. In one example, an identifier for a mobile device may be received in an uplink packet from a mobile device, instead of being assigned as an identifier specification component 402. In any case, the identifier may be used in subsequent transmissions between the mobile device and the access point 106, as described.

[0074] In any case, the hub component 102 may, upon receipt of the packet, create a locally unique identifier based on the identifier of the access point and the mobile device and may use this unique identifier instead of the original identifier of the mobile device when communicating with the MME or access point 104, as described. The hub component 102 may also receive downlink packets from the MME or access point 104 related to the mobile device, and may forward these packets to the access point 106 (e.g., based on a locally unique identifier), replacing the locally unique identifier with the identifier of the mobile device, initially presented to the hub component 102. It should be appreciated that the hub component 102 can also use the access point identifier, if any, to forward these packets Downlink to a suitable access point. The downlink receive component 408 may determine the corresponding mobile device for the downlink packet based on the identifier, and the mobile device communication component 410 may forward the downlink packet to the mobile device, for example.

[0075] Now referring to FIG. 5, an example of a wireless communications network 500 is illustrated that uses a hub component to provide multiplexing for access points accessing the MME. The network 500 may include a mobile device 502 accessing the network from an eNB / home eNB (HeNB) 504, which may be referred to as a small-scale access point, such as a femtocell access point, a picocell access point, a relay node, etc., or, in one example, an access point of a macro cell. Access to the network can be carried out, in fact, in accordance with any specification, such as E-UTRA, UBM, WiMAX, etc. As described, the HeNB 504 may communicate with the hub component 102 using the S1-MME interface on behalf of the mobile device 502 or otherwise, and may accordingly provide the identifiers of the access point and / or mobile device to allow the hub component 102 to track communication with MME 104 using the S1-MME interface as described herein. MME 104, as described, can communicate with the core network.

[0076] The core network includes various other components. For example, the MME 104 may communicate with a serving General Packet Radio Service (GPRS) support node (SGSN) according to S3 specification to access the UTRA network 508 and / or the GSM / EDGE radio access network (GERAN) 510 (radio access network with support Technologies of the Global System for Communication with Mobile Objects (GSM) / Development of GSM with Increased Data Transfer Rates (EDGE). MME 104 may connect to a Home Subscriber Server (HSS) 512 according to specification 56a, for example, to obtain subscriber information.

[0077] In another example, the eNB / HeNB 504 may communicate with a serving gateway 514 (SGW) over an S1-U interface to access the Internet 518 and / or the IP Multimedia Subsystem 520 and / or other IP systems. In another example, the eNB / HeNB 504 may similarly connect through a hub component 102 that communicates with an MME or eNB / HeNB 104, as described. MME 104 can create a connection to SGW 514 via S11, via SGSN 506 using S4, and / or via UTRA 508 via S12. In any case, the SGW facilitates access to the network by communicating with the Gateway 516 (PGW) of the packet data network (PDN) via the S5 / S8 interface, and the PGW 516 can communicate directly with the Internet 518 or IMS 520 using the SGi interface or through a node 522 functions of charging policy and rules (PCRF) via the Gx interface. In the last example, PCRF 522 can communicate with the IMS 520 via the Rx interface.

[0078] Now, referring to FIG. 6, an example of a wireless communication network 600 is illustrated that utilizes a hub component to provide multiplexing for access points accessing a peer access point. Network 600 may include a mobile device 502 accessing the network from an eNB / HeNB 504, which may be referred to as a small-scale access point, such as a femtocell access point, a picocell access point, a relay node, etc., or a macro access point cells in one example. Access to the network can be carried out, in fact, in accordance with any specification, such as E-UTRA, UBM, WiMAX, etc. As described, the HeNB 504 may communicate with the hub component 102 using the X2 interface on behalf of the mobile device 502 or otherwise, and may accordingly provide the identifiers of the access point and / or mobile device to allow the hub component 102 to track communication with the eNB / HeNB 602 using the X2 interface as described herein; The eNB / HeNB 602, as described, can communicate with the MME 104 via an S1-MME interface, which can communicate with a core network.

[0079] The core network includes various other components. For example, the MME 104 may communicate with a General Packet Radio Service (GPRS) Serving Support Node (SGSN) according to S3 specification to access the UTRA network 508 and / or the GSM / EDGE radio access network 510 (GERAN). MME 104 may connect to a Home Subscriber Server (HSS) 512 according to specification 56a, for example, to obtain subscriber information.

[0080] In another example, the eNB / HeNB 504 may communicate with a serving gateway 514 (SGW) over an S1-U interface to access the Internet 518 and / or IP Multimedia Subsystem 520 and / or other IP systems. In another example, the eNB / HeNB 504 may similarly connect through a hub component 102 that communicates with the eNB / HeNB 602, as described. The eNB / HeNB 602 can connect to a connected MME 104, which can create a connection to the SGW 514 via the S11 interface, via the SGSN 506, using the S4 interface, and / or through the UTRA network 508 via the S12 interface. In any case, the SGW facilitates network access by communicating with the Packet Data Network (PDN) gateway 516 (PGW) via the S5 / S8 interface, and the PGW 516 can communicate directly with the Internet 518 or IMS 520 using the SGi interface, or through Node 522 tariff policy and rule functions (PCRF) over the Gx interface. In the last example, PCRF 522 can communicate with the IMS 520 via the Rx interface.

[0081] Referring to FIGS. 7-13, methods are described related to facilitating the multiplexing of transmissions between access points and upstream access points or MMEs. Although, in order to simplify the explanation, the methods are shown and described as series of actions, it should be understood and taken into account that the methods are not limited to the order of actions, since some actions, in accordance with one or more aspects, can occur in a different order and / or in parallel with actions other than those shown and described herein. For example, one skilled in the art should understand and take into account that methods can alternatively be presented as series of interchangeable states or events, such as in a state diagram. Moreover, in order to implement a method in accordance with one or more aspects, not all illustrated acts may be required.

[0082] Turning to FIG. 7, an example of a method 700 that facilitates packet routing between access points and upstream network components is illustrated. At 702, a downlink packet may be received from the upstream network component. In the example, the upstream network component may be an access point, MME, and / or the like. At 704, an access point related to a downlink packet may be determined based at least in part on an identifier. As described, the identifier can be locally unique, so that the identifier can be generated and provided to the parent network component for use in transmitting packets received in relation to the corresponding access point. In one example, a locally unique identifier may be stored in the correspondence table along with the received identifier so that the packet can be correctly associated with the access point. In an example, an identifier may refer to one of a plurality of access point connections and may be configured to identify one of the connections. Although a generated identifier may be used as described, it should be appreciated that in another example, a received identifier may be used. At step 706, a downlink packet may be transmitted to the access point.

[0083] Referring to FIG. 8, an example method 800 is shown that facilitates transmitting downlink packets to access points for reception by respective mobile devices. At 802, a downlink packet may be received from the upstream network component. The downlink packet, as described, may contain a locally unique identifier generated previously to identify packets related to the access point and the mobile device. At 804, an access point related to the downlink packet may be determined based at least in part on the identifier. This may be a locally unique identifier, as described, which is associated with the access point based on: matching the locally unique identifier with the identifier received from the access point; a locally unique identifier containing a received identifier; and / or the like. Similarly, at block 806, a mobile device related to the downlink packet based at least in part on the identifier can be determined. Therefore, for example, the match can match the locally unique identifier with the corresponding identifiers of the access point and the mobile device, or such a match can be determined from the locally unique identifier itself, as described. At 808, the identifier in the downlink packet can be replaced with a specific identifier of the mobile device, and at 810, the packet can be transmitted to the access point. This, for example, allows the access point to provide a packet corresponding to a mobile device, providing continuous multiplexing of packets related to mobile devices from access points to upstream network components.

[0084] Turning to FIG. 9, an example method 900 is illustrated that facilitates routing packets between upstream network components and one or more access points. At 902, an uplink packet is received from the access point. At 904, a superior network component associated with the access point is determined. This can be determined, for example, based on the correspondence of the access point to a superior network component, which can be initialized based on a previously made installation request. In another example, an uplink packet may indicate a superior network component. At 906, an uplink packet may be transmitted to the upstream network component, as described.

[0085] Turning to FIG. 10, an example of a method 1000 is shown that facilitates transmitting downlink packets with locally unique identifiers generated. At 1002, an uplink packet may be received from the access point. At 1004, a superior network component associated with the access point can be determined. This can be accomplished based on a previously received indication, correspondence, or routing storing access point identifiers and their superior network components and / or the like, as described. At 1006, a mobile device related to the uplink packet may be determined based at least in part on the identifier in the packet. At 1008, a unique identifier may be generated relating to the access point and mobile device. As described, a unique identifier may contain identifiers of a mobile device and access point, or may be associated in a routing table or similar association. At step 1010, the identifier of the mobile device in the packet can be replaced with a unique identifier, and at step 1012, the uplink packet can be transmitted to the upstream network component. As described in the previous drawings, subsequent packets with a unique identifier can be received from the upstream network component, and the access point and mobile device associated with them can be detected based on the unique identifier.

[0086] Turning to FIG. 11, an example of a method 1100 that facilitates paging for a plurality of connected access points is illustrated. At 1102, a paging call may be received from the MME, where the paging contains the tracking area identifier. At 1104, one or more access points associated with the paging may be determined based on the tracking area identifier. As described, access points can be registered by providing one or more associated tracking zones. This allows you to associate an access point with a tracking area so that when paging is transmitted, access points belonging to the tracking area can be determined and a search call can be delivered to them. Accordingly, at 1106, the paging may be transferred to one or more access points.

[0087] Turning to FIG. 12, an example method 1200 is shown that facilitates identifying access point identifiers in downlink messages. At 1202, a unique identifier relating to the access point may be received in the uplink message. At 1204, a unique identifier can be inserted, in essence, into all related downlink messages to associate messages with the access point. Therefore, the network component receiving the downlink messages can thus route the message to the access point. At 1206, a downlink message may be transmitted to the network component. In this regard, the network component may multiplex messages according to different received identifiers.

[0088] Turning to FIG. 13, an example of a method 1300 that facilitates transmitting messages to a network component with associated identifiers is illustrated. At 1302, a unique identifier may be transmitted to the network component in the application layer setup message. A unique identifier may refer to an access point and may be provided to identify the access point in subsequent messages. Therefore, at 1304, a unique identifier can be inserted, essentially, into all subsequent messages. At 1306, subsequent messages may be transmitted to the network component. Accordingly, as described, a network component, which may be a hub component, can identify an access point in accordance with a unique identifier.

[0089] It should be appreciated that in accordance with one or more of the aspects described herein, conclusions can be made regarding the generation and / or association of unique identifiers with packets transmitted through a hub component. As used herein, the concept of “inferring” or “inference” generally refers to the process of inference about either the output states of a system, environment, and / or user from a set of observations, recorded events, or data. Inference can be used to identify a specific context or action, or it can, for example, form a probability distribution by state. The conclusion can be probabilistic — that is, by calculating the distribution of probabilities over states of interest based on a consideration of data or events. The conclusion may also relate to technologies used to compose high-level events from a group of events or data. Such conclusions lead to the construction of new events or actions from the group of observed events and / or stored event data, regardless of whether or not such events are correlated closely in time and whether or not such events and data occur from one or more sources of the event or data .

[0090] Now referring to FIG. 14, a wireless communication system 14 is illustrated in accordance with various embodiments presented herein. System 1400 comprises a base station 1402, which may include multiple antenna groups. For example, one group of antennas may include antennas 1404 and 1406, another group may include antennas 1408 and 1410, and an additional group may include antennas 1412 and 1414. Two antennas are illustrated for each group; however, more or fewer antennas may be used for each group. Base station 1402 may further include a transmitter circuit and a receiver circuit, each of which in turn may comprise a plurality of components associated with transmitting and receiving a signal (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc. ), as should be taken into account by a specialist in the relevant field.

[0091] Base station 1402 may communicate with one or more mobile devices, such as mobile device 1416 and mobile device 1422; however, it should be appreciated that base station 1402 can communicate with essentially any number of mobile devices similar to mobile devices 1416 and 1422. Mobile devices 1416 and 1422 can be, for example, cell phones, smart phones, portable computers, portable communication devices, portable computing devices, satellite radio stations, global positioning systems, PDAs, and / or any other suitable device for communication over the wireless system 1400 communication. As shown, the mobile device 1416 is in communication with antennas 1412 and 1414, where the antennas 1412 and 1414 transmit information to the mobile device 1416 on the forward link 1418 and receive information from the mobile device 1416 on the reverse link 1420. Moreover, mobile device 1422 is in communication with antennas 1404 and 1406, where antennas 1404 and 1406 transmit information to mobile device 1422 on forward link 1424 and receive information from mobile device 1422 on reverse link 1426. In a frequency division duplex (FDD) system, the forward link 1418 may use a different frequency range than that used by the reverse link 1420, and the forward link 1424 may use a different frequency range than that used by the reverse link 1426 communications, for example. Additionally, in a time division duplex (TDD) system, the forward link 1418 and the reverse link 1420 can use the common frequency range, and the forward link 1424 and the reverse link 1426 can use the common frequency range.

[0092] Each group of antennas and / or the area in which they are intended to communicate may be referred to as a sector of a base station 1402. For example, groups of antennas may be designed to transmit data to mobile devices located in a sector of areas covered by a base station 1402. When communicating over the forward links 1418 and 1424, the transmitting antennas of the base station 1402 can use antenna beamforming to improve the signal-to-noise ratio with respect to the forward lines 1418 and 1424 for mobile 1416 and 1422. Also, while base station 1402 uses beamforming to transmit to mobile devices 1416 and 1422 randomly dispersed within the associated coverage area, mobile devices in neighboring cells may be less affected by interference compared to a base station transmitting via the only antenna to all its mobile devices. Moreover, mobile devices 1416 and 1422 can communicate directly with each other using peer-to-peer or ad hoc technology (not shown).

[0093] According to an example, system 1400 may be a multi-input and multi-output (MIMO) communication system. Additionally, system 1400 can use essentially any type of duplex transmission technology to separate communication channels (eg, forward link, reverse link, ...) such as FDD, FDM, TDD, TDM, CDM and the like. In addition, the communication channels can be orthogonalized to allow simultaneous communication with multiple devices over the channels; in one example, OFDM may be used in this regard. Therefore, the channels can be divided into parts of the frequencies through time periods. In addition, frames can be defined as parts of a frequency over a plurality of time periods; therefore, the frame may contain a number of OFDM symbols. Base station 1402 can communicate with mobile devices 1416 and 1422 via channels that can be created for various types of data. For example, channels can be created to transmit various types of general-purpose communication data, control data (e.g., quality information for other channels, receipt indicators for data received on the channels, interference information, reference signals, etc.), and / or the like.

[0094] Now referring to FIG. 15, a wireless communication system 1500 is illustrated configured to support a number of mobile devices. System 1500 provides communications for multiple cells, such as, for example, macrocell 1502A-1502G, with each cell being served by a corresponding access point 1504A-1504G. As previously described, for example, access points 1504A-1504G related to macrocells 1502A-1502G may be base stations. Mobile devices 1506A-1506I are shown dispersed at various locations within the wireless communication system 1500. Each mobile device 1506A-1506I may communicate with one or more access points 1504A-1504G on the forward link and / or reverse link, as described. In addition, access points 1508A-1508D are shown. These can be small-scale access points, such as femtocell access points, picocell access points, relay nodes, mobile base stations and / or the like, offering services related to a particular location of the service as described. Mobile devices 1506A-1506I may additionally or alternatively communicate with these small-scale access points 1508A-1508D to receive services offered. A wireless communication system 1500 may provide a service for a large geographic area, in one example (e.g., macrocells 1502A-1502G may cover several neighboring quarters, and small-scale spots 1508A-1508G may be present in areas such as apartments, office buildings, and / or the like as described). In an example, mobile devices 1506A-1506I can create a connection to access points 1504A-1504G and / or 1508A-1508D via a radio connection and / or through a backhaul connection.

[0095] According to an example, mobile devices 1506A-1506I can move within a wireless network and re-select cells provided by various access points 1504A-1504G and 1508A-1508D. A new cell selection or handover can be performed for various reasons, such as proximity to the target access point, based on the services provided by the target access point, protocols or standards supported by the target access point, convenient billing associated with the target access point, etc. d. In the example, the mobile device 1506D can communicate with the access point 1504D and can initiate a new cell selection or handover to the small-scale access point 1508C when it is in a certain proximity or its specific measured signal strength. In order to facilitate the new selection of the small-scale access point 1508C, the source represented by the access point 1504D may transmit information to the target object in the form of the small-scale access point 1508C regarding the mobile device 1506D, such as context or other information related to continuing communication between them. Therefore, the target small-scale access point 1508C can provide wireless access to the mobile device 1506D based on contextual information to facilitate continuous new selection and transition from the access point 1504D. In this example, a handover may be facilitated by an MME or an upstream access point (not shown), where access points 1508C and 1504D are connected to an MME or an upstream access point.

[0096] FIG. 16 shows an example of a wireless communication system 1600. The wireless communication system 1600 depicts one base station 1610 and one mobile device 1650 for short. However, it should be appreciated that the system 1600 may include more than one base station and / or more than one mobile device, while the additional base station and / or mobile device may be substantially the same or different from exemplary base station 1610 and mobile device 1650 described below. In addition, it should be appreciated that base station 1610 and / or mobile device 1650 may use the systems described here (Figures 1-6 and 14-15) and / or methods (Figures 7-13) to facilitate wireless communication between them.

[0097] At the base station 1610, traffic data for a number of data streams is provided from a data source 1612 to a transmit (TX) data processor 1614. In accordance with an example, each data stream may be transmitted through a respective antenna. TX data processor 1614 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide encoded data.

[0098] The encoded data for each data stream may be multiplexed with pilot data using a frequency division multiplexing (OFDM) method. Additionally or alternatively, the pilot symbols may be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM). Pilot data is typically a known data pattern that is processed in a known manner and can be used in mobile device 1650 to estimate channel response. The multiplexed pilot and encoded data for each data stream may be modulated (e.g., referenced according to symbols) based on a particular modulation scheme (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), multi-position phase shift keying (M -PSK), multi-position quadrature amplitude modulation (M-QAM), etc.) selected for this data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed or provided by processor 1630.

[0099] Modulation symbols for data streams may be provided to a TX MIMO processor 1620, which may further process modulation symbols (eg, for OFDM). The 1620 TX MIMO processor then provides modulation symbol streams in the amount of N _T pieces to transmitters 1622a through 1622t (TMTR) in the number of N _T pieces. In various aspects, the TX MIMO processor 1620 applies beamforming to the symbols of the data streams and to the antennas through which the symbols are transmitted.

[0101] Each transmitter 1622 receives and processes a respective symbol stream to provide one or more analog signals, and further brings to a predetermined state (for example, amplifies, filters, and upconverts) the analog signals in order to provide a modulated signal, suitable for transmission over the MIMO channel. Further, modulated signals in the amount of N _T pieces from transmitters 1622a through 1622t are transmitted from antennas 1624a through 1624t in the amount of N _T , respectively.

[0102] In the mobile device 1650, transmitted modulated signals are received by antennas 1652a through 1652r in an amount of N _R pieces, and a received signal from each antenna 1652 is provided to a respective receiver 1654a through 1654r (RCVR). Each receiver 1654 brings to a predetermined state (for example, filters, amplifies, and downconverts) a corresponding signal, digitizes the signal to a predetermined state to provide bins, and further processes the samples to provide a corresponding “received” symbol stream.

[0103] An RX (received) data processor 1660 can receive and process the received symbol streams in the amount of N _R pieces, from the receivers 1654 in the number of N _R pieces, based on the specific receiver processing technology to provide “detected” symbol streams in the number of N _T pieces. An RX data processor 1660 may demodulate, deinterleave, and decode each detected symbol stream to recover traffic data for the data stream. The processing by RX data processor 1660 is complementary to that performed by TX MIMO processor 1620 and TX data processor 1614 at base station 1610.

[0104] The processor 1670 may periodically determine which precoding matrix to use, as discussed above. Additionally, processor 1670 may formulate a reverse link message comprising a matrix index portion and a rank portion.

[0105] The reverse link message may contain various types of information regarding the communication link and / or the received data stream. The reverse link message can be processed by a TX data processor 1638, which also receives traffic data for a number of data streams from a data source 1636 modulated by a modulator 1680, set to transmitters 1654a through 1654r, and transmitted back to base station 1610.

[0106] At the base station 1610, the modulated signals from the mobile device 1650 are received by the antennas 1624, set to receivers 1622, demodulated by the demodulator 1640, and processed by the RX data processor 1642 to extract the reverse link message transmitted by the mobile device 1650. Additionally, processor 1630 may process the extracted message to determine which precoding matrix to use for determining beamforming weights.

[0107] Processors 1630 and 1670 can control (eg, manage, coordinate, organize) the operation of base station 1610 and mobile device 1650, respectively. Respective processors 1630 and 1670 may be associated with a memory 1632 and 1672 that stores program codes and data. Processors 1630 and 1670 can also perform calculations to obtain estimates of pulse and frequency responses with respect to uplink and downlink, respectively.

[0108] It should be understood that the aspects described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. When implemented in hardware, the processing module can be implemented in one or more specialized integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), programmable gate arrays (FPGAs) ), processors, controllers, microcontrollers, microprocessors, other electronic modules designed to perform the functions described here, or combinations thereof.

[0109] When aspects are implemented in software, firmware, middleware or microcode, program code or code segments, they can be stored on a computer-readable storage medium, such as a storage component. A code segment can be a procedure, function, subprogram, program, standard program, standard subprogram, module, software package, class, or any combination of instructions, data structures, or program segments. A code segment can be connected to another code segment or a hardware circuit by sending / or receiving information, data, arguments, parameters or memory contents. Information, arguments, parameters, data, etc. can be forwarded, forwarded or transmitted using any suitable means, including shared memory, forwarding messages, forwarding tokens, network transfers, etc.

[0110] When implemented in software, the methods described herein may be implemented in modules (eg, procedures, functions, etc.) that perform the functions described herein. Software codes can be stored in memory modules and executed by processors. The memory modules can be implemented inside the processor or external to the processor, in which case they can be connected to communicate with the processor through various means known in the relevant field of technology.

[0111] With reference to FIG. 17, illustrated is a system 1700 that facilitates multiplexing communication between an access point and an MME. For example, system 1700 may be located at least partially in a base station, mobile device, etc. It should be appreciated that the system 1700 is presented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or a combination thereof (e.g., firmware). System 1700 includes a logical grouping 1702 of electrical components that can act in conjunction. For example, logical grouping 1702 may include an electrical component 1704 for receiving a downlink packet from an MME. For example, as described, a downlink packet may have an associated identifier and may be transmitted in response to an uplink packet transmitted on behalf of an access point related to the identifier, for example. In addition, logical grouping 1702 may include an electrical component 1706 for determining an access point related to a downlink packet based at least in part on a locally unique identifier contained within a downlink packet.

[0112] Therefore, as described, this can be based on: stored correspondence of the identifiers of access points to locally unique identifiers; identifying an identifier of an access point located inside a locally unique identifier; and / or the like. Moreover, logic group 1702 may include an electrical component 1708 for transmitting a downlink packet to an access point. In addition, the logical grouping 1702 may include an electrical component 1710 for determining a mobile device related to a downlink packet based at least in part on a locally unique identifier. Similarly, a mobile device identifier can be determined: from a match; Indications in a locally unique identifier and / or the like. In addition, the logical grouping 1702 may include an electrical component 1712 for extracting the identifier of the mobile device and the identifier of the access point from the uplink packet and determining a locally unique identifier as relating to the identifier of the mobile device and identifier 1712 of the access point. System 1700, although not shown, can also generate a locally unique identifier based on a received uplink packet; therefore, system 1700 can determine an access point and / or mobile device related to an identifier based on a previously generated associated locally unique identifier. Additionally, system 1700 may include a memory 1714 that contains instructions for executing functions associated with electrical components 1704, 1706, 1708, 1710, and 1712. Although shown as external to memory 1714, it should be understood that one or more electrical components 1704, 1706, 1708, 1710 and 1712 may exist within memory 1714.

[0113] With reference to FIG. 18, illustrated is a system 1800 that facilitates multiplexing communication between an access point and a higher access point. For example, system 1800 may be located, at least in part, within a base station, mobile device, etc. It should be appreciated that the system 1800 is presented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or a combination thereof (e.g., firmware). System 1800 includes a logical grouping 1802 of electrical components that can act in conjunction. For example, logical grouping 1802 may include an electrical component 1804 for retrieving a locally unique identifier from a downlink packet received from a superior access point. For example, as described, a downlink packet may have an associated identifier and may be received in response to an uplink packet transmitted on behalf of an access point related to the identifier, for example. In addition, logical grouping 1802 may include an electrical component 1806 for determining a mobile device identifier associated with a locally unique identifier, and replacing the locally unique identifier in the downlink packet with a mobile device identifier.

[0114] Moreover, the logical grouping 1802 may include an electrical component 1808 for determining an identifier for a downstream access point related to a locally unique identifier. In addition, logical grouping 1802 may include an electrical component 1810 for transmitting a downlink packet to a downlink access point related to an identifier of a downstream access point. Therefore, as described, the downstream access point receives a packet with the identifier of the mobile device, which can be exactly the same as the identifier used to transmit to the system 1802 its related uplink packet, as described here. Additionally, system 1800 may include a memory 1812 that contains instructions for executing functions associated with electrical components 1804, 1806, 1808, and 1810. Although shown as external to memory 1812, it should be understood that one or more electrical components 1804, 1806, 1808, and 1810 may exist within memory 1812.

[0115] With reference to FIG. 19, illustrated is a system 1900 that implements paging for a plurality of access points communicating with a hub to access an MME. For example, system 1900 may be located, at least in part, within a base station, mobile device, etc. It should be appreciated that the system 1900 is presented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or a combination thereof (e.g., firmware). System 1900 includes a logical grouping 1902 of electrical components that can act in conjunction. For example, logical grouping 1902 may include an electrical component 1904 for receiving a paging call from the MME containing a tracking area identifier. In addition, logical grouping 1902 may include an electrical component 1906 for determining one or more access points associated with a tracking area identifier based, at least in part, on stored correspondence of access points with tracking area identifiers.

[0116] As described, access points can be registered using the system 1900, indicating the identifiers of the tracking zone, which can be stored with the association with the access point in the correspondence or routing table. Moreover, logical grouping 1902 may include an electrical component 1908 for transmitting a paging to one or more access points. Additionally, the system 1900 may include a memory 1910 that contains instructions for executing functions associated with the electrical components 1904, 1906, and 1908. Although shown as external to the memory 1910, it should be understood that one or more electrical components 1904, 1906, and 1908 may exist inside the memory of 1910.

[0117] With reference to FIG. 20, a system 2000 is illustrated that inserts access point identifiers into downlink messages to facilitate multiplexing of access point communications. For example, system 2000 may be located, at least in part, within a base station, mobile device, etc. It should be appreciated that the system 2000 is presented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or a combination thereof (e.g., firmware). System 2000 includes a logical group 2002 of electrical components that can act in conjunction. For example, logical group 2002 may include an electrical component 2004 for receiving a unique identifier in an uplink message related to an access point. For example, as described, the identifier can be used to identify the source of the message, as well as to associate the access point with the corresponding message downlink. In addition, logical group 2002 may include an electrical component 2006 for inserting a unique identifier in an application layer downlink message to help determine an access point related to an uplink message and transmitting an application layer downlink message to a network component. The network component, as described, can determine the appropriate access point to forward the message based on the identifier. Additionally, system 2000 may include memory 2008, which contains instructions for performing functions associated with the electrical components 2004 and 2006. Although shown as external to memory 2008, it should be understood that one or more electrical components 2004 and 2006 may exist within the memory of 2008.

[0118] With reference to FIG. 21, illustrated is a system 2100 that receives messages from an upstream network component through a hub. For example, system 2100 may be located, at least in part, within a base station, MME, mobile device, etc. It should be appreciated that the system 2100 is presented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or a combination thereof (e.g., firmware). System 2100 includes a logical grouping 2102 of electrical components that can act in conjunction. For example, logical grouping 2102 may include an electrical component 2104 for inserting a unique identifier in an application layer connection setup message, and essentially all relevant uplink messages, in order to facilitate the determination of an access point related to uplink messages. In addition, logical grouping 2102 may include an electrical component 2106 for transmitting uplink messages to a network component.

[0119] Therefore, the network component can identify an access point transmitting messages as described. In addition, uplink messages may comprise, where applicable, a mobile device identifier. Moreover, logical grouping 2102 may include an electrical component 2108 for receiving one or more downlink messages in response to uplink messages. In addition, logical group 2102 may include an electrical component 2110 for sending downlink messages to one or more mobile devices based at least in part on an unequal identifier in downlink messages. Additionally, system 2100 may include a memory 2112 that contains instructions for executing functions associated with electrical components 2104, 2106, 2108, and 2110. Although shown as external to memory 2112, it should be understood that one or more electrical components 2104, 2106, 2108, and 2110 may exist within memory 2112.

[0120] The various illustrative logic blocks, modules, and circuits described in relation to the embodiments discussed herein may be implemented or implemented by a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), programmable gate array (FPGA), or other programmable logic devices, discrete component circuits or transistor logic, discrete hardware components, or any combination of these designed to I perform the functions described here. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configurations. Additionally, at least one processor may comprise one or more modules operable to perform one or more of the steps and / or actions described above.

[0121] Additionally, the steps and / or actions of a method or algorithm described in relation to the aspects discussed herein may be embodied directly in hardware, a software module executed by a processor, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be an integral part of the processor. Additionally, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as separate components in a user terminal. Additionally, in some aspects, the steps and / or actions of a method or algorithm may be placed as one or any combination or set of codes and / or instructions on a computer-readable storage medium and / or computer-readable storage medium that may be included in a computer program product .

[0122] In one or more aspects, the described functions may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, functions may be stored or transmitted as one or more instructions or code on a computer-readable storage medium. A computer-readable storage medium includes both a computer storage medium and communication means, including means that facilitate the transfer of a computer program from one place to another. The storage medium may be any suitable medium that can be accessed by a computer. By way of example, and not limitation, such a computer-readable storage medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk drive, magnetic disk drive or other magnetic storage devices, or any other medium that may be used to transfer or store the required program code in the form of instructions or data structures and access to which can be obtained through a computer. Also, any connection may be called a computer readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (DSL), or wireless technologies such as infrared, radio, or microwave, then a coaxial cable , fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio or microwave, are included in the concept of information carrier. The magnetic and non-magnetic discs used here include a compact disc (CD), a laser disc, an optical disc, a universal digital disc (DVD), a flexible magnetic disc, and a blue-ray disc, where magnetic discs typically magnetically reproduce data in while non-magnetic disks reproduce data optically with a laser. Combinations of the above should also be included within the scope of the concept of computer-readable media.

[0123] Although the foregoing disclosure addresses illustrative aspects and / or embodiments, it should be noted that various changes and modifications may be made without departing from the scope of the described aspects and / or embodiments as defined by the appended claims. inventions. In addition, although elements of the described aspects and / or embodiments could be described or claimed in the singular, the plural is contemplated unless limitation on the singular is explicitly declared. Additionally, an entire or part of any aspect and / or embodiment may be used with all or part of any other aspect and / or embodiment, unless otherwise indicated. Moreover, to the extent that the concept of “includes” is used, both in the detailed description and in the claims, such a concept is intended to be included in an image similar to the concept of “comprising”, in accordance with how “comprising” is interpreted when used as an intermediate word in the claims. In addition, although elements of the described aspects and / or embodiments could be described or claimed in the singular, the plural is contemplated unless limitation on the singular is explicitly declared. Additionally, all or part of any aspect and / or embodiment may be used with all or part of any other aspect and / or embodiment, unless otherwise indicated.

Claims (18)

1. A method for transmitting a paging call in a communication system using a concentrator, comprising the steps of: receiving from a mobility management entity, MME, a paging call containing a tracking area identifier, the paging containing one or more identifiers corresponding to one or more mobile devices ; determining one or more access points associated with the identifier of the tracking zone, based at least in part on the stored mapping of the access points to the identifiers of the tracking zone; and transmitting the paging to one or more access points to allow one or more access points to search for one or more mobile devices identified in the paging. 2. The method according to claim 1, further comprising the step of receiving one or more tracking area identifiers associated with the access point, and storing the association between the access point and one or more tracking area identifiers in a stored display. 3. The method according to claim 2, further comprising stages in which:
determining that at least one of one or more tracking area identifiers is a new tracking area identifier; and transmitting to the MME a configuration update message containing a new tracking zone identifier. 4. The method of claim 2, wherein the one or more tracking area identifiers are associated with one or more locations served by the access point. 5. The method according to claim 1, further comprising the step of indicating a tracking zone identifier in a message transmitted to the MME on behalf of one or more access points associated with the tracking zone identifier. 6. A wireless communication device, comprising: at least one processor configured to: receive from a mobility management entity, MME, a paging containing a tracking zone identifier, the paging comprising one or more identifiers corresponding to one or more mobile devices; recognizing one or more access points associated with the identifiers of the tracking zone, based at least in part on the stored association of the access points with the identifiers of the tracking zone; and transmitting the search call to one or more access points to allow one or more access points to search for one or more mobile devices identified in the search call; and memory coupled to said at least one processor. 7. The wireless communications apparatus of claim 6, wherein said at least one processor is further configured to obtain one or more tracking area identifiers associated with the access point, and maintain an association between the access point and one or more tracking area identifiers in a stored associations. 8. A hub for multiplexing connections of an access point with a wireless network, comprising: means for receiving from a mobility management entity, MME, a paging containing a tracking zone identifier, the paging containing one or more identifiers corresponding to one or more mobile devices; means for determining one or more access points associated with the identifier of the tracking zone, based at least in part on the stored mapping of the access points to the identifiers of the tracking zone; and means for transmitting the search call to one or more access points to allow one or more access points to search for one or more mobile devices identified in the search call. 9. The hub of claim 8, wherein the means for determining one or more access points associated with the tracking area identifier receives one or more tracking area identifiers associated with the access point and maintains an association between the access point and one or more zone identifiers tracking in a saved display. 10. The hub according to claim 9, in which the means for determining one or more access points associated with the identifier of the tracking zone determines that at least one of the one or more identifiers of the tracking zone is a new identifier of the tracking zone, and the means for receiving search The call from the MME sends to the MME a configuration update message containing the new tracking zone identifier. 11. The hub according to claim 9, wherein said one or more tracking area identifiers are associated with one or more locations served by the access point. 12. The hub of claim 8, wherein the means for determining one or more access points associated with the tracking area identifier indicates the tracking area identifier in a message transmitted to the MME on behalf of one or more access points associated with the tracking area identifier. 13. A computer-readable medium comprising computer-executable instructions to cause a computer to carry out a method comprising the steps of: receiving a search call from a mobility management entity, MME, comprising a tracking area identifier, the search call containing one or more identifiers corresponding to one or more mobile devices; determining one or more access points associated with the identifier of the tracking zone, based at least in part on the stored mapping of the access points to the identifiers of the tracking zone; and transmitting the paging to one or more access points to allow said one or more access points to search for one or more mobile devices identified in the paging. 14. The computer-readable medium of claim 13, further comprising code to cause at least one computer to receive one or more tracking area identifiers associated with the access point, and to keep the association between the access point and one or more tracking area identifiers in a stored display. 15. A hub for multiplexing connections of an access point to a wireless network, comprising: a connection component with upstream objects that receives from a mobility management entity, MME, a paging call containing a tracking zone identifier, the paging call containing one or more identifiers corresponding to one or more Mobile devices a paging component that identifies one or more access points associated with the tracking area identifier based, at least in part, on the stored mapping of the access points to the tracking area identifiers; and a downstream connection component transmitting the search call to one or more access points to allow one or more access points to search for one or more mobile devices identified in the search call. 16. The hub of claim 15, wherein the paging component receives one or more tracking area identifiers associated with the access point, and stores the association between the access point and one or more tracking area identifiers in a stored display. 17. The hub of claim 16, wherein the paging component determines that at least one of the one or more tracking zone identifiers is a new tracking zone identifier, and the parent connection component sends a configuration update message containing a new zone identifier to the MME tracking. 18. The hub of claim 15, wherein the paging component indicates a tracking area identifier in a message transmitted to the MME on behalf of one or more access points associated with the tracking area identifier.

Images