WO2007018714A1 - System and method for prioritizing transmission legs for precaching data - Google Patents

System and method for prioritizing transmission legs for precaching data Download PDF

Info

Publication number
WO2007018714A1
WO2007018714A1 PCT/US2006/021944 US2006021944W WO2007018714A1 WO 2007018714 A1 WO2007018714 A1 WO 2007018714A1 US 2006021944 W US2006021944 W US 2006021944W WO 2007018714 A1 WO2007018714 A1 WO 2007018714A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
priority
condition
leg
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2006/021944
Other languages
French (fr)
Inventor
Rangsan Leelahakriengkrai
John M. Harris
Ivan N. Vukovic
Fan Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Motorola Solutions Inc
Original Assignee
Motorola Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Motorola Inc filed Critical Motorola Inc
Publication of WO2007018714A1 publication Critical patent/WO2007018714A1/en
Priority to GB0800034A priority Critical patent/GB2441714A/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
    • H04W40/10—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources based on available power or energy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the field of the invention relates to routing communications through networks and, more specifically, to prioritizing traffic within these systems.
  • data may be transmitted from a Base Station Controller (BSC) to a Base Transceiver Site (BTS) and from the BTS to a mobile station.
  • BSC Base Station Controller
  • BTS Base Transceiver Site
  • Each BTS has an associated coverage area and the mobile stations may move between coverage areas of different BTSs.
  • data As data is transmitted across the network, it may also be stored at various locations for different purposes. For instance, data may be pre-cached at buffers at a BTS in order to be ready for use by a mobile station when the mobile station can utilize the data. When the mobile station is ready, the data is downloaded to the mobile station.
  • FIG. 1 is a block diagram of a system for prioritizing the transmission of data along transmission legs of a network according to the present invention
  • FIG. 2 is a flow chart illustrating one example of an approach for prioritizing the transmission legs of pre-cache data according to the present invention
  • FIG. 3 is a block diagram for of a device that prioritizes data along transmission legs of a network according to the present invention
  • FIG. 4 is a call-flow diagram of an approach for prioritizing the transmission of data along transmission legs of a network according to the present invention.
  • FIG. 5 is a flow chart illustrating one example of determining a priority of pre-cache data according to the present invention.
  • At least one transmission condition associated with making a transmission of pre-cache data over a transmission leg of a network is obtained.
  • a priority for transmitting the pre-cache data is then determined using the transmission condition.
  • Other types of priority information can be determined.
  • the determined priority in one approach, identifies which packets are to be pre-cached and to which BTSs these packets are to be eventually sent. In another approach, the priority defines a schedule for sending the pre-cache data to the BTS and an amount of packets to be transmitted.
  • transmission information is received that is related to a condition of a mobile station and this is used to set a priority.
  • This type of information may include the battery life of the mobile station, the location of the mobile station, the velocity of the mobile station, the direction of movement of the mobile station, the number of transmission legs with which the mobile station has established a connection, the volume of traffic at the mobile station, an indication that the time stayed on the transmission leg by the mobile station is high, the promotional plan used at the mobile station, whether the mobile station belongs to a high-priority group, the identity of a preferred application being run by the mobile station, or whether the mobile station is an 802.11 compatible access point (or compatible to a similar protocol).
  • transmission information is received that is related to a condition of a call and this is used to establish the priority. For instance, this information may include whether the call is an emergency call, the security level associated with the call, the identity of a premium application associated with a call, the identity of a streaming application, the identity of a delay-sensitive application, the identity of a file transmission over a primary transmission leg that is near the end of a file, the identity of a file transmission over a primary transmission leg that experiences excessive delay and times out, information indicating the received data rate is below a threshold, or whether the call is undergoing a handoff between different types of equipment.
  • the transmission condition is related to a condition of the user and this is used to set the priority.
  • this information may include whether the user is a premium user, the type of billing plan associated with the user, the type of equipment utilized by the user, or the frequency of network use by the user.
  • a system and method are described that prioritize data for transmission along the transmission legs in a network.
  • particular packets and transmission legs can be selected and a transmission schedule determined based upon a variety of transmission conditions related to the users, mobile stations, transmission legs, and/or other factors associated with a call.
  • These approaches are efficient, do not overload the resources of the system, and allow pre-caching to be used.
  • a network 102 is coupled to a Base Station Controller (BSC) 104.
  • the BSC 104 is coupled to Base Transceiver Stations (BTSs) 106 and 108.
  • BTSs Base Transceiver Stations
  • the BTSs 106 and 108 may be coupled to a mobile station 110.
  • Data is sent from the network 102 to be stored at the BSC 104.
  • a first transmission leg 112 exists from the BSC 104 to the BTS 106 and then to the mobile station 110.
  • a second transmission leg 114 exists from the BSC 104 to the BTS 108 and to the mobile station 110.
  • the later portion of either of the transmission legs 112 or 114 may be a radio link between the appropriate BTS 106 and 108 and the mobile station 110.
  • the other portions of the legs 112 or 114 may be wireless, hard- wired, or any other type of communication link.
  • Information related to the legs, the mobile stations, or from other entities is transmitted to the BSC 104 so that the BSC 104 can determine a priority.
  • the determined priority may identify the packets and/or the BTS 106 or 108 to which to send these packets.
  • the determined priority may also identify an amount of packets to send and/or a schedule to send these packets. Other types of priority information may also be determined.
  • at least one transmission condition associated with making a transmission of pre-cache data over a transmission leg 112 or 114 of a network is obtained by the BSC 104.
  • a priority for transmitting the pre-cache data is determined by the BSC 104 using the transmission condition.
  • the BSC 104 may obtain a variety of different transmission conditions in order to determine a priority.
  • transmission information that is related to a condition of one (or both) of the transmission legs 112 or 114 may be used to determine priority.
  • this information may be related to a condition of the transmission leg such as the amount of backhaul loading on the transmission leg 112 or 114, the time of day, the Radio Frequency (RF) delay on the transmission leg 112 or 114 and a time of day, whether the transmission leg 112 or 114 is a candidate for a group call, whether a signal strength is lower in the transmission leg 112 or 114 as compared to another transmission leg, an indication that a packet is of a high priority and has not been downloaded to a site, the amount of backhaul loading at a given time, an amount of Radio Frequency (RF) loading at a given time, an amount of Radio Access Network (RAN) loading at a given time, a buffer level on the transmission leg 112 or 114 and a buffer level
  • RF Radio Fre
  • the time of day is detected to be 11 :00 pm. Based upon the time of day, a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority. It will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible.
  • transmission information is received that is related to a condition of a mobile station 110 and this is used to determine the priority.
  • This type of information may include the battery life of the mobile station 110, the location of the mobile station 110, the velocity of the mobile station 110, the direction of movement of the mobile station 110, the number of transmission legs with which the mobile station 110 has established a connection, the volume of traffic at the mobile station 110, whether the time stayed on the transmission leg by the mobile station 110 is high, the promotional plan used at the mobile station 110, whether the mobile station 110 belongs to a high-priority group, the identity of a preferred application being run by the mobile station 110, or whether the mobile station is a 802.11 compatible access point (or compatible to a similar protocol).
  • transmission information is received that is related to a condition of a call and this is used to determine the priority. For instance, this information may include whether the call is an emergency call, the security level associated with the call, the identity of a premium application associated with a call, the identity of a streaming application, the identity of a delay-sensitive application, the identity of a file transmission over a primary transmission leg that is near the end of a file, the identity of a file transmission over a primary transmission leg that experiences excessive delay and times out, information indicating a received data rate is below a threshold, or whether a call is undergoing a handoff between different types of equipment.
  • a call is determined to be an emergency call. Based upon the nature of the call (emergency), a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority. Once again, it will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible.
  • the transmission condition is related to a condition of a user is used to determine the priority. For example, this information may include whether the user is a premium user, the type of bill plan associated with the user, the type of equipment utilized by the user, or the frequency of network use by the user.
  • a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority.
  • a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority.
  • transmission conditions are obtained.
  • these transmission conditions may include conditions related to the condition of the transmission leg, the condition of a user, the condition of a mobile station, or the condition of a call.
  • a priority is determined to transmit the data.
  • the determined priority may include the identity of packets within the pre-cache data and the identity of a base station to which to send the packets, hi another example, the amount of data to send may be determined.
  • a schedule may be obtained.
  • a single condition or combination of conditions obtained at step 202 may be used to make the priority determination.
  • the packets may be sent according to the priority.
  • a determined amount of packets (determined at step 204) are sent to a BTS (also identified at step 204).
  • the device 300 includes a controller 302, a receiver 304, and a transmitter 306.
  • the controller 302 is coupled to the receiver 304 and the transmitter 306, and is programmed to receive at the input of the receiver 304 a transmission condition or conditions 308 associated with making a transmission of pre-cache data using a transmission leg of a network.
  • the conditions may be related to the condition of the transmission leg, the condition of a user, the condition of a mobile station, or the condition of a call. Other examples of conditions are possible.
  • the controller 302 determines a priority 310 for transmitting the pre-cache data using the transmission conditions 308.
  • the determined priority 310 may, for example, include the identity of packets to be sent to a determined base station.
  • the determined priority 310 is based upon a condition or combination of conditions 308 received at the receiver 304.
  • transmission conditions are sent from a network element or elements to a BSC. These transmission conditions may include conditions related to a transmission leg, a user, a mobile station, or some other factor.
  • the BSC determines a priority.
  • the BSC may determine an identity of a BTS to send the pre- cache data, an identity of the packets to send to the BTS, an amount of packets to send to the BTS, or a schedule under which to send the pre-cache data to a BTS.
  • Other types of priority information may also be determined.
  • the data i.e., packets
  • the BTS has been identified at step 404 as has the amount of packets to be sent.
  • the priority may be re-determined. For example, after the passage of a variable or predetermined amount of time, at step 408, the priority is re- determined based on the same transmission conditions as described above as these conditions have changed over time.
  • step 410 the data is sent to a second BTS.
  • step 408 has determined a new BTS to which to the packets are to be sent as well as a new amount of packets to be sent.
  • the system includes two transmission legs A and B.
  • the system receives transmission conditions that are used to determine a priority. These include the time of day 504, the subscription status of a user 506, the data rate 510 on the "A" transmission leg, and the cell reselection rate 512 on the "B" transmission leg.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

