JP2003509917A - System and method for automatically determining when to respond to an incoming packet data call in a wireless communication network - Google Patents

Abstract

(57) Abstract: In a wireless communication network, a wireless communication device can determine when to respond to an incoming packet data call generated from a base station. A system and method for determining when to respond to an incoming packetized data call originating from a base station in a wireless communication network. The system includes a communication device (MT2) that interfaces with a wireless communication network, and a terminal device (TE2) that is electrically connected to the communication device and that can transmit and receive packetized data. The communication device (MT2) responds to a packetized data call coming from the base station in response to detecting a control signal or control information indicating a ready state of the terminal device (530). The terminal ready state indicator may be a high state data transmission ready signal or a low to high transition of the data transmission ready signal after the link indicator signal becomes active to alert the subscriber of an incoming call. Including control signals. The ready state indicator may also be control information, such as a point-to-point protocol packetized data indicator flag, embedded in the data stream generated by the terminal, or other indication that a point-to-point protocol packet has been transmitted by the terminal. Including information.

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to the field of wireless communications. In particular, the present invention relates to new and improved methods and systems for automatically determining when to answer an incoming packet data call in a wireless communication network.

[0002]

[Prior art]

Recent innovations in wireless communications and computer-related technologies and the unprecedented growth of Internet subscribers paved the way for mobile computing. In fact, the popularity of mobile computing has imposed on current communication infrastructures to provide more support to mobile users. A crucial part of meeting these needs and providing the necessary support to the users is the use of code division multiple access (CDMA) technology in wireless communication systems.

CDMA is a telecommunications title, "Mobile Station-Base Station Compatibility Standard for Dual-Mode Widespread Spread Spectrum Cellular Systems," issued July 1993, which is incorporated herein by reference. It is a digital radio frequency (RF) channelization technology defined in Industrial Standards Association / Electronic Industries Association Provisional Standard-95 (TIA / EIA IS-95). Wireless communication systems using this technique assign unique codes to communication signals and spread these communication signals in a common wide spread spectrum band. As long as the receiver in the CDMA system has the correct code, it can successfully detect and select its communication signal from other signals transmitted simultaneously for the same band. The use of CDMA increases system traffic capacity, improves overall call quality and noise reduction, and provides a reliable transport mechanism for data service traffic.

FIG. 1 is a simplified block diagram showing some of the basic elements of such a wireless data communication system 100. Those skilled in the art
It is readily understood that without limiting its scope or functionality, it can be modified, augmented, or conformed to known standards with its associated interface. The system 100 comprises a mobile terminal device, namely a TE2 device 102 (
For example, a device such as a laptop or palmtop computer) to communicate with an interworking function (IWF) 108. System 100 includes a wireless communication device, or mT2 device 104 (eg, a wireless telephone), and a base station / switch center (BS / MSC) 106. The IWF 108 acts as a gateway between the public switched telephone network and a wireless network, such as the Internet or a wired packet data network providing intranet-based access, and other networks. The L interface connects the IWF 108 to the BS / MSC 106. IWF 108 and BS / MSC 106 are often co-located. T
E2 device 102 is electronically connected to the MT2 device 104 via the _{R m} interface. The MT2 device 104 is connected to the BS / MSC via the radio interface U _m.
106. The TE2 device 102 and the MT2 device 104 can be integrated into a single device, or they can be separated as in the case of an installed cell phone where the laptop is the TE2 device 102 and the receiver is the MT2 device 104. You can also As shown in FIG. 2, it is important to note that the combination of TE2 device 102 and MT2 device 104, whether integrated or separated, is commonly referred to as mobile station (MS) 103.

