Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/2866—Architectures; Arrangements
  • H04L67/30—Profiles
  • H04L67/306—User profiles
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L67/62—Establishing a time schedule for servicing the requests
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
  • H04W52/02—Power saving arrangements
  • H04W52/0209—Power saving arrangements in terminal devices
  • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

• the controlling includes suspending a download of a file that is occurring when a power level or network connectivity degrades during the download.
• the suspending of the download is based on a set of rules or heuristics.
• the suspended download is resumed when the power level or network connectivity improves during the suspension.
• the resumed download does not include at least some of the file or files that were downloaded before the suspension.
• the resumed download does not include one or more pieces of a file that were downloaded before the suspension.
• Some implementations include one or more of the following features.
• the conditions are monitored after each piece is sent and before download of the subsequent piece has begun.
• a partial download of a file is allowed to continue under deteriorated conditions, if predetermined circumstances exist.
• a sync signal is received from a server with respect to one or more large files to be downloaded, and to the sync signal is responded to by requesting and accepting a download of the one or more large files.
• an indication is displayed to a user of the time when a download of one or more large files to the mobile device is expected to occur.
• an amount of bandwidth used to download one or more large files to a mobile device is adjusted based on a time of day when the download is to occur.
• a user of a mobile device can specify one or more types of files that are to be downloaded to the mobile device, and the specification of file types is stored in a server in association with an identification of the mobile device or the user.
• a server at a server, one or more files are selected to be downloaded to a mobile device based on stored preferences of a user of the mobile device and stored information about files that were previously downloaded to the user's device.
• Some of the files 10, 20 in figure 1 are large.
• a 30-minute audio, a 10+ minute video file, and a collection of 100+ web pages may be from 1MB to 500MB or larger.
• an application 60 manages the delivery of these large files from the remote server to the mobile device in a way that is sensitive to the following considerations:
• the mobile device has one or more network interfaces 80, e.g., GPRS/EDGE,
• the mobile device's power status 70 varies from time to time, depending, for example, on whether the device is charging or how long it has been on battery.
• Certain files 10 are time sensitive and may need to be delivered right away (e.g., a stock ticker update).
• Other files 20 are relatively time insensitive, and a delay of hours in delivery may be acceptable (e.g., a movie trailer).
• Each file stored on the remote server may be annotated Attorney Docket No. 19647-0012WO l with an "urgency" parameter 30, which may be assigned by a creator of the file (content) or determined based on some other policy.
• the client behaves as follows:
• the signal may come from the device itself, from the server 265, or from the end-user 255.
• the application performs these steps transparently to the user. That is, the user need not take any action to cause the steps to be performed and the user need not be made aware of any of the steps occurring.
• New files are delivered— hourly, daily, weekly— directly to the mobile device. No user action is required. This is similar to the behavior of a home Digital Video Recorder (DVR).
• DVR Digital Video Recorder
• the files can be stored on the device's file system.
• the files could be stored in the "My Documents" folder.
• the user can access them manually, using existing tools on the mobile device (e.g., a "File Manager” application on a Windows Mobile device).
• the client may include an application (figures 3, 4) that provides a user- friendly access to a list of
• a third way to initiate a sync is from the server.
• the client may be capable of receiving asynchronous messages directly from the server.
• a RIM Blackberry device provisioned to use a Blackberry Enterprise Server (BES) can receive signals directly from the server through an MDS component. Therefore, the client application need not continuously poll the server for new files, nor remain active. The application can, instead, be inactive until the server signal arrives and causes the device to launch the application.
• BES Blackberry Enterprise Server
• Voice and SMS traffic generate more revenue per bit to the owner of a mobile network than generic data traffic. Therefore, during daytime hours (e.g., 9AM-7PM), when voice and SMS traffic is high and spare capacity limited, network owners are likely to discourage network-intensive applications. On the other hand, most cellular networks are 'latent' during off-peak hours such as 9PM-6AM. During this time window, mobile network owners are likely to be more receptive to network- intensive applications.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=43449616

Family Applications (1)

Country Status (2)

Cited By (1)

Families Citing this family (1)

Family Cites Families (14)

• 2009
  • 2009-07-14 EP EP09847427.3A patent/EP2454675A4/de not_active Withdrawn
  • 2009-07-14 WO PCT/US2009/050568 patent/WO2011008199A1/en active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events