At least one transmission condition associated with making a transmission of pre-cache data over a transmission leg (112 or 114) of a network is obtained. A priority for transmitting the pre-cache data is determined using the transmission condition.

Description

SYSTEM ANP METHOD FOR PRIORITIZING TRANSMISSION LEGS FOR
PRECACHING DATA
Field of the Invention
[0001] The field of the invention relates to routing communications through networks and, more specifically, to prioritizing traffic within these systems.
Background of the Invention
[0002] Data is transmitted between different entities in communication networks.
For instance, data may be transmitted from a Base Station Controller (BSC) to a Base Transceiver Site (BTS) and from the BTS to a mobile station. Each BTS has an associated coverage area and the mobile stations may move between coverage areas of different BTSs.
[0003] As data is transmitted across the network, it may also be stored at various locations for different purposes. For instance, data may be pre-cached at buffers at a BTS in order to be ready for use by a mobile station when the mobile station can utilize the data. When the mobile station is ready, the data is downloaded to the mobile station.
[0004] As mentioned, mobile stations often move between coverage areas of different BTSs. When pre-caching is being used, data that had been pre-cached needs to be forwarded to the new BTS associated with the mobile station. If large amounts of data are involved, some data may not reach the new BTS due to the reselection process.
[0005] Some previous systems attempted to solve these problems by employing data flooding techniques. In data flooding, a BSC sent a multicast transmission of the stored data to all potential BTSs in order to ensure reaching the mobile station. Although data flooding allowed the data to reach the mobile station, the use of flooding consumed valuable transmission bandwidth and usually took a long time to accomplish. Consequently, network resources often became overloaded causing delays and inconvenience to users.
[0006] In other previous approaches, data was pre-cached only after site reselection had occurred. While this approach avoided overloading the system's bandwidth, it delays the data downloading since the mobile station had to wait for the reselection to be completed before pre-caching could be used. This reduces the potential data download rate the mobile station can achieve.
Brief Description of the Drawings
[0007] FIG. 1 is a block diagram of a system for prioritizing the transmission of data along transmission legs of a network according to the present invention;
[0008] FIG. 2 is a flow chart illustrating one example of an approach for prioritizing the transmission legs of pre-cache data according to the present invention;
[0009] FIG. 3 is a block diagram for of a device that prioritizes data along transmission legs of a network according to the present invention;
[0010] FIG. 4 is a call-flow diagram of an approach for prioritizing the transmission of data along transmission legs of a network according to the present invention; and
[0011] FIG. 5 is a flow chart illustrating one example of determining a priority of pre-cache data according to the present invention.
[0012] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein.
Detailed Description of the Preferred Embodiments
[0013] A system and method is used to prioritize the transmission of pre-cache data along the transmission legs in a network. By prioritizing the transmission of the data, the system is not overloaded by the data transmissions and data can be pre-cached and used even as mobile stations move between different Base Transceiver Stations (BTSs).
[0014] In many of these embodiments, at least one transmission condition associated with making a transmission of pre-cache data over a transmission leg of a network is obtained. A priority for transmitting the pre-cache data is then determined using the transmission condition. Other types of priority information can be determined.
[0015] The determined priority, in one approach, identifies which packets are to be pre-cached and to which BTSs these packets are to be eventually sent. In another approach, the priority defines a schedule for sending the pre-cache data to the BTS and an amount of packets to be transmitted.
[0016] Different parameters may be used to determine the priority. For instance, transmission information that is related to a condition of the transmission leg may be received and used to determine the priority. This transmission information may include the amount of backhaul loading on the transmission leg, the time of day, the Radio Frequency (RF) delay on the transmission leg in combination with the time of day, whether the transmission leg is a candidate for a group call, whether the signal strength is lower in the transmission leg as compared to another transmission leg, indications that a packet is of a high priority and has not been downloaded to a site, the amount of backhaul loading at a given time, the amount of Radio Frequency (RF) loading at a given time, the amount of Radio Access Network (RAN) loading at a given time, the buffer level on a transmission leg and the buffer level at a playout buffer at a mobile station, the length of a cell reselection time on a transmission leg, whether extra buffer space exists, whether the transmission leg has a different associated base station controller as compared to the primary transmission leg, or the number of mobiles connected to the transmission leg.
[0017] In others of these embodiments, transmission information is received that is related to a condition of a mobile station and this is used to set a priority. This type of information may include the battery life of the mobile station, the location of the mobile station, the velocity of the mobile station, the direction of movement of the mobile station, the number of transmission legs with which the mobile station has established a connection, the volume of traffic at the mobile station, an indication that the time stayed on the transmission leg by the mobile station is high, the promotional plan used at the mobile station, whether the mobile station belongs to a high-priority group, the identity of a preferred application being run by the mobile station, or whether the mobile station is an 802.11 compatible access point (or compatible to a similar protocol).
[0018] In still others of these embodiments, transmission information is received that is related to a condition of a call and this is used to establish the priority. For instance, this information may include whether the call is an emergency call, the security level associated with the call, the identity of a premium application associated with a call, the identity of a streaming application, the identity of a delay-sensitive application, the identity of a file transmission over a primary transmission leg that is near the end of a file, the identity of a file transmission over a primary transmission leg that experiences excessive delay and times out, information indicating the received data rate is below a threshold, or whether the call is undergoing a handoff between different types of equipment.
[0019] In yet other embodiments, the transmission condition is related to a condition of the user and this is used to set the priority. For example, this information may include whether the user is a premium user, the type of billing plan associated with the user, the type of equipment utilized by the user, or the frequency of network use by the user.
[0020] Other conditions may also be used to determine priority and other actions may be taken. For instance, in some of these embodiments, data compression may be used to compress the pre-cache data on the transmission leg whenever a low priority for the at least transmission one leg is determined. In still others of these embodiments, it may be determined whether a number of mobile stations are likely to substantially simultaneously initiate a handoff and, responsively, the system may initiate pre-filling. The determination may be based upon information such as the number of previous handoffs that were made at substantially the same time by the number of mobile stations, information indicating the number of mobile stations are on a same conveyance, and information indicating that a traffic signal has changed which will result in a correlated handoff event.
[0021] Thus, a system and method are described that prioritize data for transmission along the transmission legs in a network. Conveniently, particular packets and transmission legs can be selected and a transmission schedule determined based upon a variety of transmission conditions related to the users, mobile stations, transmission legs, and/or other factors associated with a call. These approaches are efficient, do not overload the resources of the system, and allow pre-caching to be used.
[0022] Referring now to FIG. 1, one example of a system for prioritizing the transmission of pre-cache data is described. A network 102 is coupled to a Base Station Controller (BSC) 104. The BSC 104 is coupled to Base Transceiver Stations (BTSs) 106 and 108. The BTSs 106 and 108 may be coupled to a mobile station 110.
[0023] Data is sent from the network 102 to be stored at the BSC 104. A first transmission leg 112 exists from the BSC 104 to the BTS 106 and then to the mobile station 110. A second transmission leg 114 exists from the BSC 104 to the BTS 108 and to the mobile station 110. The later portion of either of the transmission legs 112 or 114 may be a radio link between the appropriate BTS 106 and 108 and the mobile station 110. The other portions of the legs 112 or 114 may be wireless, hard- wired, or any other type of communication link.
[0024] Information related to the legs, the mobile stations, or from other entities is transmitted to the BSC 104 so that the BSC 104 can determine a priority. The determined priority may identify the packets and/or the BTS 106 or 108 to which to send these packets. The determined priority may also identify an amount of packets to send and/or a schedule to send these packets. Other types of priority information may also be determined. [0025] In one example of the operation of the system of FIG. 1, at least one transmission condition associated with making a transmission of pre-cache data over a transmission leg 112 or 114 of a network is obtained by the BSC 104. A priority for transmitting the pre-cache data is determined by the BSC 104 using the transmission condition.
[0026] The BSC 104 may obtain a variety of different transmission conditions in order to determine a priority. For example, transmission information that is related to a condition of one (or both) of the transmission legs 112 or 114 may be used to determine priority. In some examples, this information may be related to a condition of the transmission leg such as the amount of backhaul loading on the transmission leg 112 or 114, the time of day, the Radio Frequency (RF) delay on the transmission leg 112 or 114 and a time of day, whether the transmission leg 112 or 114 is a candidate for a group call, whether a signal strength is lower in the transmission leg 112 or 114 as compared to another transmission leg, an indication that a packet is of a high priority and has not been downloaded to a site, the amount of backhaul loading at a given time, an amount of Radio Frequency (RF) loading at a given time, an amount of Radio Access Network (RAN) loading at a given time, a buffer level on the transmission leg 112 or 114 and a buffer level at a playout buffer at the mobile station 110, the length of a cell reselection time on a transmission leg 112 or 114, whether extra buffer space exists, whether the transmission leg 112 or 114 has a different associated base station controller than a primary leg, or a number of mobile stations connected to the transmission leg.
[0027] In one example of the application of these conditions, the time of day is detected to be 11 :00 pm. Based upon the time of day, a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority. It will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible.
[0028] In other examples, transmission information is received that is related to a condition of a mobile station 110 and this is used to determine the priority. This type of information may include the battery life of the mobile station 110, the location of the mobile station 110, the velocity of the mobile station 110, the direction of movement of the mobile station 110, the number of transmission legs with which the mobile station 110 has established a connection, the volume of traffic at the mobile station 110, whether the time stayed on the transmission leg by the mobile station 110 is high, the promotional plan used at the mobile station 110, whether the mobile station 110 belongs to a high-priority group, the identity of a preferred application being run by the mobile station 110, or whether the mobile station is a 802.11 compatible access point (or compatible to a similar protocol).
[0029] hi one example of the application of these conditions, the battery condition of the mobile station is determined to be low. Based upon this condition, a priority including the transmission leg 114, an amount of data (only some of the pending data), and a schedule (transmit at 12:00pm midnight) is determined and the data is transmitted along leg 114 according to this priority. Again, it will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible.
[0030] In still other examples, transmission information is received that is related to a condition of a call and this is used to determine the priority. For instance, this information may include whether the call is an emergency call, the security level associated with the call, the identity of a premium application associated with a call, the identity of a streaming application, the identity of a delay-sensitive application, the identity of a file transmission over a primary transmission leg that is near the end of a file, the identity of a file transmission over a primary transmission leg that experiences excessive delay and times out, information indicating a received data rate is below a threshold, or whether a call is undergoing a handoff between different types of equipment.
[0031] In one example of the application of these conditions, a call is determined to be an emergency call. Based upon the nature of the call (emergency), a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority. Once again, it will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible. [0032] In yet other examples, the transmission condition is related to a condition of a user is used to determine the priority. For example, this information may include whether the user is a premium user, the type of bill plan associated with the user, the type of equipment utilized by the user, or the frequency of network use by the user.
[0033] In one example of the application of these conditions, it is determined that the user is a premium user. Based upon the identity of the user, a priority including the transmission leg 114, an amount of data (all pending data), and a schedule (transmit immediately) is determined and the data is transmitted along leg 114 according to this priority. Again, it will be appreciated that other examples of determining this priority and applying this priority to transmit data are possible.
[0034] Referring now to FIG. 2, one example of an approach for prioritizing the transmission of pre-cache data is described. At step 202, transmission conditions are obtained. For example, these transmission conditions may include conditions related to the condition of the transmission leg, the condition of a user, the condition of a mobile station, or the condition of a call. At step 204, a priority is determined to transmit the data. The determined priority may include the identity of packets within the pre-cache data and the identity of a base station to which to send the packets, hi another example, the amount of data to send may be determined. In still another example, a schedule may be obtained. A single condition or combination of conditions obtained at step 202 may be used to make the priority determination.
[0035] At step 206, the packets may be sent according to the priority. In one example, a determined amount of packets (determined at step 204) are sent to a BTS (also identified at step 204).
[0036] Referring now to FIG. 3, one example of a device 300 for determining the priority by which to transmit pre-cache data is described. The device 300 includes a controller 302, a receiver 304, and a transmitter 306. The controller 302 is coupled to the receiver 304 and the transmitter 306, and is programmed to receive at the input of the receiver 304 a transmission condition or conditions 308 associated with making a transmission of pre-cache data using a transmission leg of a network. As mentioned above, the conditions may be related to the condition of the transmission leg, the condition of a user, the condition of a mobile station, or the condition of a call. Other examples of conditions are possible.
[0037] The controller 302 determines a priority 310 for transmitting the pre-cache data using the transmission conditions 308. The determined priority 310 may, for example, include the identity of packets to be sent to a determined base station. The determined priority 310 is based upon a condition or combination of conditions 308 received at the receiver 304.
[0038] Referring now to FIG. 4, one example of an approach for prioritizing the transmission of pre-cache data is described. At step 402, transmission conditions are sent from a network element or elements to a BSC. These transmission conditions may include conditions related to a transmission leg, a user, a mobile station, or some other factor.
[0039] At step 404, the BSC determines a priority. In determining a priority to transmit the pre-cache data, the BSC may determine an identity of a BTS to send the pre- cache data, an identity of the packets to send to the BTS, an amount of packets to send to the BTS, or a schedule under which to send the pre-cache data to a BTS. Other types of priority information may also be determined.
[0040] At step 406, the data (i.e., packets) is sent to a BTS according to the priority. In this case, the BTS has been identified at step 404 as has the amount of packets to be sent.
[0041] At a later time, the priority may be re-determined. For example, after the passage of a variable or predetermined amount of time, at step 408, the priority is re- determined based on the same transmission conditions as described above as these conditions have changed over time.
[0042] At step 410, the data is sent to a second BTS. In this case, step 408 has determined a new BTS to which to the packets are to be sent as well as a new amount of packets to be sent.
[0043] Referring now to FIG. 5, one example of an approach for using a transmission condition to determine a priority is described. In this example, the system includes two transmission legs A and B. At step 502, the system receives transmission conditions that are used to determine a priority. These include the time of day 504, the subscription status of a user 506, the data rate 510 on the "A" transmission leg, and the cell reselection rate 512 on the "B" transmission leg.
[0044] At step 514, the system determines the identity of the base station based upon factor 504. At step 516, the system determines the identity of the packets to be sent based upon the factors 506. At step 518, the system determines the total amount of packets to be sent based upon the factors 510 and 512. Those skilled in the art will realize that various algorithms and/or approaches may be used to implement steps 514, 516, and 518. For example, for step 504, if a call is to be made in the afternoon, a first base station may be selected while if the call is to be made in the afternoon, a second base station may be selected.
[0045] It will also be understood that the example given with respect to FIG. 5 is only one possible example. Thus, other types of priority information may be determined and different combinations of characteristics may be used to determine the priority information.
[0046] Thus, a system and method are given that prioritize data for transmission along transmission legs in a network. Conveniently, particular packets and transmission legs can be selected and the transmission schedule based upon a variety of transmission conditions related to the users, mobile stations, transmission legs, and/or other factors associated with a call. These approaches are efficient and do not overload the resources of the system.
[0047] Those skilled in the art will recognize that a wide variety of modifications, alterations, and combinations can be made with respect to the above described embodiments without departing from the spirit and scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the scope of the invention.

