Classifications

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

Definitions

• This invention generally relates to the field of wireless communications. More particularly, the present invention relates to a novel and improved method and system for automatically answering incoming packet data calls in a wireless communication network.
• CDMA Code Division Multiple Access
• 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 STATPON- BASE STATION COMPATIBILITY STANDARD FOR DUAL-MODE WIDEBAND 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 bandwidth. As longas the receiving apparatus in a CDMA system has the correct code, it can successfully detect and select its communication signal from the other signals concurrently transmitted over the same bandwidth.
• FIG. 1 illustrates a simplified block diagram depicting some of the basic elements of such a wireless data communication system 100.
• System 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.
• IWF Interworking Function
• 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 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 R m interface.
• the MT2 device 104 communicates with the BS/MSC 106 via the wireless interface U m .
• 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 device 102 and the MT2 device 104, whether integrated or separate, is generally referred to as a mobile station (MS) 103.
• MS mobile station
• TIA/EIA IS-707-A.5 standard entitled “DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: PACKET DATA SERVICES”
• TIA/EIA IS-707-A.9 standard entitled “DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: HIGH-SPEED PACKET DATA SERVICES”
• 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.
• FIG. 2 depicts one of the protocol option models, the Relay Layer Interface Protocol Option model 200, in which the application running on the TE2 device 102 manages the packet data services as well as the network addressing.
• the TE2 protocol stack is logically connected to the protocol stack of the MT2 device 104 over the R m interface.
• the R m 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 standards or protocols known to artisans of ordinary skill in the art may be used to define the transmission across the R m interface.
• R m interface standards include, the "UNIVERSAL SERIAL BUS (USB) SPECIFICATION, Revision 1.1", published in September 1998, and the "BLUETOOTH SPECIFICATION VERSION 1.0A CORE, published in July 1999, both incorporated by reference.
• the TIA/EIA-232-F standard is shown in FIG. 2 as specifying the R m 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) (i.e., the TE2 device 102) and the Data Circuit-Terminating Equipment (DCE) (i.e., the MT2 device 104).
• DTE Data Terminal Equipment
• DCE Data Circuit-Terminating Equipment
• 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.
• the TE2 device 102 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.
• 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.
• DTR Data-Terminal-Ready
• DSR Data-Set-Ready
• the TE2 device 102 Request-to-Send (RTS) signal 304 and the MT2 device 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.
• RTS Request-to-Send
• CTS Clear-to-Send
• 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- 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.
• TXD Transmit Data
• RXD Receive-Data
• 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 Comments 1661 (RFC 1661), entitled “THE POINT-TO-POINT PROTOCOL (PPP)", dated May 1992 and herein incorporated by reference.
• the PPP protocol configures, tests, and establishes the data link connection.
• the PPP protocol encodes the packets coming from upper protocol layers of the TE2102 device, "serializing" them to facilitate transmission.
• 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.
• the IWF 108 link layer 232 must be 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.
• the BS/MSC 106 initiates the connect operation by transmitting a Page Message to the MT2 device 104 and requesting a packet data service option.
• 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 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.
• other protocols may implement methods, other than Page messaging, to notify the MT2 device 104 of incoming calls. For example, under certain circumstances a message protocol operating on the U m 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 Forward and Reverse Traffic Channel Frames.
• the Traffic Channel assignment 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.
• 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.
• 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 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).
• receipt and processing of the ALERT WITH INFORMATION MESSAGE places the MT2 device 104 in a "WAITING FOR MOBILE STATION ANSWER SUBSTATE" 410.
• the MT2 device 104 sets a substate timer for a maximum of T 53m 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.).
• the MT2 device 104 If the subscriber answers the signaling MT2 device 104 within the T 53m 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 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.
• the MT2 device 104 must accept and process the ALERT WITH INFORMATION MESSAGE.
• 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 key.
• the MT2 device 104 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 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 R m (EIA-232F) interface.
• the TE2 device 102 may be a laptop or palmtop computer that is electrically coupled to the MT2 device 104 via the R m (EIA-232F) interface.
• the MT2 device 104 Before the MT2 device 104 can accept and process the ALERT WITH INFORMATION MESSAGE transmitted by the 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.
• 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 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 and is capable of transmitting and receiving packetized data.
• the 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 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 indicating that a point-to-point protocol packet was sent by the terminal device.
• FIG. 1 is a high level block diagram depicting various elements of a wireless communication system.
• 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.
• FIG. 5 is a state diagram illustrating an embodiment of the invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
• 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 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.
• the MT2 device 104 is coupled to the TE2 device 102 via the R m 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 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.
• the MT2 device 104 has been configured to detect ready-state control information. In other implementations, the MT2 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).
• 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 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 order places the MT2 device 104 into the "CALL ACTIVE STATE" 530.
• 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 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).
• 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 Ring Indicator signal (RI) on the R m interface to signify the existence of an 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.
• 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 R m 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 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 R m interface negotiation, the TE2 device 102 transmits PPP packets to the MT2 104 device. By detecting the control signal transition coming from the TE2 device 102, the MT2 device 104 is notified of an awaiting TE2 device 102.
• the MT2 104 device can still detect PPP packets by examining byte streams on the R m interface and looking for the PPP flag (i.e., 0x7E character) at the beginning of a packet. Accordingly, if, within the T 53m 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 procedure (see FIG. 4).
• the MT2 device 104 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 53m 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. 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 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.

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)

Priority Applications (5)

Applications Claiming Priority (2)

Publications (3)

Family

ID=23550209

Family Applications (2)

Family Applications After (1)

Country Status (7)

Families Citing this family (13)

Citations (3)

Family Cites Families (7)

• 2000
  • 2000-09-07 KR KR1020027003034A patent/KR20020029783A/ko not_active Application Discontinuation
  • 2000-09-07 JP JP2001522784A patent/JP4846948B2/ja not_active Expired - Lifetime
  • 2000-09-07 CA CA2384162A patent/CA2384162C/en not_active Expired - Fee Related
  • 2000-09-07 AU AU73577/00A patent/AU7357700A/en not_active Abandoned
  • 2000-09-07 CA CA002384168A patent/CA2384168A1/en not_active Abandoned
  • 2000-09-07 WO PCT/US2000/024622 patent/WO2001019099A2/en not_active Application Discontinuation
  • 2000-09-07 WO PCT/US2000/024623 patent/WO2001019027A2/en active Application Filing
  • 2000-09-07 IL IL14847700A patent/IL148477A0/xx unknown
  • 2000-09-07 CN CN00815410A patent/CN1387732A/zh active Pending
  • 2000-09-07 CN CNB008154457A patent/CN100361541C/zh not_active Expired - Fee Related
• 2010
  • 2010-10-08 JP JP2010228525A patent/JP2011055528A/ja not_active Withdrawn

Patent Citations (3)

Also Published As

Similar Documents

Legal Events