The ability of a CDMA system to provide data service traffic is described in "Data Service Option for Wide Spread Spectrum Systems: Packet Data," published February 1998, which is incorporated herein by reference. It is recognized in TIA EIA IS-707.5 entitled "Services". This standard defines the requirements to support packet data transmission for the TIA / EIA IS-95 wide spread spectrum system and provides a set of packet data bearer services. Similarly, TIA / EIA IS-707-A., Entitled "Data Service Option for Spread Spectrum Systems: Packet Data Service," incorporated herein by reference and published in March 1999 together. 5 and TIA / EIA IS-707-A.5, entitled "Data Service Option for Spread Spectrum Systems: High Speed Packet Data Service". 9 also defines requirements for packet data transmission support for TIA / EIAIS-95 systems.

These standards refer to TE2 device 102 and IWF 10 via BS / MSC 106.
It is possible to use some packet data service options in the communication with. By doing so, IS-707.5 introduces two protocol option models. These models define the packet data protocol requirements for R _m interface. FIG. 2 shows one of the protocol option models, namely the relay layer interface protocol option model 200. In this model, applications running on TE2 device 102 manage packet data services as well as network addressing.

At the left end of FIG. 2 is a protocol stack, shown in a generally vertical format, depicting the protocol layers implemented on the TE2 device 102. TE2 protocol stack is logically connected to the protocol stack of the MT2 device 104 via the _{R m} interface. R _m interface, for example, is incorporated herein by reference, issued in October 1997, "between a data terminal equipment and data circuit terminating equipment using serial binary data replacement interface" titled It can comply with the TIA / EIA-232-F standard. It is understood that other standards or protocols known to those skilled in the art can be used to define the transmission across the R _m interface. For example, other applicable interface standards are published in November 1998, "Universal Serial Bus (USB) Specification, Revision 1.1," and July 1999, which are incorporated herein by reference. Includes published "BLUETOOTH Specification Version 1.0A Core".

Illustratively, the TIA / EIA-232-F standard is shown in FIG. 2 as defining the R _m interface. The TIA / EIA-232-F standard defines a physical interface as well as a data terminal equipment (DTE) (ie TE2 device 102).
Both a communication protocol for relatively slow serial data communication between the device and a data circuit-terminating equipment (DCE) (ie, MT2 device 104) are described. FIG. 3A shows the physical interface and lists the corresponding signals defined by the TIA / EIA-232-F standard.