Claims

What Is Claimed Is:
1. A method of assigning a priority to a transmission leg in a network comprising: obtaining at least one transmission condition associated with making a transmission of pre-cache data over a transmission leg of a network; and determining a priority for transmitting the pre-cache data using the at least one transmission condition.
2. The method of claim 1 further comprising scheduling the sending of the pre-cache data to the base station according to the priority.
3. The method of claim 1 further comprising determining an amount of packets to be transmitted to the base station based upon the priority.
4. The method of claim 3 wherein determining an amount comprises determining an amount that is related to a data rate of the transmission leg and a cell reselection time associated with the transmission leg.
5. The method of claim 1 wherein obtaining the at least one transmission condition comprises receiving transmission information that is related to one or more of a condition of the transmission leg, a condition of a mobile station, a condition of a user, and a condition of a call.
6. The method of claim 1 further comprising applying data compression to the pre-cache data on the transmission leg whenever a low priority for the at least transmission one leg is determined.
7. The method of claim 1 further comprising determining whether a number of mobile stations are likely to substantially simultaneously initiate a handoff and, responsively, to initiate pre-filling.
8. A device for determining a priority for transmitting data on a transmission leg of a network comprising: a receiver having an input; a transmitter having an output; and a controller coupled to the receiver and the transmitter, the controller programmed to receive at the input of the receiver at least one transmission condition associated with making a transmission of pre-cache data using a transmission leg of a network and to determine a priority for transmitting the pre-cache data using the at least one transmission condition.
9. The device of claim 8 wherein the at least one transmission condition is selected from a group comprising: a condition of the transmission leg; a condition of a user; a condition of a mobile station; and a condition of a call.
10. A system for prioritizing the transmission legs of a network comprising: at least one base station; and a base station controller coupled to the at least one base station, the base station controller programmed to obtain at least one transmission condition associated with making a transmission of pre-cache data via a transmission leg in a network and to determine a priority for transmitting the pre-cache data using the at least one transmission condition.
11. The system of claim 10 wherein the base station controller is further programmed to send the pre-cache data to the at least one base station according to the priority.
PCT/US2006/021944 2005-07-26 2006-06-06 System and method for prioritizing transmission legs for precaching data Ceased WO2007018714A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
GB0800034A GB2441714A (en) 2005-07-26 2008-01-02 System and method for prioritizing transmission legs for precaching data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/189,468 US20070025304A1 (en) 2005-07-26 2005-07-26 System and method for prioritizing transmission legs for precaching data
US11/189,468 2005-07-26

