Efficient retrieval of 4G LTE capabilities

• US 9,282,181 B2
• Filed: 03/21/2014
• Issued: 03/08/2016
• Est. Priority Date: 03/21/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Antos, Christopher, Reeves, Chuck
• Primary Examiner(s): Appiah, Charles
• Assistant Examiner(s): YI, ALEXANDER J.
• Application Number:
  US14/221,773
• Publication Number:
  US 20150271318A1
• Time in Patent Office: 718 Days
• Field of Search: 455/412.1, 455/414.1, 370/230.1, 348/14.08, 348/14.01, 348/E07.077
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04M 1/27453 Directories allowing storage of additional subscriber data, e.g. metadata
• CPC Class Codes: H04M 1/2757 by data transmission, e.g. downloading
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/72469 for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

A mobile device executes a background process under an on demand model that queries a remote service exposed by a mobile broadband network to receive status updates as to the capabilities of devices, such as the ability to stream video, that are associated with contacts that are stored on the mobile device. When a mobile device user invokes an action like using a dialer application that causes a contact to be displayed on the device'"'"'s user interface (UI) such as in a contact card or contact list format, the background process immediately retrieves status for that contact card or list. While waiting for the status retrieval to complete, the background process will trigger the display of a temporary UI on the mobile device which can show either unknown capabilities status or show the most recently retrieved status that is read out of a cache.

Claims

1. A method performed on a mobile device with a user interface (UI) and having access to a mobile broadband network, comprising:

receiving an input from a user for invoking display of a contact card or a contact list on the UI;

responsively to the input, sending a request to a remote service for current status of capabilities of devices respectively associated with each of the displayed contacts, the status describing capabilities of the devices to implement features or services supported by the mobile broadband network;

while waiting for the service to respond to the request, displaying a temporary UI to the user on the mobile device, the temporary UI showing the invoked contact card or contact list but without showing current status for the displayed contacts;

receiving the current status for a contact from the remote service; and

applying a timestamp to the received current status, and throttling requests for current status to the remote service using the timestamp,

wherein the timestamp is utilized to enable a current status for a contact to automatically expire at the end of a predetermined time interval, and

wherein a status request will not be attempted during the predetermined time interval.

2. The method of claim 1 further including receiving the current status from the remote service and caching the status.

3. The method of claim 1 further including showing a most recently cached status on the temporary UI.

4. The method of claim 1 further including receiving the current status for a contact from the remote service and updating the UI with the received current status for the contact.

5. The method of claim 1 further including receiving the current status for a contact, the current status including a timestamp, and throttling requests for current status to the remote service using the timestamp so as to preserve life of a battery disposed in the mobile device.

6. The method of claim 1 in which the request for current status includes batched requests for status of capabilities for a plurality of devices.

7. A mobile device having connectivity to a mobile operator network, comprising:

one or more processors;

a display that supports a user interface (UI) for conveying information to a user of the mobile device; and

a memory device storing computer-readable instructions which, when executed by the one or more processors, perform a method comprising the steps of;

receiving an input from the user that invokes display of a list of contacts on the UI,

showing the list of contacts on a displayed screen on the UI responsively to the received input, the displayed screen showing a most recently cached status for each of the listed contacts,

sending a request to a remote service for current status of capabilities of devices respectively associated with each of the listed contacts displayed on the displayed screen,

updating the displayed screen with the current status for each of the listed contacts displayed on the displayed screen when the current status is received from the remote service,

pre-fetching status from the remote service for contacts in additional screens that are displayable on the UI, the contacts in the additional screens having a contextual relationship to the contacts shown in the current screen,

displaying one or more additional screens of contacts including the pre-fetched status responsively to user input to view additional screens,

applying a timestamp to the received current status, and throttling requests for current status to the remote service using the timestamp,

wherein the timestamp is utilized to enable a current status for a contact to automatically expire at the end of a predetermined time interval, and

wherein a status request will not be attempted during the predetermined time interval.

8. The mobile device of claim 7 in which the mobile operator network comprises a mobile broadband network.

9. The mobile device of claim 7 in which the user input is associated with utilization of a dialer application.

10. The mobile device of claim 7 in which the capabilities include at least availability of a device to render streaming video transmitted over an LTE (Long Term Evolution) mobile broadband network.

11. The mobile device of claim 7 in which the contextual relationship is one of visual proximity, relationship proximity, location, time, or associative property.

12. The mobile device of claim 11 in which the relationship proximity includes contacts in the current screen and contacts in the additional screens sharing membership in one of special contacts, frequently used contacts, most recently called contacts, contacts called before, or contacts having known capabilities.

13. The mobile device of claim 7 further including applying one or more heuristics to data included in the received status to make inferences as to capabilities of a device to which the received status is associated.

14. A method, by a remote service, for providing a service that returns capabilities status in response to a request from a mobile device, comprising:

receiving a request for current status from a mobile device having connectivity to a mobile broadband network, the current status indicating capabilities of devices respectively associated with contacts shown in a list on a user interface (UI) supported by the mobile device, wherein the current status includes an indication of devices abilities to implement features or services supported by a mobile broadband network, the features or services being related to video consumption or video rendering;

in response to the request for current status for a contact by the mobile device, sending the current status to the mobile device, where the current status includes a timestamp generated by the remote service, operable to throttle requests for current status to the remote service using the timestamp by the mobile device, wherein the timestamp is utilized to enable a current status for a contact to automatically expire at the end of a predetermined time interval, and wherein a status request will not be attempted during the predetermined time interval;

receiving a request for pre-fetching additional status from the mobile device, the additional status pertaining to contacts in additional screens that are displayable on the UI in response to user input; and

in response to the request pre-fetching additional status, sending the additional status to the mobile device.

15. The method of claim 14 in which the service is exposed by a network element disposed in a mobile broadband network.

16. The method of claim 14 further including exposing an application programming interface configured for fulfilling status requests for a single contact per request.

17. The method of claim 14 further including exposing an application programming interface configured for fulfilling status requests on a batched request basis.

18. The method of claim 17 further including sending a notification when status responsive to the batched request is fulfilled.