FIG. 3B briefly shows the communication protocol provided by the TIA / EIA-232-F standard. According to the standard, the TE2 device 102 is a data terminal ready (DT
R) signal 320 is generated and signal 320 transitions from the low state to the high state, indicating that data transmission is ready. Similarly, MT2 device 104 generates a data set ready (DSR) signal 306, which transitions from the low state to the high state, indicating that it is ready to receive data. TE2 device 102
Request-to-send (RTS) signal 304 and MT2 device 104 clear-to-send (CTS) signal 305 are used to control the flow of data between TE2 device 102 and MT2 device 104. Remote DCE device (eg BS / MSC1
The MT2 device 104 activates the signal carrier to establish a link with the communication device at 06. The activation of this signal carrier triggers the MT2 device 104 data carrier detect (DCD) signal 308, transitioning from low to high, informing the TE2 device 102 that it is ready to exchange data. While the DCD signal 308 is high, the data are respectively transmitted data (
TXT) signal 302 and received data (RXD) signal 303 are transmitted and received. At the heart of the IS-707.5 relay layer interface protocol option, the major link layer connections are the TE2 equipment 102 and the IWF 108.
It is a concept that is established between. Therefore, MT2 device 104 sends the TE2 device frame through a Um interface, I via the _{R m} interface
It behaves as a pipe for sending WF108 frames. As shown in FIG. 2, the link layer protocols at both ends of the link PPP are incorporated herein by reference and are published in May 1992, "Point-to-Point Protocol (PPP)".
The relay layer interface protocol option implements a point-to-point protocol (PPP), as detailed in the requirements for comment entitled ". In essence, the PPP protocol configures, tests, and establishes a data link connection. In addition, the PPP protocol encodes packets from the TE2 device's 102 upper protocol layer and "serializes" the packets to facilitate transmission.

In order to support packet data services on CDMA systems, IS-
The 707.5 standard defines the following: That is, IWF 108 and MS1
03 (ie a combination of TE2 device 102 and MT2 device 104) uses a link layer connection symbolized by a relay layer interface protocol option model to facilitate the transmission of packet data. For example, the IWF 108 link layer 232 must be open. The IWF 108 must then request activation of the link layer connection for the packet data call destined for the TE2 device 102. The request for such activation is BS /
MT2 device 104 with packet data service option in MSC 106
It is obtained by instructing to connect to the TE2 device 102 via.

Generally, the BS / MSC 106 initiates a connect operation by sending a page message to the MT2 device 104 and requesting a packet data service option. According to the IS-95 standard, page messaging is used to announce incoming calls, including incoming packet calls, to MT2 device 104 and is incorporated into the overhead paging channel of the forward link channel. When the MT2 device 104 responds with a page response message with a valid service option number, BS / MSC1
06 assigns a traffic channel to the MT2 device 104. The page response message is sent via the access channel of the reverse link channel. So being said, it is important that other protocols be able to perform methods other than page messages to inform the MT2 device 104 of the incoming call. For example, under some circumstances, the message protocol operating on the _Um interface is
The traffic channel can be provided directly to the BS / MSC 106 without having to notify the MT2 device 104 of the incoming call.

The traffic channel provides transfer of packet data between the BS / MSC 106 and the TE2 device 102, and consists of a combination of forward traffic channel frames and reverse traffic channel frames. The traffic channel assignment is established by first initializing the channel for MT2 device 104, then negotiating a packet data service option connection with TE2 device 102, and then negotiating with TE2 device 102 for the requested service option. To be done.

FIG. 4 illustrates the MT2 device 104 and BS / M after the traffic channels have been assigned.
FIG. 6 is a high-level state diagram showing a general permutation with the SC 106. After allocation, the IS-95 standard allows the BS / MSC 106 to send an "alert with information message" to the MT2 device 104 on the forward link. This information message alert is BS
/ MSC 102, which includes signaling information from the MSC 102, which facilitates MT2 devices notifying the subscriber of an incoming call (eg, ringing with a possibly different tone and pattern).

As shown in FIG. 4, the MT2 device 104 receives and processes the alert with the information message.
Is set to “wait for mobile station response substate” 410. Upon entering substate 410, MT2 device 104 sets the substate timer for a maximum of T ₅₃ ms. Then, the MT2 device 104 sends the signaling information (
That is, wait for the subscriber to answer the incoming call by responding to an audible "ringing" pattern, a visual "flash" on the screen, etc.). MT2 device 10 if subscriber responds to signaling MT2 device 104 within T _{5 3} msec time
4 sends a "connect command" to BS / MSC 106. As a result, the MT2 device 1
04 becomes "conversational substate" 430. MT2 device 104 then proceeds to communicate with BS / MSC 106 by processing forward traffic channel frames and reverse traffic channel frames. On the other hand, if the subscriber does not respond to the signaling MT2 device 104, the sub-state timer expires, causing the MT2 device 104 to enter the "transmitter disable substate" 420. In substate 420, MT2 device 104 disables the transmitter, releases the traffic channel, and ends the call.

As described above, when the MT2 device 104 becomes “waiting for mobile station response substate”, the MT2 device 104 must accept and process the “alert with information message”. Processing of this message is typically relatively automatic for voice calls and will ring the MT2 device. The subscriber then responds to the ringing MT2 device by picking up the handset or pressing a preprogrammed function.

However, unlike an incoming voice call, there is no clearly defined procedure that defines how the MT2 device 104 answers an incoming packet data call. For example, to inform the subscriber, instead of just ringing or flashing, M
The T2 device 104 has additional elements in handling packet data calls,
That is, the TE2 device 102, which is the ultimate purpose of the incoming packet data call, must be considered. As mentioned above, the TE2 device 102 has R _m (EIA-232F).
It can be a laptop or palmtop computer electrically connected to the MT2 device 104 via an interface. Therefore, MT2 device 104 is BS
Before the alert with informational message sent by the / MSC 106 can be accepted and processed, the MT2 device 104 must determine whether the TE2 device 102 is ready or can connect and exchange packet data. .

Therefore, there is a need for new methods and systems that allow a wireless communication device to determine when to answer an incoming packet data call.

[0018]

The present invention provides a system and method in a wireless communication network that allows a wireless communication device to determine when to respond to an incoming packet data call originated from a base station. Strive to solve the above mentioned needs.

Systems and methods consistent with the principles of the invention as embodied and broadly described herein include a communication device that interfaces with a wireless communication network, and a device that is electrically connected to the communication device to send and receive packetized data. Including possible terminal devices. The communication device responds to a packetized data call coming from the base station in response to detecting a control signal or control information indicating the ready state of the terminal device. This terminal equipment ready state indicator may be a high state data transmission ready signal or a transition from a low state to a high state of the data transmission ready signal after the ring indicator signal has been activated to alert the subscriber of an incoming call. Includes control signals. 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 by the terminal, or other indication that a point-to-point protocol packet has been transmitted by the terminal. Information can be included.

[0020]

DETAILED DESCRIPTION OF THE INVENTION

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description, serve to explain the objects, advantages and principles of the invention.

The following detailed description of the invention refers to the accompanying drawings which illustrate preferred embodiments consistent with the invention. Other embodiments are possible and various modifications may be made to the embodiments without departing from the spirit and scope of the invention. Therefore, the following description is not meant to limit the invention. Rather, the scope of the invention is defined by the appended claims.

The embodiments of the invention described below include elements shown in the figures (ie, TE2 device 10).
2, MT2 device 104, BS / MSC 106 and IWF 108) can be implemented in various ways, including software, firmware and hardware. The actual software code or control hardware used to implement the present invention is not limiting of the present invention. Therefore, the operation and operation of the present invention will be described without specific reference to actual software code components or hardware components. It is acceptable without such specific reference. It is easily understood that those skilled in the art can design software and hardware for implementing the embodiments of the present invention based on the description herein.