Publications (1)

Publication Number Publication Date
WO2007018714A1 true WO2007018714A1 (en) 2007-02-15

Family

ID=37694182

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/021944 Ceased WO2007018714A1 (en) 2005-07-26 2006-06-06 System and method for prioritizing transmission legs for precaching data

Country Status (4)

Country Link
US (1) US20070025304A1 (en)
KR (1) KR20080028969A (en)
GB (1) GB2441714A (en)
WO (1) WO2007018714A1 (en)

Families Citing this family (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050055426A1 (en) * 2000-06-12 2005-03-10 Kim Smith System, method and computer program product that pre-caches content to provide timely information to a user
US8578480B2 (en) * 2002-03-08 2013-11-05 Mcafee, Inc. Systems and methods for identifying potentially malicious messages
US20060015942A1 (en) 2002-03-08 2006-01-19 Ciphertrust, Inc. Systems and methods for classification of messaging entities
US8561167B2 (en) * 2002-03-08 2013-10-15 Mcafee, Inc. Web reputation scoring
US7296129B2 (en) 2004-07-30 2007-11-13 International Business Machines Corporation System, method and storage medium for providing a serialized memory interface with a bus repeater
US7389375B2 (en) * 2004-07-30 2008-06-17 International Business Machines Corporation System, method and storage medium for a multi-mode memory buffer device
US7539800B2 (en) 2004-07-30 2009-05-26 International Business Machines Corporation System, method and storage medium for providing segment level sparing
US7305574B2 (en) 2004-10-29 2007-12-04 International Business Machines Corporation System, method and storage medium for bus calibration in a memory subsystem
US20060095620A1 (en) * 2004-10-29 2006-05-04 International Business Machines Corporation System, method and storage medium for merging bus data in a memory subsystem
US7512762B2 (en) * 2004-10-29 2009-03-31 International Business Machines Corporation System, method and storage medium for a memory subsystem with positional read data latency
US7331010B2 (en) * 2004-10-29 2008-02-12 International Business Machines Corporation System, method and storage medium for providing fault detection and correction in a memory subsystem
US7395476B2 (en) * 2004-10-29 2008-07-01 International Business Machines Corporation System, method and storage medium for providing a high speed test interface to a memory subsystem
US7277988B2 (en) * 2004-10-29 2007-10-02 International Business Machines Corporation System, method and storage medium for providing data caching and data compression in a memory subsystem
US7356737B2 (en) * 2004-10-29 2008-04-08 International Business Machines Corporation System, method and storage medium for testing a memory module
US7441060B2 (en) * 2004-10-29 2008-10-21 International Business Machines Corporation System, method and storage medium for providing a service interface to a memory system
US7299313B2 (en) * 2004-10-29 2007-11-20 International Business Machines Corporation System, method and storage medium for a memory subsystem command interface
US8635690B2 (en) 2004-11-05 2014-01-21 Mcafee, Inc. Reputation based message processing
US7478259B2 (en) * 2005-10-31 2009-01-13 International Business Machines Corporation System, method and storage medium for deriving clocks in a memory system
US7685392B2 (en) * 2005-11-28 2010-03-23 International Business Machines Corporation Providing indeterminate read data latency in a memory system
US7636813B2 (en) * 2006-05-22 2009-12-22 International Business Machines Corporation Systems and methods for providing remote pre-fetch buffers
US7640386B2 (en) * 2006-05-24 2009-12-29 International Business Machines Corporation Systems and methods for providing memory modules with multiple hub devices
US7594055B2 (en) 2006-05-24 2009-09-22 International Business Machines Corporation Systems and methods for providing distributed technology independent memory controllers
US7584336B2 (en) * 2006-06-08 2009-09-01 International Business Machines Corporation Systems and methods for providing data modification operations in memory subsystems
US7493439B2 (en) 2006-08-01 2009-02-17 International Business Machines Corporation Systems and methods for providing performance monitoring in a memory system
US7669086B2 (en) * 2006-08-02 2010-02-23 International Business Machines Corporation Systems and methods for providing collision detection in a memory system
US7581073B2 (en) 2006-08-09 2009-08-25 International Business Machines Corporation Systems and methods for providing distributed autonomous power management in a memory system
US7587559B2 (en) 2006-08-10 2009-09-08 International Business Machines Corporation Systems and methods for memory module power management
US7539842B2 (en) 2006-08-15 2009-05-26 International Business Machines Corporation Computer memory system for selecting memory buses according to physical memory organization information stored in virtual address translation tables
US7490217B2 (en) 2006-08-15 2009-02-10 International Business Machines Corporation Design structure for selecting memory busses according to physical memory organization information stored in virtual address translation tables
JP4905007B2 (en) * 2006-09-12 2012-03-28 富士通株式会社 Uplink communication method and radio terminal in radio communication system
US7870459B2 (en) 2006-10-23 2011-01-11 International Business Machines Corporation High density high reliability memory module with power gating and a fault tolerant address and command bus
US7477522B2 (en) 2006-10-23 2009-01-13 International Business Machines Corporation High density high reliability memory module with a fault tolerant address and command bus
US7721140B2 (en) 2007-01-02 2010-05-18 International Business Machines Corporation Systems and methods for improving serviceability of a memory system
US7779156B2 (en) 2007-01-24 2010-08-17 Mcafee, Inc. Reputation based load balancing
US8763114B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Detecting image spam
US8214497B2 (en) 2007-01-24 2012-07-03 Mcafee, Inc. Multi-dimensional reputation scoring
US7606988B2 (en) * 2007-01-29 2009-10-20 International Business Machines Corporation Systems and methods for providing a dynamic memory bank page policy
US7603526B2 (en) 2007-01-29 2009-10-13 International Business Machines Corporation Systems and methods for providing dynamic memory pre-fetch
KR100958191B1 (en) * 2007-02-06 2010-05-17 엘지전자 주식회사 A data transmission method considering the number of terminals participating in multicast, a base station and a terminal for wireless communication for the same, and a wireless communication system
US8185930B2 (en) 2007-11-06 2012-05-22 Mcafee, Inc. Adjusting filter or classification control settings
US20090125980A1 (en) * 2007-11-09 2009-05-14 Secure Computing Corporation Network rating
US8589503B2 (en) * 2008-04-04 2013-11-19 Mcafee, Inc. Prioritizing network traffic
EP2244516B1 (en) * 2009-04-23 2016-05-18 Alcatel Lucent Relaying data between a base station and user equipment
US8761727B2 (en) * 2009-11-06 2014-06-24 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for pre-caching in a telecommunication system
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
WO2013025146A2 (en) * 2011-08-17 2013-02-21 Telefonaktiebolaget L M Ericsson (Publ) Method and controlling network node in a radio access network
EP2772013B1 (en) * 2011-10-27 2021-03-17 Telefonaktiebolaget LM Ericsson (publ) Caching in wireless communication networks
US9497682B2 (en) * 2013-06-07 2016-11-15 Intel Corporation Central processing unit and methods for supporting coordinated multipoint transmission in an LTE network
US11386183B2 (en) * 2020-08-06 2022-07-12 Microstrategy Incorporated Systems and methods for predictive caching
KR20220027551A (en) * 2020-08-27 2022-03-08 삼성전자주식회사 Apparatus and method for optimizing buffer size in dual connectivity
EP4211836B1 (en) * 2020-09-10 2024-07-31 Nokia Technologies Oy Burst transmission of data packets with feedback

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010018346A1 (en) * 1999-12-28 2001-08-30 Ntt Docomo, Inc. Method and apparatus for stabilizing communication in mobile communication system
US20040017860A1 (en) * 2002-07-29 2004-01-29 Jung-Tao Liu Multiple antenna system for varying transmission streams
US20050018613A1 (en) * 2003-05-30 2005-01-27 Kyocera Corporation Communication system switching method, and terminal device using this method
US20050289515A1 (en) * 2000-11-10 2005-12-29 Renesas Technology Corp. Data processor

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5923650A (en) * 1997-04-08 1999-07-13 Qualcomm Incorporated Method and apparatus for reverse link rate scheduling
US7319667B1 (en) * 2000-11-15 2008-01-15 Cisco Technology, Inc. Communication system with priority data compression
US6807426B2 (en) * 2001-04-12 2004-10-19 Qualcomm Incorporated Method and apparatus for scheduling transmissions in a communication system
US20040228349A1 (en) * 2003-01-10 2004-11-18 Sophie Vrzic Semi-distributed scheduling scheme for the reverse link of wireless systems

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010018346A1 (en) * 1999-12-28 2001-08-30 Ntt Docomo, Inc. Method and apparatus for stabilizing communication in mobile communication system
US20050289515A1 (en) * 2000-11-10 2005-12-29 Renesas Technology Corp. Data processor
US20040017860A1 (en) * 2002-07-29 2004-01-29 Jung-Tao Liu Multiple antenna system for varying transmission streams
US20050018613A1 (en) * 2003-05-30 2005-01-27 Kyocera Corporation Communication system switching method, and terminal device using this method

Also Published As

Publication number Publication date
GB0800034D0 (en) 2008-02-13
GB2441714A8 (en) 2008-03-20
US20070025304A1 (en) 2007-02-01
KR20080028969A (en) 2008-04-02
GB2441714A (en) 2008-03-12

Similar Documents

Publication Publication Date Title
US20070025304A1 (en) System and method for prioritizing transmission legs for precaching data
CN110856222B (en) A method and device for flow control
CN111970719B (en) Method and device for evaluating quality of anchor point station in 5G NSA network
JP5190547B2 (en) Congestion flag generation method based on measurement system load
US20130065633A1 (en) Access points selection apparatus and methods
CN112136338A (en) Wireless communication device and method
US20020167926A1 (en) Apparatus and method for controlling packet data transmission between BSC and BTS
US20040097191A1 (en) Controlling channel switching in a umts network
EP2067314A1 (en) Resource allocation in wireless communications system
WO2007117861A2 (en) Repeater for multiple radio access
US7583969B2 (en) Method of communication
EP2594104A1 (en) Dynamic optimization of radio network resources based on user equipment type smartphone
CN108029158A (en) System and method for data reporting reception state
CN119563339A (en) Enhanced configuration options for Layer 1/Layer 2 triggered mobility
US20170027016A1 (en) Communication device, wireless communication device, and communication method
US20050250504A1 (en) Channel setup in a wireless communication network
JP2020188472A (en) Feedback for RAN-assisted rate adaptation
EP1868395A1 (en) Network selection
US20030096619A1 (en) Data transmission in a telecommunications network
US20040202129A1 (en) Method, network nodes and system for sending data in a mobile communication network
KR101735317B1 (en) Method and apparatus for allocating resource of base station in mobile communication system
CN101127935B (en) A mobile communications system and communication branch establishing method
US10813110B2 (en) Method and apparatus for scheduling terminal radio resources
CN110830950A (en) Mode configuration and switching method of vehicle-mounted terminal
EP3114868B1 (en) Methods and devices for managing connectivity for a service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref document number: 0800034

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20060606

WWE Wipo information: entry into national phase

Ref document number: 0800034.1

Country of ref document: GB

WWE Wipo information: entry into national phase

Ref document number: 1020087002119

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06772313

Country of ref document: EP

Kind code of ref document: A1