Registration notification for mobile device management

• US 10,095,505 B2
• Filed: 11/22/2016
• Issued: 10/09/2018
• Est. Priority Date: 12/03/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: Lewis, John, Payne, James
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Gooray, Mark A
• Application Number:
  US15/359,211
• Publication Number:
  US 20170075681A1
• Time in Patent Office: 686 Days
• Field of Search: None
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 30/018 Certifying business or products
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 36/04 Reselecting a cell layer in multi-layered cells
• CPC Class Codes: H04W 40/00 Communication routing or communication path finding
• CPC Class Codes: H04W 40/36 due to handover
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 84/045 using private Base Stations, e.g. femto Base Stations, home Node B

Abstract

Notification of registration of a mobile device with femto coverage for firmware content management is provided. An attachment component that administers location of mobile devices or a femto access point (AP) conveys a notification to a network platform that manages firmware content updates when a mobile device for which firmware update is available hands off from wireless macro coverage onto femto coverage through the femto AP. The notification is triggered in response to firmware update notification received by the attachment component, or an update flag received by the femto AP. Upon reception of the notification, to exploit wireline bandwidth, the network platform delivers firmware content(s) update through backhaul link to the femto AP to which the mobile device is registered. Femto APs not provisioned to serve a mobile device can be incentivized to authorize the mobile device for coverage and thus facilitate firmware updates.

Claims

1. A method, comprising:

sending, by a network device comprising a processor to a femto cell device of a femto network, an update flag associated with an availability of a firmware update for a mobile device of the femto network;

in response to a first indication that the mobile device is not registered with the femto cell device, delaying, by the network device, sending of the firmware update;

sending, by the network device, data representing a data storage incentive to the femto cell device to transfer a connection of the mobile device from a base station device of a wireless network to the femto cell device to receive the firmware update;

in response to a second indication that the mobile device has registered with the femto cell device, receiving, by the network device, a registration notification, via a backhaul link, from the femto cell device;

based on the second indication, sending, by the network device, the firmware update to the femto cell device;

in response to the sending the firmware update, receiving, by the network device, error bits indicative of an error associated with the firmware update at the femto cell device being determined to have been unsuccessful, wherein the error bits are received via a control channel between the femto cell device and the network device; and

in response to the receiving the error bits, initiating, by the network device, a retry cycle to resend the firmware update to the femto cell device.

2. The method of claim 1, further comprising:

determining, by the network device, whether a resource of the mobile device is available to receive the firmware update.

3. The method of claim 2, wherein the resource comprises a memory to store the firmware update.

4. The method of claim 3, further comprising:

generating, by the network device, the firmware update based on a condition associated with a quality of service enabled by the resource being determined not to have been satisfied.

5. The method of claim 3, further comprising:

generating, by the network device, the firmware update based on a condition associated with a quality of service enabled by the resource being determined to have been satisfied.

6. The method of claim 1, further comprising:

in response to the mobile device transferring the connection, initiating, by the network device, a delivery of the firmware update to the femto cell device.

7. The method of claim 6, wherein the initiating the delivery comprises initiating the delivery of signal data representative of a transferred connection between the mobile device and the femto cell device.

8. A system, comprising:

a processor; and

a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising;

sending, to a femto cell device of a femto network, flag data that indicates that a firmware content update is available for a mobile device;

sending, to the femto cell device, incentive data related to an incentive for the mobile device to register with the femto cell device to receive the firmware content update, wherein the incentive is associated with a data store;

in response to a first indication that the mobile device is not registered with the femto cell device, delaying sending of the firmware update;

in response to the mobile device being determined to have registered with the femto cell device, receiving a registration notice from the femto cell device;

based on the registration notice, sending, to the femto cell device, the firmware content update;

in response to the sending the firmware content update, receiving notification data indicative of a notification that the firmware content update at the femto cell device has been determined to have been unsuccessful, wherein the notification data comprises error bits; and

in response to the receiving the notification data, resending the firmware update a defined number of times.

9. The system of claim 8, wherein the mobile device is a first mobile device, and wherein the operations further comprise:

based on a bandwidth granted for the firmware content update via a second mobile device, configuring an update profile.

10. The system of claim 8, wherein the operations further comprise:

based on the firmware content update, configuring an update profile.

11. The system of claim 10, wherein the configuring is based on a priority ranking of the firmware content update.

12. The system of claim 8, wherein the operations further comprise:

in response to determining that a communication resource is unavailable, generating the firmware content update.

13. The system of claim 8, wherein the operations further comprise:

based on a condition associated with wireless device resources being determined not to have been satisfied, resending the firmware content update.

14. The system of claim 8, wherein the notification is a first notification, and wherein the operations further comprise:

receiving a second notification, via a notification component, when the mobile device is attached to the femto cell device.

15. A non-transitory machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:

sending, to a femto cell device of a femto network, update flag data comprising a first indication that a firmware content update is available for a mobile device;

sending incentive data, related to an incentive for the mobile device to register with the femto cell device, to the mobile device, wherein the incentive data is associated with a data storage for the mobile device;

in response to a second indication that the mobile device has not registered with the femto cell device, receiving a registration notification and delaying sending the firmware content update to the femto cell device;

in response to the sending the firmware content update, receiving notification data representative of a notification that installation of the firmware content update at the femto cell device has been determined to be unsuccessful, wherein the notification data comprises an error bit received via a control channel; and

based on the installation of the firmware content update being determined to be unsuccessful, resending the firmware content update to the femto cell device a determined number of times.

16. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

based on a condition associated with a mobile device resource being determined not to have been satisfied, delaying the sending the firmware content update.

17. The non-transitory machine-readable storage medium of claim 16, wherein the mobile device resource enables a bandwidth associated with the mobile device.

18. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

tracking a location of the mobile device relative to the femto cell device.

19. The non-transitory machine-readable storage medium of claim 15, wherein the notification is a first notification, and wherein the operations further comprise:

receiving a second notification in response to the mobile device being determined to have been attached to the femto cell device.

20. The non-transitory machine-readable storage medium of claim 19, wherein the operations further comprise:

based on the receiving the second notification, tracking a registration status associated with a registration of the mobile device to the femto cell device.