AU7357700A - System and method for automatically determining when to answer incoming packet data calls in a wireless communication network - Google Patents

System and method for automatically determining when to answer incoming packet data calls in a wireless communication network Download PDF

Info

Publication number
AU7357700A
AU7357700A AU73577/00A AU7357700A AU7357700A AU 7357700 A AU7357700 A AU 7357700A AU 73577/00 A AU73577/00 A AU 73577/00A AU 7357700 A AU7357700 A AU 7357700A AU 7357700 A AU7357700 A AU 7357700A
Authority
AU
Australia
Prior art keywords
ready
state
communication device
data
terminal device
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.)
Abandoned
Application number
AU73577/00A
Inventor
Nischal Abrol
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.)
Qualcomm Inc
Original Assignee
Qualcomm 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 Qualcomm Inc filed Critical Qualcomm Inc
Publication of AU7357700A publication Critical patent/AU7357700A/en
Abandoned legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18Negotiating wireless communication parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/204Multiple access
    • H04B7/216Code division or spread-spectrum multiple access [CDMA, SSMA]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854Wide area networks, e.g. public data networks
    • H04L12/2856Access arrangements, e.g. Internet access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Description

WO 01/19099 PCT/USOO/24622 1 SYSTEM AND METHOD FOR AUTOMATICALLY DETERMINING WHEN TO ANSWER INCOMING PACKET DATA CALLS IN A WIRELESS COMMUNICATION NETWORK 5 BACKGROUND OF THE INVENTION I. Field of the Invention This invention generally relates to the field of wireless communications. More particularly, the present invention relates to a novel and improved 10 method and system for automatically answering incoming packet data calls in a wireless communication network. II. Description of Related Art Recent innovations in wireless communication and computer-related 15 technologies, as well as the unprecedented growth of Internet subscribers, have paved the way for mobile computing. In fact, the popularity of mobile computing has placed greater demands on the current communications infrastructure to provide mobile users with more support. A crucial part of meeting these demands andproviding users with the necessary support is the use 20 of Code Division Multiple Access (CDMA) technology in wireless communication systems. CDMA is a digital radio-frequency (RF) channelization technique that is defined in the Telecommunications Industry Association/Electronics Industries Association Interim Standard-95 (TIA /EIA IS-95), entitled "MOBILE STATION 25 BASE STATION COMPATIBILITY STANDARD FOR DUAL-MODE W IDEBAND SPREAD SPECTRUM CELLULAR SYSTEM", published in July 1993 and herein incorporated by reference. Wireless communication systems employing this technology assign a unique code to communication signals and spread these communication signals across a common wideband spread spectrum 30 bandwidth. As long as the receiving apparatus in a CDMA system has the correct code, it can sucossfully detect and select its communication signal from the other WO 01/19099 PCT/USOO/24622 2 signals concurrently transmitted over the same bandwidth. The use of CDMA produces an increase in system traffic capacity, improves overall call quality and noise reduction, and provides a reliable transport mechanism for data service traffic. 5 FIG. 1 illustrates a simplified block diagram depicting some of the basic elements of such a wireless data communication system 100. Artisans of ordinary skill will readily appreciate that these basic elements, along with their associated interfaces, may be modified, augmented, or subjected to various standards known in the art, without limiting their scope or function. System 10 100 allows a mobile terminal equipment, TE2 device 102 (e.g., the terminal equipment such as laptop or palmtop computer) to communicate with an Interworking Function (IWF) 108. System 100 includes a wireless communication device, MT2 device 104 (e.g., wireless telephone), and a Base Station/Mobile Switching Center (BS/MSC) 106. The IWF 108 serves as a 15 gateway between the wireless network and other networks, such as the Public Switched Telephone Network and wireline packet data networks providing Internet- or Intranet-based access. An L interface couples IWF 108 to BS/MSC 106. Often the IWF 108 will be co-located with the BS/MSC 106. The TE2 device 102 is electronically coupled to the MT2 device 104 via the Rm interface. The 20 MT2 device 104 communicates with the BS/MSC 106 via the wireless interface Um. The TE2 device 102 and the MT2 device 104 may be integrated into a single unit or may be separated out, as in the case of an installed mobile phone unit in which a laptop is the TE2 device 102 and the transceiver is the MT2 device 104. It is important to note that, as indicated by FIG. 2, the combination of the TE2 25 device 102 and the MT2 device 104, whether integrated or separate, is generally referred to as a mobile station (MS) 103. The ability of CDMA system to accommodate data service traffic has been recognized in the TIA/EIA IS-707.5 standard, entitled "DATA SERVICE OPTIONS FOR WIDEBAND SPREAD SPECTRUM SYSTEMS: PACKET DATA 30 SERVICES," published in February 1998 and herein incorporated by reference.
WO 01/19099 PCT/US00/24622 3 This standard defines the requirements for supporting packet data transmission on TIA/EIA IS-95 wideband spread spectrum systems and provides a suite of packet data bearer services. Similarly, the TIA/EIA IS-707-A.5 standard, entitled "DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: PACKET 5 DATA SERVICES," and the TIA/EIA IS-707-A.9 standard, entitled "DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: HIGH-SPEED PACKET DATA SERVICES," both published in March 1999 and incorporated by reference, also define requirements for packet data transmission support on TIA/EIA IS-95 systems. 10 These standards provide that certain packet data service options may be used to communicate between the TE2 device 102 and IWF 108 via BS/MSC 106. In doing so, IS-707.5 introduces two protocol option models, which specify the packet data protocol requirements for the Rm interface. FIG. 2 depicts one of the protocol option models, the Relay Layer Interface Protocol Option model 15 200, in which the application running on the TE2 device 102 manages the packet data services as well as the network addressing. At the far left of FIG. 2 is a protocol stack, shown in conventional vertical format that depicts the protocol layers running on the TE2 device 102. The TE2 protocol stack is logically connected to the protocol stack of the MT2 device 104 20 over the Rm interface. The Rm interface may comply, for example, with the TIA/EIA-232-F standard, entitled "INTERFACE BETWEEN DATA TERMINAL EQUIPMENT AND DATA CIRCUIT-TERMINATING EQUIPMENT EMPLOYING SERIAL BINARY DATA INTERCHANGE", published in October 1997 and herein incorporated by reference. It is to be understood that other 25 standards or protocols known to artisans of ordinary skill in the art may be used to define the transmission across the Rm interface. For example, other applicable Rm interface standards include, the "UNIVERSAL SERIAL BUS (USB) SPECIFICATION, Revision 1.1", published in September 1998, and the "BLUETOOTH SPECIFICATION VERSION 1.OA CORE, published in July 1999, 30 both incorporated by reference.
WO 01/19099 PCTUSOO/24622 4 By way of illustration, the TIA/EIA-232-F standard is shown in FIG. 2 as specifying the Rm interface. The TIA/EIA-232-F standard describes both the physical interface as well as the communications protocol for relatively low speed serial data communication between the Data Terminal Equipment (DTE) 5 (i.e., the TE2 device 102) and the Data Circuit-Terminating Equipment (DCE) (i.e., the MT2 device 104). FIG. 3A depicts the physical interface and lists the corresponding signals defined by the TIA/EIA-232-F standard. FIG. 3B briefly illustrates the communications protocol provided by the TIA/EIA-232-F standard. According to the standard, the TE2 device 102 10 generates a Data-Terminal-Ready (DTR) signal 320, which transitions from a low state to a high state, to indicate that it is ready to transmit data. Similarly, the MT2 device 104 generates a Data-Set-Ready (DSR) signal 306, which transitions from a low state to a high state, to indicate that it is ready to receive data. The TE2 device 102 Request-to-Send (RTS) signal 304 and the MT2 device 15 104 Clear-to-Send (CTS) signal 305 are used to control the flow of data between the TE2 device 102 and the MT2 device 104. To establish a link with a remote DCE device (e.g., communications equipment at the BS/MSC 106), the MT2 device 104 activates a signal carrier. This signal carrier activation triggers the MT2 device 104 Data-Carrier-Detect (DCD) signal 308 to transition from low-to 20 high, which notifies the TE2 device 102 that it is ready to exchange data. While the DCD signal 308 is high, data is transmitted and received by the Transmit Data (TXD) 302 and Receive-Data (RXD) 303 signals, respectively. Central to the IS-707.5 Relay Layer Interface Protocol Option is the notion that the principal link layer connection is established between the TE2 device 25 102 and the IWF 108. As such, the MT2 device 104 simply behaves as a pipe transmitting the TE2 device 102 frames over the Um interface and the IWF 108 frames over the Rm interface. As indicated in FIG. 2, the Relay Layer Interface Protocol Option implements the Point-to-Point Protocol (PPP) as its link layer protocol 208,232 at both ends of the link. PPP is described in detail in Request for 30 Comments 1661 (RFC1661), entitled "THE POINT-TO-POINT PROTOCOL (PPP)", WO 01/19099 PCT/USOO/24622 5 dated May 1992 and herein incorporated by reference. Essentially, the PPP protocol configures, tests, and establishes the data link connection. In addition, the PPP protocol encodes the packets coming from upper protocol layers of the TE2 102 device, "serializing" them to facilitate transmission. 5 To support packet data services on CDMA systems, the IS-707.5 standard provides that the IWF 108 and the MS 103 (i.e., the combination of the TE2 device 102 and the MT2 device 104) utilize the link layer connection, as typified by the Relay Layer Interface Protocol Option model, to facilitate the transmission of packet data. For example, the IWF 108 link layer 232 must be 10 open and the IWF 108 must request the activation of a link layer connection for packet data calls destined to the TE2 device 102. Such activation requests are achieved by directing the BS/MSC 106 to connect to the TE2 device 102 via the MT2 device 104 with a packet data service option. Generally, the BS/MSC 106 initiates the connect operation by 15 transmitting a Page Message to the MT2 device 104 and requesting a packet data service option. As per the IS-95 standard, Page messaging is used to notify the MT2 device 104 of incoming calls, including incoming packet calls, and is incorporated in the overhead Paging Channel of the forward link channel. If the MT2 device 104 replies with a Page Response Message having a valid 20 service option number, the BS/MSC 106 assigns the MT2 device 104 a Traffic Channel. The Page Response Message is transmitted over the Access Channel of the reverse link channel. With this said, it is important to note that other protocols may implement methods, other than Page messaging, to notify the MT2 device 104 of incoming calls. For example, under certain circumstances a 25 message protocol operating on the Um interface may directly provide the BS/MSC 106 with a Traffic Channel, without having to notify the MT2 device 104 of incoming calls. The Traffic Channel accommodates the transfer of packet data between the BS/MSC 106 and the TE2 device 102 and comprises a combination of 30 Forward and Reverse Traffic Channel Frames. The Traffic Channel assignment WO 01/19099 PCT/USOO/24622 6 is established by first initializing the channel for the MT2 device 104, followed by negotiating the connection of a packet data service option with the TE2 device 102, and then further negotiating the requested service configuration with the TE2 device 102. 5 FIG. 4 is a high-level state diagram depicting the general interchange between the MT2 device 104 and the BS/MSC 106 after the Traffic Channel has been assigned. After the assignment, the IS-95 standard specifies that the BS/MSC 106 transmits an "ALERT WITH INFORMATION MESSAGE" to the MT2 device 104 on the forward link channel. The ALERT WITH 10 INFORMATION MESSAGE contains signaling information from the BS/MSC 106, which prompts the MT2 device 104 to notify the subscriber of an incoming call (e.g., ringing with possibly different tones and patterns). As indicated in FIG. 4, receipt and processing of the ALERT WITH INFORMATION MESSAGE places the MT2 device 104 in a "WAITING FOR 15 MOBILE STATION ANSWER SUBSTATE" 410. Upon entering substate 410, the MT2 device 104 sets a substate timer for a maximum of T 53 m seconds. The MT2 device 104 then waits for the subscriber to answer the incoming call by responding to the signaling information processed by the MT2 device 104 (i.e., audible "ringing" patterns, visual "flashes" on a screen, etc.). If the subscriber 20 answers the signaling MT2 device 104 within the T 53 m second time limit, the MT2 device 104 transmits a "CONNECT ORDER" to the BS/MSC 106. This places the MT2 device 104 in the "CONVERSATION SUBSTATE" 430. The MT2 device 104 then proceeds to communicate with the BS/MSC 106 by processing Forward and Reverse Traffic Channel Frames. On the other hand, if 25 the subscriber does not answer the signaling MT2 device 104, the substate timer expires, which results in the MT2 device 104 entering the "TRANSMITTER DISABLED SUBSTATE" 420. In substate 420, the MT2 device 104 disables the transmitter, releases the Traffic Channel, and terminates the call. As stated above, once the MT2 device 104 is in the WAITING FOR 30 MOBILE STATION ANSWER SUBSTATE 410, the MT2 device 104 must accept WO 01/19099 PCT/USOO/24622 7 and process the ALERT WITH INFORMATION MESSAGE. Typically, for voice calls, the processing of this message is relatively automatic and results in the ringing of the MT2 device 104. The subscriber then answers the ringing MT2 device 104 by picking up the handset or pressing a pre-programmed function 5 key. Unlike incoming voice calls, however, there is no clearly defined procedure that specifies how the MT2 device 104 responds to an incoming packet data call. For example, instead of simply ringing or flashing to notify the subscriber, the MT2 device 104, in processing packet data calls, has to consider 10 an additional element - the TE2 device 102 - which is the ultimate destination of the incoming packet data call. As stated above, the TE2 device 102 may be a laptop or palmtop computer that is electrically coupled to the MT2 device 104 via the Rm (EIA-232F) interface. Thus, before the MT2 device 104 can accept and process the ALERT WITH INFORMATION MESSAGE transmitted by the 15 BS/MSC 106, the MT2 device 104 has to determine whether the TE2 device 102 is ready, or even capable, of connecting and exchanging packet data. Therefore, what is needed is a novel method and system that enables the wireless communication device to determine when to answer an incoming packet data call. 20 SUMMARY OF THE INVENTION The present invention addresses the need identified above by providing a system and method that enables a wireless communication device to determine when to answer an incoming packet data call generated from a base 25 station in a wireless communication network. Systems and methods consistent with the principles of the present invention as embodied and broadly described herein include a communication device, which interfaces with the wireless communication network, and a terminal device, which is electronically coupled to the communication device 30 and is capable of transmitting and receiving packetized data. The WO 01/19099 PCT/USOO/24622 8 communications device answers the incoming packetized data call from the base station in response to detecting a control signal or control information indicating the ready-state of the terminal device. This terminal device ready state indicator may include control signals such as a high-state data transmit 5 ready signal or the low-state to high-state transition of the data transmit ready signal after a ring-indicator signal has been activated to alert a subscriber of the incoming call. The ready-state indicator may also include control information such as a point-to-point protocol packetized data indicator flag, embedded in the data stream generated from the terminal device, or other information 10 indicating that a point-to-point protocol packet was sent by the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a 15 part of this Specification, illustrate an embodiment of the invention and, together with the description, explain the objects, advantages, and principles of the invention. In the drawings: FIG. 1 is a high level block diagram depicting various elements of a wireless communication system. 20 FIG. 2 schematically describes the protocol stacks of a wireless communication system. FIGs. 3A, 3B describe the TIA/EIA-232-F protocol. FIG. 4 is a state diagram depicting the operation of a wireless communication device. 25 FIG. 5 is a state diagram illustrating an embodiment of the invention.
WO 01/19099 PCT/USOO/24622 9 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following detailed description of the present invention refers to the 5 accompanying drawings that illustrate preferred embodiments consistent with this invention. Other embodiments are possible and modifications may be made to the embodiments without departing from the spirit and scope of the invention. Therefore, the following detailed description is not meant to limit the invention. Rather the scope of the invention is defined by the appended 10 claims. It will be apparent to one of ordinary skill in the art that an embodiment of the present invention, as described below, may be realized in a variety of implementations, including the software, firmware, and hardware of the entities illustrated in the figures (i.e., TE2 device 102, MT2 device 104, BS/MSC 15 106 and IWF 108). The actual software code or control hardware used to implement the present invention is not limiting of the present invention. Thus, the operation and behavior of the present invention will be described without specific reference to the actual software code or hardware components. Such non-specific references are acceptable because it is clearly understood that 20 a person of ordinary skill in the art would be able to design software and control hardware to implement the embodiment of the present invention based on the description herein. FIG. 5 is a high-level state diagram of an embodiment of the present invention. As such, FIG. 5 details the operation of the MT2 device 104 for 25 determining whether to accept, process, and answer incoming packet data calls. The MT2 device 104 begins in the "IDLE STATE" 510. In this state, there is no Traffic Channel established between the BS/MSC 106 and the MT2 device 104 to accommodate packet data traffic. Therefore, the MT2 device 104 is free to originate or receive any type of call.
WO 01/19099 PCT/USOO/24622 10 As stated above, the MT2 device 104 is coupled to the TE2 device 102 via the Rm interface and signaling between the two devices can be achieved in accordance with such standards as the TIA/EIA-232-F or the USB. These standards provide control information or control signals that indicate the 5 ready-state of the TE2 device 102. Examples of such TE2 device 102 ready-state control information include USB packets embedded with ready-state information as well as the TIA/EIA-232-F DTR signal. Moreover, in some conventional implementations, the MT2 device 104 has been configured to detect ready-state control information. In other implementations, the MT2 10 device 104 has not been specifically instructed to ignore the ready-state control signals (e.g., the Hayes standard dialing command string 'AT&DO' has not been set to disregard the TIA/EIA-232-F DTR signal). In either case, the present embodiment exploits such ready-state control information by using it to trigger the MT2 device 104 to answer the incoming packet data call. For example, if the 15 MT2 device 104 receives a Page Message from the BS/MSC 106 that requests a packet data service option, the MT2 device 104 will automatically answer the incoming packet data call if it detects ready-state control information/signal. This automatic answer is executed by the MT2 device 104 sending a CONNECT ORDER to the BS/MSC 106, consistent with IS-95 procedure (see FIG. 4). This 20 order places the MT2 device 104 into the "CALL ACTIVE STATE" 530. If the MT2 device 104 receives a Page Message with a packet data service option and the MT2 device 104 is not capable of detecting the pertinent ready state control information/signal (e.g., the DTR signal) or otherwise detects the ready-state control signal in a "low state" (e.g., the TE2 device 102 is not 25 physically connected to the MT2 device 104), the MT2 device 104 progresses to the PROCESS PAGE STATE 520. This state is analogous to the WAITING FOR MS ANSWER SUBSTATE defined in the IS-95 standard (see FIG. 4). Because a low ready-state control signal fails to indicate the presence of an awaiting TE2 device 102, the MT2 device 104, in state 520, will toggle the 30 Ring Indicator signal (RI) on the Rm interface to signify the existence of an WO 01/19099 PCT/USOO/24622 11 incoming packet data call. This RI toggling can be configured to trigger an alert signal (e.g., audible tones/patterns or visual flashes/messages) to notify a subscriber of the incoming packet data call. If, after the RI toggling, and within the T 5 3 m second time limit of the WAITING FOR MS ANSWER SUBSTATE 430 5 T 5 3m timer, the MT2 104 device detects a low-to-high ready-state control signal transition (i.e., DTR signal transition) or detects PPP packets on the Rm interface, the MT2 104 advances to the "CALL ACTIVE STATE" 530. The ready-state control signal transition and the existence of PPP packets can occur, for example, if the TE2 device 102 was previously disconnected from 10 the MT2 104 device and the audible or visual signal produced by the RI toggling reminded the subscriber to reconnect the two devices. After reconnecting the two devices, the TE2 device 102 packet data application drives the ready-state control signal to a high state and, after the usual Rm interface negotiation, the TE2 device 102 transmits PPP packets to the MT2 104 device. By detecting the 15 control signal transition coming from the TE2 device 102, the MT2 device 104 is notified of an awaiting TE2 device 102. Moreover, in the event that the MT2 104 device cannot detect the ready-state control information/signal or is instructed to ignore such signals (e.g., by sending the AT dialing command string 'AT&DO' to ignore the DTR signal), the MT2 104 device can still detect PPP 20 packets by examining byte streams on the Rm interface and looking for the PPP flag (i.e., Ox7E character) at the beginning of a packet. Accordingly, if, within the
T
5 3 m time limit, the MT2 104 device detects either (1) the ready-state control signal transition or (2) the PPP packet flag, it answers the incoming packet data call by sending a CONNECT ORDER to the BS/MSC 106, consistent with IS-95 25 procedure (see FIG. 4). If, on the other hand, the MT2 device 104 does not detect the ready-state control signal transition or the PPP flag within the T 53 m time limit, the MT2 104 device times out and returns to the IDLE STATE 510. As stated above, in this state the MT2 device 104 is free to originate or receive any type of call.
WO 01/19099 PCT/USOO/24622 12 Whenever the MT2 device 104 answers the call by sending a CONNECT ORDER to the BS/MSC 106, the MT2 device 104 enters into the CALL ACTIVE STATE 530. This state is analogous to the CONVERSATION SUBSTATE 430 described in the IS-95 standard. In state 530, the MT2 device 104 exchanges 5 packet data traffic with the BS/MSC 106 by processing Forward and Reverse Traffic Channel Frames. This embodiment, therefore, provides a system and method that enables the MT2 device 104 to determine when to answer an incoming packet data call. The foregoing description of preferred embodiments of the present 10 invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disposed. Modifications and variations are possible consistent with the above teachings or may be acquired from practice of the invention. Accordingly, the scope of the invention is defined by the claims and their equivalents. 15 What is claimed is:

