WO2006057906A2 - Method and apparatus for mitigating the impact of receiving unsolicited packets at a wireless device - Google Patents
Method and apparatus for mitigating the impact of receiving unsolicited packets at a wireless device Download PDFInfo
- Publication number
- WO2006057906A2 WO2006057906A2 PCT/US2005/041845 US2005041845W WO2006057906A2 WO 2006057906 A2 WO2006057906 A2 WO 2006057906A2 US 2005041845 W US2005041845 W US 2005041845W WO 2006057906 A2 WO2006057906 A2 WO 2006057906A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- unsolicited
- received
- wireless device
- inactivity timer
- Prior art date
Links
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
- H04B1/06—Receivers
- H04B1/16—Circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
-
- 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/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0238—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is an unwanted signal, e.g. interference or idle signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
-
- 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 present disclosure relates generally to communication, and more specifically to techniques for processing Internet Protocol (IP) packets at a wireless device.
- IP Internet Protocol
- Wireless communication networks are widely deployed to provide various communication services such as voice, packet data, and so on.
- a wireless device may obtain data service from a wireless network by using IP over an air-link interface employed by the wireless network.
- the wireless device may establish a data session with a network entity and exchange data with other entities coupled to the wireless network via the Internet or some other network.
- the wireless device may operate in an active state or a dormant state at any given moment during the data session.
- the wireless device may be active for only a portion of the time during the data session, which may be opened for an extended period of time.
- the wireless device may transmit and/or receive packet data in short bursts and may remain in dormancy for significant periods of time between these data bursts.
- Dormancy refers to a scenario in which the data session is opened but radio resources are released.
- the wireless device may power down as much circuitry as possible while in dormancy.
- the wireless device may only wake up periodically to receive (1) page messages that alert the wireless device to the presence of an incoming call or packet data and (2) overhead messages that carry system and other information for the wireless device.
- the wireless device may receive unsolicited IP packets from the wireless network while in dormancy.
- An unsolicited IP packet may be defined as an IP packet that is not requested by the wireless device and further has no corresponding application or service running at the wireless device.
- the reception of an IP packet while in dormancy typically causes the wireless device to re-establish traffic channels with the wireless network and remain in the active state for some period of time. If the received IP packet is an unsolicited IP packet, then the wireless device typically drops the IP packet and/or sends a reset packet and takes no further action.
- the unsolicited IP packet does not trigger an exchange of data with the wireless network. Instead, the unsolicited IP packet wastes system resources since traffic channels are established but not used for exchanging data.
- the unsolicited IP packet further consumes battery power and shortens standby time since the wireless device is turned on and ready for wireless communication as a result of receiving this IP packet.
- an IP packet received at the wireless device may be deemed as an unsolicited IP packet if the received IP packet (1) causes the wireless device to reactivate from dormancy (e.g., transition from the dormant state to the active state), (2) is not delivered to an application or a service running at the wireless device, (3) results in no reply or a single "reject" reply by the wireless device, or (4) satisfies some other condition or criterion.
- the wireless device initiates dormancy early for unsolicited IP packets.
- the wireless device receives an IP packet from the wireless network and determines whether the received IP packet is an unsolicited IP packet. The wireless device transitions to dormancy early if the received IP packet is deemed to be an unsolicited IP packet and no other events prevent transition to dormancy.
- the wireless device may use various mechanisms for transitioning to dormancy early.
- the wireless device may maintain an inactivity timer while in the active state during the data session.
- the wireless device may reset the inactivity timer upon receiving or sending an IP packet and may transition to dormancy upon expiration of the inactivity timer.
- the inactivity timer may be operated with multiple timer values to mitigate the impact of unsolicited IP packets.
- a received IP packet that causes reactivation from dormancy is deemed to be an unsolicited IP packet and results in the use of a shortened value for the inactivity timer for a predetermined time duration.
- a nominal value is used for the inactivity timer after this time duration.
- the shortened value allows the wireless device to go dormant early if reactivation was due to an unsolicited IP packet.
- FIG. 1 shows an exemplary wireless deployment.
- FIG. 2 shows an exemplary protocol stack.
- FIG. 3 shows an embodiment of a wireless device.
- FIG. 4 shows a process for transitioning to dormancy early for unsolicited IP packets.
- FIG. 5 illustrates the use of two values for the inactivity timer.
- FIG. 6 shows a process for operating the inactivity timer with multiple values.
- FIG. 7 shows a process for selectively resetting the inactivity timer.
- FIG. 8 shows a block diagram of the wireless device.
- the techniques described herein to identify unsolicited IP packets and to initiate dormancy early may be used for various wireless networks.
- CDMA Code Division Multiple Access
- UMTS Universal Mobile Telecommunications System
- LAN wireless local area network
- a CDMA network may implement a radio access technology (RAT) such as cdma2000 and a networking protocol such as ANSI-41.
- RAT radio access technology
- a UMTS network may implement a RAT such as Wideband-CDMA (W-CDMA) and/or Global System for Mobile Communications (GSM) and a networking protocol such as GSM Mobile Application Part (GSM-MAP).
- W-CDMA Wideband-CDMA
- GSM Global System for Mobile Communications
- GSM-MAP GSM Mobile Application Part
- a wireless LAN provides communication coverage for a limited geographic area and may be an IEEE 802.11 network, a Bluetooth personal area network (BT-PAN), and so on.
- BT-PAN Bluetooth personal area network
- the techniques described herein may be used for a wireless wide area network (e.g., a CDMA or UMTS network) or a wireless LAN (e.g., an IEEE 802.11 network or a BT-PAN).
- FIG. 1 shows a deployment 100 in which a wireless device 120 communicates with a wireless network 130 to obtain communication services.
- Wireless device 120 may also be called a mobile station (MS), a user equipment (UE), a user terminal, a subscriber unit, or some other terminology.
- MS mobile station
- UE user equipment
- subscriber unit or some other terminology.
- Wireless network 130 includes a base station 142, a packet data entity 144, and an IP gateway 150.
- Base station 142 provides radio communication for wireless device 120.
- Packet data entity 144 controls the transmission of packets between base station 142 and IP gateway 150.
- IP gateway 150 supports data service for wireless devices in wireless network 130. For example, IP gateway 150 may be responsible for the establishment, maintenance, and termination of data sessions for the wireless devices and may further assign dynamic IP addresses to the wireless devices.
- IP gateway 150 may couple to a data network 160a, the Internet 160b, and/or other data networks. IP gateway 150 can communicate with various entities (e.g., a remote host 170) that couple to these data networks.
- Wireless network 130 may also be viewed as being composed of a radio network 140 and a packet data network.
- Radio network 140 includes base station 142 and packet data entity 144 and supports radio communication.
- the packet data network includes IP gateway 150 and supports packet-switched communication between radio network 140 and external data networks.
- Wireless network 130 may be a CDMA network, in which case packet data entity 144 is called a Packet Control Function (PCF) and IP gateway 150 is called a Packet Data Serving Node (PDSN).
- PCF Packet Control Function
- PDSN Packet Data Serving Node
- Wireless network 130 may also be a UMTS network, in which case packet data entity 144 is called a Serving GPRS Support Node (SGSN) and IP gateway 150 is called a Gateway GPRS Support Node (GGSN).
- Wireless network 130 may also be a wireless LAN.
- FIG. 2 shows an exemplary protocol stack 200 for data communication between wireless device 120 and remote host 170 via wireless network 130.
- the protocol stack includes a transport layer, a network layer, a link layer, and a physical layer.
- Wireless device 120 and remote host 170 may communicate using Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or some other protocol at the transport layer.
- TCP and UDP typically operate on top of IP at the network layer.
- Transport layer data is encapsulated in IP packets, which are exchanged between wireless device 120 and remote host 170 via radio network 140 and IP gateway 150.
- the link layer between wireless device 120 and wireless network 130 is typically dependent on the wireless network technology.
- the link layer is implemented with a Point-to-Point Protocol (PPP) over a Radio Link Protocol (RLP).
- Wireless device 120 maintains a PPP session with IP gateway 150 for a data session and communicates with radio network 140 via RLP for data exchanges.
- RLP operates on top of an air-link interface (e.g., cdma2000).
- Radio network 140 communicates with IP gateway 150 via a technology-dependent interface (e.g., an "R- P" interface for a CDMA network) that operates on top of a physical layer.
- IP gateway 150 communicates with remote host 170 via IP over a link layer and a physical layer.
- the various layers may be different for other wireless networks.
- FIG. 3 shows an embodiment of wireless device 120.
- applications and services 320 execute over sockets 322 and a data protocol stack 324.
- a socket is one endpoint of a two-way communication path between two applications running on a network.
- a socket is associated with an IP address, a protocol at the transport layer (e.g., TCP or UDP), and a port number for the transport layer protocol.
- Each application running at wireless device 120 is associated with one or more sockets and exchanges data with external entities via the associated sockets.
- Each service e.g., FTP, Telnet, and so on
- data protocol stack 324 utilizes TCP and/or UDP operating on top of IP.
- a data protocol stack may implement any combination of protocols for any number of layers.
- Wireless device 120 communicates with wireless network 130 via a Um interface 328a and may further communicate with a terminal equipment via an Rm interface 328b.
- the terminal equipment may be a laptop computer, a personal digital assistant (PDA), or some other computing device.
- PDA personal digital assistant
- Wireless device 120 may have an open data session with IP gateway 150 but may exchange data sporadically. During the data session, the wireless device may enter the active state when there is data to exchange (e.g., send or receive) and may enter the dormant state when there is no data to exchange. The wireless device transitions between the active and dormant states depending on data activity. [0029] Wireless device 120 communicates with radio network 140 in order to exchange data with IP gateway 150 and remote host 170. hi the active state, wireless device 120 may establish (1) a forward link traffic channel used to receive data from radio network 140 and (2) a reverse link traffic channel used to send data to radio network 140.
- a forward link traffic channel used to receive data from radio network 140
- a reverse link traffic channel used to send data to radio network 140.
- Wireless device 120 may receive an IP packet from wireless network 130 while in the dormant state.
- the received IP packet reactivates the wireless device from dormancy and causes the wireless device to reestablish the traffic channels for the forward and/or reverse links in anticipation of possible exchange of data with the wireless network.
- the wireless device typically drops the BP packet and/or sends a TCP reset packet and performs no other action, hi this case, it is desirable to release the traffic channels and transition back to dormancy early.
- FIG. 4 shows a flow diagram of a process 400 for transitioning to dormancy early for unsolicited IP packets.
- an IP packet is received from the wireless network (block 412).
- a determination is made whether the received IP packet is an unsolicited IP packet (block 414). This determination may be made based on various criteria.
- the wireless device transitions to dormancy early if the received D? packet is deemed to be an unsolicited D? packet and no other events prevent transition to dormancy, e.g., no other activity occurs (block 416).
- the early transition to dormancy may be achieved in various manners. Several embodiments for transitioning to dormancy early based on an inactivity timer are described below.
- Wireless device 120 may maintain an inactivity timer while in the active state.
- the inactivity timer determines the amount of time to remain in the active state without exchanging any data.
- the wireless device may reset the inactivity timer to a nominal value upon receiving or sending an IP packet and may enter the dormant state when the inactivity timer expires.
- the inactivity timer allows the wireless device to release the traffic channels when data is not being exchanged, thus saving radio resources.
- the nominal value for the inactivity timer is typically selected to provide good performance for expected data usage.
- a short inactivity timer value may result in the wireless device being timed-out and entering dormancy too quickly, which may result in loss of data, e.g., due to a delayed response from a remote server.
- a long inactivity timer value may result in the wireless device maintaining the traffic channels for too long without exchanging any data, thereby wasting radio resources.
- the nominal value is typically selected based on a tradeoff between these two factors. A nominal value of around 20 seconds has been found to provide good performance under certain data usage scenarios.
- the wireless device may receive an unsolicited IP packet while in dormancy.
- the unsolicited IP packet results in reactivation of the wireless device and sets the inactivity timer to the nominal value.
- the wireless device would then need to wait until the inactivity timer expires before transitioning back to dormancy and releasing the traffic channels.
- the inactivity timer is operated with multiple values to mitigate the impact of receiving unsolicited IP packets.
- a shortened value (which is shorter than the nominal value) may be used for the inactivity timer when the wireless device is reactivated from dormancy. The shortened value allows the wireless device to go back to dormancy and release the traffic channels earlier if the reactivation was due to an unsolicited IP packet.
- the nominal value may be used for the inactivity timer when the wireless device is exchanging data with the wireless network. The nominal value allows the wireless device to achieve the desired behavior in terms of the two factors noted above. The shortened value may be selected to achieve good performance, e.g., for the two factors noted above.
- the nominal value may be 20 seconds, and the shortened value may be 5 seconds.
- the shortened value may also be a configurable value that is selected based on typical patterns for unsolicited traffic, network behavior, and so on.
- the configurable shortened value may also be restricted to be within a predetermined range of values, e.g., from one to five seconds.
- FIG. 5 illustrates the use of the shortened and nominal values for the inactivity timer, in accordance with an embodiment.
- the shortened value is used for a predetermined time duration after the wireless device is reactivated from dormancy, which is called the wait period, and the nominal value is used after this wait period.
- the wait period may be a fixed value that is selected to provide good performance.
- the wait period may be equal to the shortened value or the nominal value.
- the wait period may be a configurable value that is selected based on the typical patterns for unsolicited traffic.
- a wait timer may be used to keep track of the elapsed time for when the shortened value is used.
- the wireless device can (1) treat network originated traffic and mobile originated traffic in the same manner and (2) provide the same behavior for both types of traffic in term of when inactivity should result in dormancy and release of the traffic channels.
- FIG. 6 shows a flow diagram of a process 600 for operating the inactivity timer with multiple values.
- an IP packet is received from the wireless network (block 612).
- a determination is made whether the received IP packet causes the wireless device to reactivate from dormancy (block 614). If the answer is 'Yes', then the inactivity timer value is set equal to the shortened value (block 616) and the wait timer is reset to the wait period (block 618). Otherwise, if the answer is 'No' for block 614, then the inactivity timer value is set equal to the nominal value (block 620).
- the inactivity timer is then reset to the current inactivity timer value, which may be the shortened value or the nominal value depending on whether the wireless device was reactivated from dormancy by the received IP packet (block 622).
- the inactivity timer and the wait timer each count down or up after being reset and expire upon reaching the value loaded in the timer.
- the wireless device initiates dormancy and releases the traffic channels (block 628). The process then terminates.
- the inactivity timer value may be set equal to the nominal value when the wireless device goes dormant for any reason. This ensures that the nominal value is used if the wireless device thereafter sends an IP packet to the wireless network.
- a received IP packet that causes reactivation from dormancy also results in the shortened value being used for the inactivity timer. If the received IP packet is an unsolicited IP packet (e.g., an MS RPC packet) and no other IP packets are exchanged thereafter, then the wireless device initiates dormancy after the shortened period has elapsed and the inactivity timer expires. This early transition to dormancy reduces the amount of time the traffic channels are unnecessarily established. For example, if the nominal value is 20 seconds and the shortened value is 5 seconds, then dormancy rriay be initiated up to 15 seconds earlier.
- an unsolicited IP packet e.g., an MS RPC packet
- the early dormancy conserves both radio resources for the wireless network and battery power for the wireless device. Conversely, if the received IP packet is a valid IP packet, then other IP packets may be exchanged thereafter and the inactivity timer would be reset after each IP packet exchange. If the wireless device does not go dormant for the entire wait period, then the nominal value is used for the inactivity timer. The wireless device would then operate in the same manner as in the conventional case.
- Process 600 relies on assumptions that (1) unsolicited IP packets are received sporadically, so that the inactivity timer is not continually reset by inbound unsolicited IP packets, and (2) subsequent IP packets are not exchanged in response to receiving unsolicited IP packets, so that the inactivity timer is not reset by outbound IP packets.
- Process 600 is simple to implement. However, performance is dependent on the accuracy of the underlying assumptions.
- FIG. 6 shows a specific embodiment in which two values are used for the inactivity timer, and the shortened value is used for the entire wait period.
- the shortened value is used whenever a received IP packet causes reactivation from dormancy, and the nominal value is used once a valid IP packet is received or sent.
- a received IP packet may be deemed to be a valid IP packet if, e.g., it is delivered to an application or a service running at the wireless device.
- the wait timer is not needed for this embodiment, hi yet another embodiment, the shortened value is used for the wait duration or until a valid IP packet is received, whichever occurs first. For this embodiment, the wait timer effectively expires upon receiving the valid IP packet.
- the shortened value is used only for the first received IP packet that causes reactivation from dormancy, and the nominal value is used thereafter. For this embodiment, it is not necessary to maintain the wait timer.
- more than two values are used for the inactivity timer. For example, each received IP packet may result in the inactivity timer being reset with a progressively longer value, from the shortest value to the nominal value.
- the first received IP packet may result in the inactivity timer being reset with the shortest value
- the next received IP packet may result in the inactivity timer being reset with a longer value
- the n-th received IP packet may result in the inactivity timer being reset with the nominal value, hi general, any number of values may be used for the inactivity timer, and each timer value may be applied in any manner.
- the inactivity timer is selectively reset based on the detected traffic.
- a single value or multiple values may be used for the inactivity timer.
- the inactivity timer is not automatically reset upon receiving an inbound IP packet or sending an outbound IP packet. Instead, the inactivity timer is selectively reset whenever an IP packet is deemed to be a valid IP packet.
- FIG. 7 shows a flow diagram of a process 700 for selectively resetting the inactivity timer. Initially, an IP packet is received from the wireless network (block 712). This received IP packet may or may not have caused reactivation from dormancy. The destination for the received IP packet within the wireless device is then determined (block 714).
- a web application may be running at the wireless device and may use a particular port to send out data. An inbound IP packet destined for this port would be delivered to the web application. The web application may be viewed as having silently solicited the traffic. An inbound IP packet may thus be considered as a valid IP packet if it is destined for a port associated with an application or service running at the wireless device.
- the inactivity timer is reset to the nominal value by either a valid received IP packet or an outbound IP packet.
- the inactivity timer is thus reset to the nominal value whenever valid traffic is detected.
- the inactivity timer is not reset, or is reset to the shortened value, by an unsolicited IP packet that is not delivered to an application or service running at the wireless device, which may then result in early transition to dormancy.
- Process 700 may be triggered by a received IP packet that causes reactivation from dormancy, as indicated in FIG. 7.
- process 700 may be used for reactivation caused by the wireless network or the wireless device and for both inbound traffic and outbound traffic.
- Process 700 requires more processing to determine whether each received IP packet is valid or unsolicited. However, process 700 may be more accurate at initiating dormancy early since an attempt is made to ascertain the validity of each received IP packet.
- the values for the inactivity timer and the wait timer may be fixed values or configurable values.
- fixed values may be selected based on characterization of unsolicited traffic that exists for the wireless network.
- the use of fixed values can simplify implementation of the timers.
- Configurable values allow for adaptation to the operating environment, which may improve performance.
- the timer values may be determined based on the nature of the unsolicited IP packets, the wireless network behavior, and so on.
- FIGS. 6 and 7 show specific embodiments of identifying unsolicited IP packets and transitioning to dormancy early so that the impact of receiving unsolicited IP packets is mitigated.
- unsolicited IP packets may be identified in various manners. For example, a received IP packet may be deemed as an unsolicited IP packet if it (1) causes the wireless device to reactivate from dormancy, as described for FIG. 6, (2) is not delivered to an application or service running at the wireless device, as described for FIG. 7, (3) results in no reply or a single reject by the wireless device, or (4) satisfies some other condition or criterion.
- An unsolicited IP packet may also be identified by the amount of time required for a subsequent data exchange, if any.
- a data exchange following a received IP packet is shorter than a predetermined time duration, then the received IP packet may be deemed as an unsolicited IP packet.
- a data exchange for an unsolicited IP packet is typically quite short in comparison to a data exchange for a valid IP packet.
- the detection of received IP packets as unsolicited IP packets may be used to initiate dormancy earlier and hence conserve both radio resources and battery power.
- FIG. 8 shows a block diagram of an embodiment of wireless device 120.
- Wireless device 120 includes a wireless modem for communication with wireless network 130, a controller 840, a memory 842, and timers 844.
- data and signaling to be sent by wireless device 120 are processed (e.g., formatted, encoded, and interleaved) by an encoder 822 and further processed (e.g., modulated, spread, channelized, and scrambled) by a modulator (Mod) 824 to generate a stream of data chips.
- Mod modulator
- a transmitter unit (TMTR) 832 then conditions (e.g., converts to analog, filters, amplifies, and frequency upconverts) the data chip stream to generate a reverse link signal, which is transmitted via an antenna 836.
- TMTR transmitter unit
- RCVR receiver unit
- Receiver unit 838 conditions (e.g., filters, amplifies, frequency downconverts, and digitizes) the received signal to generate data samples.
- a demodulator (Demod) 826 processes (e.g., descrambles, despreads, channelizes, and demodulates) the samples to obtain symbol estimates.
- a decoder 828 further processes (e.g., deinterleaves and decodes) the symbol estimates to obtain decoded data.
- Encoder 822, modulator 824, demodulator 826, and decoder 828 may be implemented by a modem processor 820. These units perform processing in accordance with the wireless technology (e.g., W-CDMA or cdma2000) used by wireless network 130.
- Controller 840 directs the operation of various units within wireless device 120 and may further execute the applications and implement the protocol stack shown in FIG. 3.
- Memory unit 842 stores program codes and data used by controller 840 and other units.
- Timers 844 may implement the inactivity timer, the wait timer, and/or other timers.
- Controller 840 may implement processes 400, 600 and/or 700 shown in FIGS. 4, 6 and 7 to mitigate the impact of receiving unsolicited IP packets. Controller 840 may receive pertinent information used to identify unsolicited IP packets. This information may include, e.g., an indication as to whether a received IP packet causes reactivation from dormancy, the destination port number for the received IP packet, and so on. Controller 840 identifies unsolicited IP packets based on the received information and operates the inactivity timer and/or wait timer based on the detected traffic, e.g., as described above for FIGS. 6 and/or 7. Controller 840 may initiate dormancy early if unsolicited IP packets are detected.
- Controller 840 may initiate dormancy early if unsolicited IP packets are detected.
- the techniques described herein may be implemented by various means. For example, these techniques may be implemented in hardware, software, or a combination thereof.
- the processing units used to identify unsolicited IP packets and initiate dormancy early may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gate arrays
- processors controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
- the techniques may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.
- the software codes may be stored in a memory unit (e.g., memory unit 842 in FIG. 8) and executed by a processor (e.g., controller 840).
- the memory unit may be implemented within the processor or external to the processor.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05824712.3A EP1825597B1 (en) | 2004-11-22 | 2005-11-18 | Method and apparatus for mitigating the impact of receiving unsolicited packets at a wireless device |
JP2007543274A JP2008521356A (en) | 2004-11-22 | 2005-11-18 | Method and apparatus for mitigating the effects of receiving unsolicited IP packets at a wireless device |
CN200580046867.XA CN101103537B (en) | 2004-11-22 | 2005-11-18 | Method and apparatus for mitigating the impact of receiving unsolicited IP packets at a wireless device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US63026004P | 2004-11-22 | 2004-11-22 | |
US60/630,260 | 2004-11-22 | ||
US11/135,819 US8379553B2 (en) | 2004-11-22 | 2005-05-23 | Method and apparatus for mitigating the impact of receiving unsolicited IP packets at a wireless device |
US11/135,819 | 2005-05-23 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006057906A2 true WO2006057906A2 (en) | 2006-06-01 |
WO2006057906A3 WO2006057906A3 (en) | 2007-01-04 |
Family
ID=36460868
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2005/041845 WO2006057906A2 (en) | 2004-11-22 | 2005-11-18 | Method and apparatus for mitigating the impact of receiving unsolicited packets at a wireless device |
Country Status (6)
Country | Link |
---|---|
US (1) | US8379553B2 (en) |
EP (1) | EP1825597B1 (en) |
JP (2) | JP2008521356A (en) |
KR (1) | KR100924953B1 (en) |
CN (1) | CN101103537B (en) |
WO (1) | WO2006057906A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8923906B2 (en) | 2010-01-14 | 2014-12-30 | Huawei Technoloies Co., Ltd. | Method, user terminal and network side equipment for improving network resource occupancy |
CN108401279A (en) * | 2018-01-10 | 2018-08-14 | 海信集团有限公司 | A kind of low-power consumption treatment method and device of equipment |
Families Citing this family (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8639557B2 (en) * | 2002-06-11 | 2014-01-28 | The Nielsen Company (Us), Llc | Method and system for collecting and analyzing market data in a mobile communications system |
ES2377818T3 (en) * | 2005-12-14 | 2012-04-02 | Research In Motion Limited | Method and apparatus for the control of radio resources directed to a user equipment in a UMTS network |
US8701091B1 (en) | 2005-12-15 | 2014-04-15 | Nvidia Corporation | Method and system for providing a generic console interface for a graphics application |
US7891012B1 (en) * | 2006-03-01 | 2011-02-15 | Nvidia Corporation | Method and computer-usable medium for determining the authorization status of software |
US8452981B1 (en) * | 2006-03-01 | 2013-05-28 | Nvidia Corporation | Method for author verification and software authorization |
US7680478B2 (en) * | 2006-05-04 | 2010-03-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Inactivity monitoring for different traffic or service classifications |
US8265034B2 (en) * | 2006-05-17 | 2012-09-11 | Research In Motion Limited | Method and system for a signaling connection release indication |
EP2363981B1 (en) | 2006-05-17 | 2017-08-02 | BlackBerry Limited | Method and system for signaling release cause indication in a UMTS network |
US7933392B1 (en) | 2006-05-31 | 2011-04-26 | The Nielsen Company (Us), Llc | Method and system for measuring market-share for an entire telecommunication market |
US7761088B1 (en) | 2006-07-14 | 2010-07-20 | The Nielsen Company (U.S.), Llc | Method and system for measuring market information for wireless telecommunication devices |
US7778800B2 (en) * | 2006-08-01 | 2010-08-17 | Nvidia Corporation | Method and system for calculating performance parameters for a processor |
US8436864B2 (en) * | 2006-08-01 | 2013-05-07 | Nvidia Corporation | Method and user interface for enhanced graphical operation organization |
US8436870B1 (en) | 2006-08-01 | 2013-05-07 | Nvidia Corporation | User interface and method for graphical processing analysis |
US8607151B2 (en) * | 2006-08-01 | 2013-12-10 | Nvidia Corporation | Method and system for debugging a graphics pipeline subunit |
US8963932B1 (en) | 2006-08-01 | 2015-02-24 | Nvidia Corporation | Method and apparatus for visualizing component workloads in a unified shader GPU architecture |
EP1892895A1 (en) * | 2006-08-25 | 2008-02-27 | Research In Motion Limited | Apparatus, and associated method, for releasing a data service radio resource allocated to a data service capable mobile node |
US7760628B2 (en) | 2006-09-26 | 2010-07-20 | Kyocera Corporation | Socket based passive server |
KR100781705B1 (en) * | 2006-10-24 | 2007-12-03 | 삼성전자주식회사 | Apparatus and method for controlling mode in a mobile communication terminal |
US8385350B2 (en) * | 2006-11-28 | 2013-02-26 | Qualcomm Incorporated | Detection for end of service using dynamic inactivity timer thresholds |
US8296738B1 (en) | 2007-08-13 | 2012-10-23 | Nvidia Corporation | Methods and systems for in-place shader debugging and performance tuning |
US9035957B1 (en) | 2007-08-15 | 2015-05-19 | Nvidia Corporation | Pipeline debug statistics system and method |
US9344290B2 (en) * | 2007-09-24 | 2016-05-17 | Qualcomm Incorporated | Terminating a multicast session within a wireless communications network |
US8570911B2 (en) | 2007-09-24 | 2013-10-29 | Qualcomm Incorporated | Multicast messaging within a wireless communication system |
US7765500B2 (en) * | 2007-11-08 | 2010-07-27 | Nvidia Corporation | Automated generation of theoretical performance analysis based upon workload and design configuration |
ATE553628T1 (en) | 2007-11-13 | 2012-04-15 | Research In Motion Ltd | METHOD AND APPARATUS FOR STATUS/MODE TRANSITIONS |
KR100963876B1 (en) * | 2008-03-14 | 2010-06-16 | 삼성전자주식회사 | Apparatus and method for controlling mode of portable terminal according to reception service |
US8448002B2 (en) * | 2008-04-10 | 2013-05-21 | Nvidia Corporation | Clock-gated series-coupled data processing modules |
US8279852B2 (en) * | 2008-10-01 | 2012-10-02 | The Nielsen Company (Us), Llc | Method and system for measuring market share for voice over internet protocol carriers |
US8837699B2 (en) * | 2008-10-01 | 2014-09-16 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor subscriber activity |
AU2009313191B2 (en) * | 2008-11-10 | 2014-03-13 | Blackberry Limited | Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution |
US8369826B2 (en) * | 2009-03-18 | 2013-02-05 | The Nielsen Company (Us), Llc | Methods and apparatus to identify wireless subscriber activity status |
CN101859330B (en) * | 2009-04-09 | 2012-11-21 | 辉达公司 | Method for verifying integrated circuit effectiveness models |
US8533809B1 (en) * | 2009-05-29 | 2013-09-10 | Sprint Spectrum L.P. | Forced state-change to facilitate blacklist evaluation |
CN102763484B (en) | 2009-11-23 | 2016-06-01 | 黑莓有限公司 | Method and apparatus for state/mode conversion |
WO2011060998A1 (en) | 2009-11-23 | 2011-05-26 | Research In Motion Limited | State or mode transition triggering based on sri message transmission |
JP5525620B2 (en) * | 2009-11-23 | 2014-06-18 | ブラックベリー リミテッド | Method and apparatus for state / mode transition |
US20110124294A1 (en) * | 2009-11-24 | 2011-05-26 | Research In Motion Limited | Method and apparatus for state/mode transitioning |
US8983532B2 (en) | 2009-12-30 | 2015-03-17 | Blackberry Limited | Method and system for a wireless communication device to adopt varied functionalities based on different communication systems by specific protocol messages |
JP5551275B2 (en) * | 2010-02-10 | 2014-07-16 | ブラックベリー リミテッド | Method and apparatus for status / mode transmission |
US8830848B1 (en) * | 2010-12-09 | 2014-09-09 | Sprint Communications Company L.P. | Adjusting a control channel timer in a wireless communication |
DE102011054509A1 (en) * | 2011-10-14 | 2013-04-18 | Deutsche Telekom Ag | Method and device for controlling a mobile radio interface on mobile terminals |
CA2823789C (en) | 2011-11-11 | 2016-08-16 | Research In Motion Limited | Method and apparatus for user equipment state transition |
US9526091B2 (en) * | 2012-03-16 | 2016-12-20 | Intel Corporation | Method and apparatus for coordination of self-optimization functions in a wireless network |
WO2013184748A1 (en) * | 2012-06-08 | 2013-12-12 | Apple Inc. | Performing packet filtering and adjusting radio dormancies based on unsolicited incoming packets to electronic devices |
US9787589B2 (en) | 2012-06-08 | 2017-10-10 | Apple Inc. | Filtering of unsolicited incoming packets to electronic devices |
US9549372B2 (en) * | 2012-06-08 | 2017-01-17 | Apple Inc. | Adjusting radio dormancies in electronic devices based on receipt of unsolicited incoming packets |
US9323315B2 (en) | 2012-08-15 | 2016-04-26 | Nvidia Corporation | Method and system for automatic clock-gating of a clock grid at a clock source |
US8850371B2 (en) | 2012-09-14 | 2014-09-30 | Nvidia Corporation | Enhanced clock gating in retimed modules |
JP6003478B2 (en) * | 2012-09-27 | 2016-10-05 | 富士通株式会社 | Wireless communication apparatus and communication control method |
US9519568B2 (en) | 2012-12-31 | 2016-12-13 | Nvidia Corporation | System and method for debugging an executing general-purpose computing on graphics processing units (GPGPU) application |
KR102191174B1 (en) * | 2013-04-16 | 2020-12-15 | 삼성전자주식회사 | Method and apparatus for setting up/releasing radio resource control connection between evolved node b base station and user equipment in communication system |
CN103269513B (en) | 2013-05-05 | 2016-04-06 | 清华大学 | The tail time in cellular network is utilized to carry out the method for transfer of data |
US9471456B2 (en) | 2013-05-15 | 2016-10-18 | Nvidia Corporation | Interleaved instruction debugger |
CN104349363B (en) * | 2013-08-09 | 2017-11-24 | 上海贝尔股份有限公司 | A kind of method, equipment and system for being used to determine connection status auxiliary parameter |
US9271326B2 (en) * | 2013-08-22 | 2016-02-23 | Verizon Patent And Licensing Inc. | Radio resource control dormancy timer based on traffic type |
KR102093178B1 (en) * | 2013-09-02 | 2020-03-25 | 에스케이텔레콤 주식회사 | An apparatus and method for controlling inactivity time of mobile terminal connecting with base station |
US11323957B2 (en) * | 2017-03-30 | 2022-05-03 | Intel Corporation | Apparatus, system, and method of channel switching |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5265270A (en) * | 1990-10-31 | 1993-11-23 | Motorola, Inc. | Method and apparatus for providing power conservation in a communication system |
WO2001003451A1 (en) * | 1999-07-02 | 2001-01-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Variable fast page mode |
US20020106997A1 (en) * | 2000-10-11 | 2002-08-08 | Douglas Barber | Method and apparatus for low power operation of an RF wireless modem |
US20020172178A1 (en) * | 2001-05-16 | 2002-11-21 | Masayasu Suzuki | Radio base station/radio base station controller equipped with inactivity timer, mobile station, and state control method |
US20030100310A1 (en) * | 2001-11-26 | 2003-05-29 | Mark Lindner | System and method for traffic channel dormancy in wireless communication socket mode |
WO2003096730A1 (en) * | 2002-05-07 | 2003-11-20 | Nokia Corporation | Adaptive release/inactivity timer for controlling non real-time data connection resources in a mobile communication network |
US20040022225A1 (en) * | 2002-08-02 | 2004-02-05 | Jie Liang | Low power packet detector for low power WLAN devices |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0786059B2 (en) | 1987-07-24 | 1995-09-20 | 富士写真フイルム株式会社 | Seat control loading mechanism |
US6058289A (en) * | 1995-09-26 | 2000-05-02 | Pacific Communication Sciences, Inc. | Method and apparatus for low power mobile unit for cellular communications system |
JPH1028150A (en) * | 1996-07-10 | 1998-01-27 | Fuji Electric Co Ltd | Communication system |
JPH10276194A (en) | 1997-03-31 | 1998-10-13 | Matsushita Electric Ind Co Ltd | Data processing method |
US6480476B1 (en) * | 1998-10-15 | 2002-11-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Variable sleep mode for mobile stations in a mobile communications |
US6622251B1 (en) * | 1999-04-07 | 2003-09-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Method to put a mobile terminal into sleep when a frame control channel containing a location of slow broadcast channel does not include wakeup information |
JP4486232B2 (en) | 2000-07-28 | 2010-06-23 | 京セラ株式会社 | Wireless communication device |
US6904288B2 (en) * | 2001-05-15 | 2005-06-07 | Qualcomm Incorporated | Controller for providing an efficient dormant mode for a group communication network |
JP3886795B2 (en) * | 2001-12-10 | 2007-02-28 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication system, mobile communication method, mobile terminal, and communication base station |
US6748247B1 (en) * | 2002-03-12 | 2004-06-08 | Winphoria Networks, Inc. | System and method of handling dormancy in wireless networks |
US7227848B2 (en) * | 2002-12-06 | 2007-06-05 | Motorola, Inc. | Method and apparatus for supporting multiple packet data service connections |
US7466675B2 (en) * | 2003-02-14 | 2008-12-16 | Motorola, Inc. | Method and apparatus for supporting a reduced resource dormant state for packet data |
EP1463309A1 (en) | 2003-03-26 | 2004-09-29 | THOMSON Licensing S.A. | Data stream format processing for mobile audio/video reception |
US7729686B2 (en) * | 2003-04-02 | 2010-06-01 | Qualcomm Incorporated | Security methods for use in a wireless communications system |
KR100665457B1 (en) * | 2003-04-30 | 2007-01-04 | 삼성전자주식회사 | System and method for controlling state transition in sleep mode and awake mode in broadband wireless access communication system |
US20050041631A1 (en) * | 2003-08-20 | 2005-02-24 | Naveen Aerrabotu | Apparatus and method for primary link packet control |
KR100594009B1 (en) * | 2003-09-26 | 2006-06-30 | 삼성전자주식회사 | Method for controlling a sleep interval in broadband wireless access communication systems |
AU2004310728B2 (en) * | 2003-12-05 | 2009-09-03 | Blackberry Limited | Apparatus and method of controlling unsolicited traffic destined to a wireless communication device |
US8335533B2 (en) * | 2004-04-19 | 2012-12-18 | Zte Corporation | Trunking and push-to-talk mechanisms for WCDMA wireless communications |
US7139246B2 (en) * | 2004-06-29 | 2006-11-21 | Motorola, Inc. | Method and apparatus for adjusting a mobile communication inactivity timer |
US9198156B2 (en) * | 2004-08-23 | 2015-11-24 | Telefonaktiebolaget L M Ericsson (Publ) | Paging mobile stations in a hybrid network |
-
2005
- 2005-05-23 US US11/135,819 patent/US8379553B2/en active Active
- 2005-11-18 KR KR1020077014111A patent/KR100924953B1/en active IP Right Grant
- 2005-11-18 JP JP2007543274A patent/JP2008521356A/en not_active Withdrawn
- 2005-11-18 WO PCT/US2005/041845 patent/WO2006057906A2/en active Application Filing
- 2005-11-18 EP EP05824712.3A patent/EP1825597B1/en not_active Not-in-force
- 2005-11-18 CN CN200580046867.XA patent/CN101103537B/en active Active
-
2011
- 2011-04-07 JP JP2011085517A patent/JP5048854B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5265270A (en) * | 1990-10-31 | 1993-11-23 | Motorola, Inc. | Method and apparatus for providing power conservation in a communication system |
WO2001003451A1 (en) * | 1999-07-02 | 2001-01-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Variable fast page mode |
US20020106997A1 (en) * | 2000-10-11 | 2002-08-08 | Douglas Barber | Method and apparatus for low power operation of an RF wireless modem |
US20020172178A1 (en) * | 2001-05-16 | 2002-11-21 | Masayasu Suzuki | Radio base station/radio base station controller equipped with inactivity timer, mobile station, and state control method |
US20030100310A1 (en) * | 2001-11-26 | 2003-05-29 | Mark Lindner | System and method for traffic channel dormancy in wireless communication socket mode |
WO2003096730A1 (en) * | 2002-05-07 | 2003-11-20 | Nokia Corporation | Adaptive release/inactivity timer for controlling non real-time data connection resources in a mobile communication network |
US20040022225A1 (en) * | 2002-08-02 | 2004-02-05 | Jie Liang | Low power packet detector for low power WLAN devices |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8923906B2 (en) | 2010-01-14 | 2014-12-30 | Huawei Technoloies Co., Ltd. | Method, user terminal and network side equipment for improving network resource occupancy |
US9288835B2 (en) | 2010-01-14 | 2016-03-15 | Huawei Technologies Co., Ltd. | Method, user terminal and network side equipment for improving network resource occupancy |
CN108401279A (en) * | 2018-01-10 | 2018-08-14 | 海信集团有限公司 | A kind of low-power consumption treatment method and device of equipment |
Also Published As
Publication number | Publication date |
---|---|
WO2006057906A3 (en) | 2007-01-04 |
CN101103537B (en) | 2015-06-24 |
JP2008521356A (en) | 2008-06-19 |
US20060109846A1 (en) | 2006-05-25 |
KR20070086510A (en) | 2007-08-27 |
JP2011176859A (en) | 2011-09-08 |
KR100924953B1 (en) | 2009-11-06 |
JP5048854B2 (en) | 2012-10-17 |
CN101103537A (en) | 2008-01-09 |
US8379553B2 (en) | 2013-02-19 |
EP1825597A2 (en) | 2007-08-29 |
EP1825597B1 (en) | 2016-11-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8379553B2 (en) | Method and apparatus for mitigating the impact of receiving unsolicited IP packets at a wireless device | |
JP2008521356A5 (en) | ||
US8755848B2 (en) | Mobile device power management | |
CA2544244C (en) | Always-on wireless internet protocol communication | |
EP1621041B1 (en) | Method and apparatus for enhancing air-interface information exchange during a dormant packet data session | |
KR101107357B1 (en) | Method and system for signaling release cause indication in a umts network | |
US20100285804A1 (en) | Apparatus, and associated method, for permitting communication system transition based upon signal threshold determination | |
TW201141135A (en) | Method and apparatus for user equipment directed radio resource control in a UMTS network | |
JP2011176856A (en) | Method and system for signaling release cause indication in umts network | |
KR20110110857A (en) | Method and apparatus for state/mode transitioning | |
JP4186480B2 (en) | Mobile portable terminal and always-on PDP context management method used therefor | |
AU2004237719B2 (en) | Method and apparatus for exchanging air-interface information during a dormant packet data session | |
KR100897452B1 (en) | Method of entering preservation mode in a mobile communicatin terminal during multi radio access bearer service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2007543274 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 842/MUMNP/2007 Country of ref document: IN |
|
REEP | Request for entry into the european phase |
Ref document number: 2005824712 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005824712 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020077014111 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580046867.X Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2005824712 Country of ref document: EP |