FEMTOCELL ARCHITECTURE FOR INFORMATION MANAGEMENT

• US 20090286540A1
• Filed: 05/13/2009
• Published: 11/19/2009
• Est. Priority Date: 05/13/2008
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Huber, Kurt Donald, Flynn, Judson John, Mansfield, William Gordon
• Granted Patent: US 8,254,368 B2
• Time in Patent Office: Days
• US Class Current: 455/435.100
• CPC Class Codes: G05B 2219/2614 HVAC, heating, ventillation, climate control
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/387 Payment using discounts or coupons relating to marketing G06Q30/02
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0222 During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0261 based on user location
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G07F 9/001 Interfacing with vending machines using mobile or wearable devices
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: H04B 1/3822 specially adapted for use in vehicles H04B1/3827 takes precedence
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 5/0048 Allocation of pilot signals, i.e. of signals known to the receiver
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/101 : Access control lists [ACL]
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 63/108 : when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04M 15/73 : Validating charges
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/082 : using revocation of authorisation
• CPC Class Codes: H04W 12/088 : using filters or firewalls
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/023 : using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/027 : using movement velocity, acceleration information
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 : Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 4/40 : for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 48/02 : Access restriction performed under specific conditions
• CPC Class Codes: H04W 48/04 : based on user or terminal location or mobility data, e.g. moving direction, speed
• CPC Class Codes: H04W 48/08 : Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/20 : Selecting an access point
• CPC Class Codes: H04W 64/006 : with additional information processing, e.g. for direction or speed determination
• CPC Class Codes: H04W 68/02 : Arrangements for increasing efficiency of notification or paging channel
• CPC Class Codes: H04W 8/20 : Transfer of user or subscriber data
• CPC Class Codes: H04W 8/22 : Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 84/045 : using private Base Stations, e.g. femto Base Stations, home Node B
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices

Abstract

A system and methodology that significantly reduces traffic in a backhaul pipe of a femto access point (AP) and organizes content delivery is provided. Specifically, an aggregator/routing platform is employed to connect multiple femto APs in a femto enterprise to a single backhaul network. The aggregator/routing platform collects and analyzes information from the multiple femtos and directly route communication packets to between femto APs within the enterprise when possible, without employing the backhaul network. Content and/or tasks can be internally organized between devices connected to the multiple femtos, without accessing the core network. During internal communication, a control link can preserved and sent to the core network to facilitate billing.

Claims

1. A system that reduces traffic in a backhaul pipe in a femto enterprise architecture, comprising:

a routing platform that connects multiple femto access points (APs) to a common femto gateway, the routing platform directs communication received from a femto AP based in part on an analysis of the received communication.

2. The system of claim 1, further comprising, a route determination component that provides determined routing information associated with the received communication to the routing platform.

3. The system of claim 1, further comprising, a content/task organization component that provides information associated with at least one of synchronizing, updating, distributing or transferring data between multiple devices connected to the multiple femto APs without accessing a core network.

4. The system of claim 3, wherein the content/task organization component employs at least one of a policy, schedule, user preference, white list or black lists to provide the information.

5. The system of claim 1, further comprising, an aggregation component that receives registration data associated with user equipment (UE) attached to the multiple femto access points connected to the routing platform, the registration data employed to determine a route for the received communication.

6. The system of claim 1, further comprising, an analysis component that determines whether the received communication can be routed internally within the femto enterprise without accessing a core network, based in part on an evaluation of the received communication.

7. The system of claim 6, wherein, the routing platform performs a soft handover and directs the communication to a femto AP connected within the femto enterprise when determined that the received communication can be routed internally.

8. The system of claim 6, wherein, the routing platform performs a hard handover and directs the communication to the common femto gateway when determined that the received communication cannot be routed internally.

9. The system of claim 7, wherein, the routing platform sends control data associated with the communication to the core network when the received communication is routed internally, the control data employed to update a billing database.

10. A method that facilitates content and task organization in a femto enterprise architecture, comprising:

connecting multiple femto access points (APs) to a common backhaul pipe to generate a femto enterprise mesh network;

receiving a communication packet from at least one of the multiple femto APs; and

,

routing the communication packet based on an analysis of the communication packet to reduce traffic over the common backhaul pipe.

11. The method of claim 10, further comprising, determining whether the communication packet can be routed internally without accessing a core network.

12. The method of claim 11, further comprising, performing a soft handover and routing the communication packet to a destination femto AP connected within the femto enterprise mesh network when determined that communication packet can be routed internally.

13. The method of claim 12, further comprising, transferring control data associated with the internal routing to a core network via the backhaul pipe, the control data facilitates billing associated with network usage.

14. The method of claim 10, further comprising, at least one of synchronizing, updating, distributing or transferring data between multiple devices connected to the multiple femto APs without accessing a core network, based in part on an analysis of at least one of a policy, schedule, user preference, white list or black lists.

15. The method of claim 10, wherein, the analysis is based in part on information associated with at least one of a source user equipment (UE), a destination UE, a policy, a white list, a black list, a user preference, or aggregated UE registration information.

16. A system that employs an enterprise femto architecture to efficiently manage bandwidth on a backhaul network, comprising:

means for connecting multiple femto access points (APs) to a common backhaul pipe to generate a femto enterprise mesh network; and

means for routing a packet received from at least one of the multiple femto APs based on an analysis of the packet.

17. The system of claim 16, further comprising, means for aggregating user equipment (UE) registration data received from the multiple femto APs that identifies a set of UEs currently connected to the multiple femto APs.

18. The system of claim 17, further comprising, means for determining a route for the packet based in part on an analysis of at least one of the packet, or the aggregated UE registration data.

19. The system of claim 18, further comprising:

means for performing a soft handover and transferring the packet to a destination femto AP connected within the femto enterprise mesh network when the determined route is internal; and

means for generating control information associated with the packet transfer when the determined route is internal.

20. The system of claim 16, further comprising, means for at least one of synchronizing, updating, distributing or transferring data between multiple devices connected to the multiple femto APs without accessing a core network, based in part on an analysis of at least one of a policy, schedule, user preference, white list or black lists.