Claims (16)

1. A system for determining when to answer an incoming packetized 2 data call in a wireless communication network, said system comprising: a communication device for interfacing with said wireless 4 communication network; and a terminal device, coupled to said communication device, for 6 transmitting and receiving packetized data; wherein said communication device answers said incoming 8 packetized data call in response to detecting a ready-state indicator generated by said terminal device.
2. The system of Claim 1, wherein said ready-state indicator includes 2 a high-state data transmit ready signal.
3. The system of Claim 2, wherein said ready-state indicator includes 2 a low-state to high-state transition of a data transmit ready signal after a ring indicator signal on said communication device has been activated to alert a 4 subscriber of said incoming packetized data call.
4. The system of Claim 3, wherein said ready-state indicator includes 2 information in a data stream generated from said terminal device indicating a transmission of point-to-point protocol packetized data.
5. A method for determining when to answer an incoming 2 packetized data call in a wireless communication network, said method comprising: 4 interfacing a communication device with said wireless communication network; WO 01/19099 PCT/USOO/24622 14 6 coupling a terminal device to said communication device, said terminal device capable of transmitting and receiving packetized data; 8 detecting, by said communication device, a ready-state indicator generated by said terminal device; and 10 answering, by said communication device, said incoming packetized data call, in response to said detection of said ready-state indicator.
6. The method of Claim 5, wherein said ready-state indicator 2 includes a high-state data transmit ready signal.
7. The method of Claim 6, wherein said ready-state indicator 2 includes a low-state to high-state transition of a data transmit ready signal after a ring-indicator signal on said communication device has been activated to 4 alert a subscriber of said incoming packetized data call.
8. The method of Claim 7, wherein said ready-state indicator 2 includes information in a data stream generated from said terminal device indicating a transmission of point-to-point protocol packetized data.
9. A communication device capable of determining when to answer 2 a packetized data call in a wireless communication network, said communication device comprising: 4 means for interfacing with said wireless communication network; means for being coupled to a terminal device, said terminal device 6 capable of transmitting and receiving packetized data; means for detecting a ready-state indicator generated by said 8 terminal device; and means for answering said incoming packetized data call in 10 response to said detection of said ready-state indicator. WO 01/19099 PCT/USOO/24622 15
10. The communication device of Claim 9, wherein said ready-state 2 indicator includes a high-state data transmit ready signal.
11. The communication device of Claim 10, wherein said ready-state 2 indicator includes a low-state to high-state transition of a data transmit ready signal after a ring-indicator signal on said communication device has been 4 activated to alert a subscriber of said incoming packetized data call.
12. The communication device of Claim 11, wherein said ready-state 2 indicator includes information in a data stream generated from said terminal device indicating a transmission of point-to-point protocol packetized data.
13. A machine-readable medium encoded with a plurality of processor 2 executable instructions for performing a process comprising enabling a communication device to interface with a wireless 4 communication network; enabling said communication device to communicate with a 6 terminal device, said terminal device capable of transmitting and receiving packetized data; 8 detecting, by said communication device, a ready-state indicator generated by said terminal device; and 10 answering, by said communication device, an incoming packetized data call in response to said detection of said ready-state indicator.
14. The machine-readable medium of Claim 13, wherein said ready 2 state indicator includes a high-state data transmit ready signal.
15. The machine-readable medium of Claim 14, wherein said ready 2 state indicator includes a low-state to high-state transition of a data transmit WO 01/19099 PCT/USOO/24622 16 ready signal after a ring-indicator signal on said communication device has 4 been activated to alert a subscriber of said incoming packetized data call.
16. The machine-readable medium of Claim 14, wherein said ready 2 state indicator includes information in a data stream generated from said terminal device indicating a transmission of point-to-point protocol packetized 4 data.
AU73577/00A 1999-09-08 2000-09-07 System and method for automatically determining when to answer incoming packet data calls in a wireless communication network Abandoned AU7357700A (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US39234299A 1999-09-08 1999-09-08
PCT/US2000/024622 WO2001019099A2 (en) 1999-09-08 2000-09-07 System and method for automatically determining when to answer incoming packet data calls in a wireless communication network
US09 2000-12-01

Publications (1)

Publication Number Publication Date
AU7357700A true AU7357700A (en) 2001-04-10

Family

ID=23550209

Family Applications (1)

Application Number Title Priority Date Filing Date
AU73577/00A Abandoned AU7357700A (en) 1999-09-08 2000-09-07 System and method for automatically determining when to answer incoming packet data calls in a wireless communication network

Country Status (7)

Country Link
JP (2) JP4846948B2 (en)
KR (1) KR20020029783A (en)
CN (2) CN1387732A (en)
AU (1) AU7357700A (en)
CA (2) CA2384162C (en)
IL (1) IL148477A0 (en)
WO (2) WO2001019099A2 (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8121296B2 (en) 2001-03-28 2012-02-21 Qualcomm Incorporated Method and apparatus for security in a data processing system
US9100457B2 (en) * 2001-03-28 2015-08-04 Qualcomm Incorporated Method and apparatus for transmission framing in a wireless communication system
US7352868B2 (en) 2001-10-09 2008-04-01 Philip Hawkes Method and apparatus for security in a data processing system
US7649829B2 (en) 2001-10-12 2010-01-19 Qualcomm Incorporated Method and system for reduction of decoding complexity in a communication system
US7616637B1 (en) 2002-04-01 2009-11-10 Cisco Technology, Inc. Label switching in fibre channel networks
US7406034B1 (en) 2002-04-01 2008-07-29 Cisco Technology, Inc. Methods and apparatus for fibre channel frame delivery
US7433326B2 (en) 2002-11-27 2008-10-07 Cisco Technology, Inc. Methods and devices for exchanging peer parameters between network devices
US7599655B2 (en) 2003-01-02 2009-10-06 Qualcomm Incorporated Method and apparatus for broadcast services in a communication system
US8098818B2 (en) 2003-07-07 2012-01-17 Qualcomm Incorporated Secure registration for a multicast-broadcast-multimedia system (MBMS)
US8718279B2 (en) 2003-07-08 2014-05-06 Qualcomm Incorporated Apparatus and method for a secure broadcast system
US8724803B2 (en) 2003-09-02 2014-05-13 Qualcomm Incorporated Method and apparatus for providing authenticated challenges for broadcast-multicast communications in a communication system
EP2074712B1 (en) * 2006-10-03 2012-04-11 ViaSat, Inc. Web/bulk transfer preallocation of upstream resources in a satellite communication system
JP5172447B2 (en) * 2008-04-23 2013-03-27 京セラ株式会社 Data transfer system and wireless communication device

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2802188B2 (en) * 1992-02-04 1998-09-24 シャープ株式会社 Modem
JPH07322045A (en) * 1994-05-20 1995-12-08 Matsushita Electric Ind Co Ltd Communication controller and communication control method
FI98027C (en) * 1995-01-10 1997-03-25 Nokia Telecommunications Oy Packet radio system and terminal equipment for a packet radio system
US6108704A (en) * 1995-09-25 2000-08-22 Netspeak Corporation Point-to-point internet protocol
US5699350A (en) * 1995-10-06 1997-12-16 Canon Kabushiki Kaisha Reconfiguration of protocol stacks and/or frame type assignments in a network interface device
US5940383A (en) * 1996-01-29 1999-08-17 Qualcomm Incorporated Automatic data service selection
JPH10285361A (en) * 1997-04-08 1998-10-23 Ricoh Co Ltd Communication equipment
US6512754B2 (en) * 1997-10-14 2003-01-28 Lucent Technologies Inc. Point-to-point protocol encapsulation in ethernet frame
US20030156571A1 (en) * 1998-06-05 2003-08-21 Hans-Ake Lund Communications network and method for framing point-to-point frame structures
US6765901B1 (en) * 1998-06-11 2004-07-20 Nvidia Corporation TCP/IP/PPP modem

Also Published As

Publication number Publication date
CA2384162C (en) 2011-01-04
CN1437829A (en) 2003-08-20
JP2003509917A (en) 2003-03-11
WO2001019099A2 (en) 2001-03-15
KR20020029783A (en) 2002-04-19
WO2001019027A2 (en) 2001-03-15
WO2001019027A8 (en) 2003-12-31
WO2001019027A9 (en) 2002-10-03
JP4846948B2 (en) 2011-12-28
CA2384162A1 (en) 2001-03-15
CN100361541C (en) 2008-01-09
CA2384168A1 (en) 2001-03-15
WO2001019099A9 (en) 2002-10-03
WO2001019027A3 (en) 2002-01-17
IL148477A0 (en) 2002-09-12
CN1387732A (en) 2002-12-25
WO2001019099A3 (en) 2002-01-17
JP2011055528A (en) 2011-03-17

Similar Documents

Publication Publication Date Title
JP2011055528A (en) System and method for automatically determining time to answer incoming packet data call in wireless communication network
RU2274959C2 (en) Method and wireless system for interrupting inactive mode in session for transmitting packet data
CA2158659C (en) Method and apparatus of providing audio feedback over a digital channel
JP4673537B2 (en) Method for enabling reception of packet switched pages by a mobile station
US7522181B2 (en) Method and apparatus for videoconference interaction with bluetooth-enabled cellular telephone
JP3442393B2 (en) Data transmission method
EP1608113A1 (en) Message transmission during packet service termination
US8098617B2 (en) Method and apparatus for selective examination of PPP packets for renegotiation of a PPP link on a Um interface
JPH05501186A (en) Data network interface
AU2002301156B2 (en) Apparatus And Method For Accessing Private Wireless Internet Packet Data Communication System
EP1625701A1 (en) Systems and methods for seamlessly roaming between a wireless wide area network and a wireless local area network
JP2000504178A (en) Automatic data service selection method
JP2003507946A5 (en)
JP3045076B2 (en) Non-telephone call connection system
US6167280A (en) Method and system for initiating a data transfer in a cellular communications system
KR20080058372A (en) Efficient sharing of mobile equipment identifiers
US6631278B2 (en) Method for originating packet data calls via dial-up networking applications
KR100605865B1 (en) Method and appatus for call set up in a mobile communication system
US20020126317A1 (en) Facsimile transmission method and system
KR20020065385A (en) Multicode-based cdma communication system for simultaneously performing voice communication and data communication
KR100746866B1 (en) Methods for efficient early protocol detection
JP2972581B2 (en) PC compatible wireless modem card device
KR100429289B1 (en) Method for waiting data call
KR100254770B1 (en) Call control of interworking function in the digital cellular network
KR0181653B1 (en) Method and apparatus for controlling data communication in cdma mobile communication system