FIG. 5 is a high level state diagram of an embodiment of the present invention. Accordingly, FIG. 5 details the operation of the MT2 device 104 for accepting, processing and answering an incoming packet data call.

The MT2 device 104 begins in an “idle state” 510. In this state, no traffic channel is established between BS / MSC 106 and MT2 device 104 to provide packet data traffic. Therefore, the MT2 device 104 originates or receives any type of call.

As mentioned above, the MT2 device 104 is connected to the TE2 device 102 via the R _m interface. And the signaling between the two devices is TIA / EIA-
It can be obtained according to standards such as 232-F or USB. These standards provide control information or control signals that indicate the ready state of the TE2 device 102. Such TE2 device 102 ready state control information includes USB packets embedded with ready state information as well as TIA / EIA-232-F DT.
Includes R signal. In some further implementations, MT2 device 104 was configured to detect ready state control information. In another implementation, MT2
Device 104 was not specifically instructed to ignore the ready state control signal. (For example, the Hayes standard dialing command string'AT & D0 'was not set to ignore the TIA / EIA-232-F DTR signal.) In either case, the present invention provides such ready state control information. This information is used to trigger the MT2 device 104 to respond to incoming and incoming packet data calls. For example, if the MT2 device 104 receives a page message from the BS / MSC 106 requesting a packet data service option, the MT2 device 104 automatically detects an incoming packet data call upon detecting ready state control information / signalling. Will respond. This automatic response is I
A connection command (CONNECT ORDER) that matches the S-95 procedure (see FIG. 4)
) To the BS / MSC 106. This instruction puts the MT2 device 104 into a "call active state" 530.

The MT2 device 104 receives a page message with a packet data service option, and the MT2 device 104 is interested in ready state control information / signals (
For example, when the DTR signal) cannot be detected, or when a "low state" ready state control signal is detected (for example, the TE2 device 102 is physically MT2).
(Not connected to device 104), MT2 device 104 proceeds to process page state 520. This state is similar to the MS response substate wait (see FIG. 4) defined in the IS-95 standard.

Since the low ready state control signal cannot indicate the presence of a waiting TE2 device 102, the MT2 device 104 in state 520 indicates a ring indicator on the R _m interface to indicate the presence of an incoming packet data call. signal(
RI) will be toggled. The RI toggle may be configured to trigger an alert signal (eg, audible tone / pattern or visible blink / message) to signal an incoming packet data call to the subscriber. After the RI toggle and within the T _53m second time limit of the T _53m wait for MS response _substate 430, the MT2 device 104 detects a ready state control signal transition from low to high (ie a DTR signal transition). If, or when detecting a PPP packet on _{R m} interface, MT2 104 proceeds to "call active state" 530.

For example, if the TE2 device 102 was previously disconnected from the MT2 104 and the audible or visible signal output by the RI toggle prompts the subscriber to reconnect the two devices, the ready state control. Signal transitions and the presence of PPP packets can occur. After reconnecting the two devices, the TE2 device 102 packet data application drives the ready state control signal to the high state, and the TE2 device 102 sends a PPP packet to the MT2 device 104, usually after R _m interface negotiation. By detecting the control signal transition coming from the TE2 device 102, the MT2 device 104 is notified of the waiting TE2 device 102. Further, if the MT2 device 104 cannot detect ready state control information / signals or is instructed to ignore such signals (eg, DTR).
By sending an AT command dialing string 'AT &D0' to ignore signals), MT2 device 104 examines the byte stream of the _{R m} interface, to look for PPP flag (i.e. 0x7E character) at the start of a packet Can still detect a PPP packet. Therefore, if the MT2 device 104 detects either (1) ready state control signal transition or (2) PPP packet flag within the T _53m time limit, the MT2 device 104 sends a connect command that matches the IS-95 procedure to the BS. / MSC
Answer incoming packet data call by sending to 106 (see FIG. 4)
.

On the other hand, when the MT2 device 104 does not detect the ready state control signal or the PPP flag within the T _53m time limit, the MT2 device 104 times out and returns to the idle state 510. As mentioned above, in this state the MT2 device 104 can originate or receive any type of call.

MT2 device 104 enters call active state 530 when MT2 device 104 answers the call by sending a connect command to BS / MSC 106. This state is similar to the conversation substate 430 described in the IS-95 standard. In state 530, MT2 device 104 processes packet data traffic by processing forward and reverse traffic channel frames to BS / M.
Replace with SC106.

Therefore, this embodiment provides MT when to answer an incoming packet data call.
2 provides a system and method that allows the device 104 to make decisions.

The above description of the preferred embodiments of the present invention provides an illustration and description, but is not exhaustive or limited to the precise form disclosed. Variations consistent with the above disclosure are possible or can be obtained from practice of the invention. Accordingly, the scope of the invention is defined by the claims and their equivalents.

[Brief description of drawings]

[Figure 1]   FIG. 3 is a high-level block diagram illustrating various elements of a wireless communication system.

[Fig. 2]   1 schematically shows a protocol stack of a wireless communication system.

FIG. 3A   2 shows the TIA / EIA-232-F protocol.

FIG. 3B   2 shows the TIA / EIA-232-F protocol.

[Figure 4]   It is a state diagram which shows operation | movement of a wireless communication apparatus.

[Figure 5]   It is a state diagram showing an embodiment of the present invention.

[Explanation of symbols]

102 ... TE2 device 104 ... MT2 device 106 ... BS / MSC 108 ... IWF 510 ... Idle state 520 ... Process page state 530 ... Call active state

─────────────────────────────────────────────────── ─── Continued front page    (81) Designated countries EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, I T, LU, MC, NL, PT, SE), OA (BF, BJ , CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, K E, LS, MW, MZ, SD, SL, SZ, TZ, UG , ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AG, AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, BZ, C A, CH, CN, CR, CU, CZ, DE, DK, DM , DZ, EE, ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, K E, KG, KP, KR, KZ, LC, LK, LR, LS , LT, LU, LV, MA, MD, MG, MK, MN, MW, MX, MZ, NO, NZ, PL, PT, RO, R U, SD, SE, SG, SI, SK, SL, TJ, TM , TR, TT, TZ, UA, UG, UZ, VN, YU, ZA, ZW [Continued summary] Point-to-Point Protocol Packetized Data In Control information, such as a indicator flag, or points Two-point protocol packet sent by terminal Includes other information indicating that it has been done.

Claims (16)

[Claims] 1. A system for determining when to answer an incoming packetized data call in a wireless communication network, comprising: a communication device for interfacing with the wireless communication network; and the communication. A terminal device connected to the device for transmitting and receiving packetized data, wherein the communication device is responsive to the incoming packetized data call in response to detecting a ready state indicator generated by the terminal device. respond. 2. The system of claim 1, wherein the ready state indicator comprises a high state data transmission ready signal. 3. The ready state indicator is a low state of a data transmission ready signal after a ring indicator signal on the communication device has been activated to alert a subscriber of the incoming packetized data call. The system of claim 2, including a transition from a to a high state. 4. The system of claim 3, wherein the ready state indicator includes information indicating transmission of point-to-point protocol packetized data in a data stream generated from the terminal device. 5. A method for determining when to answer an incoming packetized data call in a wireless communication network comprising the steps of: interfacing a communication device with the wireless communication network; Connecting to a communication device, the terminal device being capable of transmitting and receiving packetized data; detecting a ready state indicator generated by the terminal device by the communication device; and by the communication device Responsive to the incoming packetized data call in response to detecting the ready state indicator. 6. The method of claim 5, wherein the ready state indicator comprises a high state data transmission ready signal. 7. The ready state indicator is a low state of a data transmission ready signal after a ring indicator signal on the communication device has been activated to alert a subscriber to the incoming packetized data call. 7. The method of claim 6, including a transition from to high state. 8. The method of claim 7, wherein the ready state indicator includes information indicating transmission of point-to-point protocol packetized data in a data stream generated from the terminal device. 9. A wireless communication device capable of determining when to respond to a packetized data call in a wireless communication network, comprising: means for interfacing with said wireless communication network; connected to a terminal device Means for transmitting and receiving packetized data; means for detecting a ready state indicator generated by the terminal apparatus; and said arriving in response to detecting the ready state indicator A means of responding to packetized data calls. 10. The communication device of claim 9, wherein the ready state indicator includes a high state data transmission ready signal. 11. The ready state indicator is a low state of a data transmission ready signal after a ring indicator signal on the communication device has been activated to alert a subscriber to the incoming packetized data call. 11. The communication device of claim 10, including a transition from to high state. 12. The communication device of claim 11, wherein the ready state indicator includes information indicating transmission of point-to-point protocol packetized data in a data stream generated by the terminal device. 13. A machine-readable medium encoded with a plurality of instructions executable by a processor to perform the following processes: enabling a communication device to interface with a wireless communication network; Enable communication, the terminal device can send and receive packetized data; the communication device detects a ready state indicator generated by the terminal device; and the communication device enables the ready state Responsive to an incoming packetized data call in response to the detection of the indicator. 14. The machine-readable medium of claim 13, wherein the ready state indicator includes a high state data transmission ready signal. 15. The ready state indicator is a low state of a data transmission ready signal after a ring indicator signal on the communication device is activated to alert a subscriber of the incoming packetized data call. 15. The machine-readable medium of claim 14, including a transition from to high state. 16. The machine-readable medium of claim 14, wherein the ready-state indicator includes information indicating transmission of point-to-point protocol packetized data in a data stream generated by the terminal device.