KR20000015296A - Method of displaying communication failing reason in second generation cordless telephone - Google Patents

Abstract

PURPOSE: A displaying method is provided to rapidly and effectively display a communication failing reason in a second generation cordless telephone (CT2). CONSTITUTION: The CT2 is provided with a memory in which a received signal strength indicator and a message of indicating a communication failing reason are stored. The method comprises a first step of inspecting whether the phone is liked when communication key is input, a second step of detecting the received signal strength indicator if the phone link is failed and comparing the detected received signal strength indicator with the predetermined received signal strength indicator stored in the memory, and a third step of displaying that the phone is out of a service area if the detected received signal strength indicator is smaller than the predetermined received signal strength indicator and determining whether the link failing is an error by a channel occupation based on a link status information transmitted from a base station and outputting a corresponding message from the memory if the detected received signal strength indicator is greater than the predetermined received signal strength indicator. Thereby, a user can rapidly recognize the communication failing reason.

Description

How to identify the cause of a call failure in next-generation digital cordless phones

The present invention relates to a method of displaying the cause of a call failure in a next generation digital wireless telephone, and more particularly, a method of displaying a call failure cause by detecting link state information transmitted from a base station and displaying the cause of the call on a liquid crystal display (LCD). It is about.

In general, 2nd Generation Cordless Telephone (hereinafter referred to as "CT2") is a transmission-only communication terminal, which is called a telepoint in a public base station or a body of a radiotelephone. Communicate using a home base station with the added points. The call range of the CT2 terminal is 200 meters in the radius where the telepoint is installed, and the number of channels has 40 channels for one telepoint. In addition, two to six public telephone lines are allocated to a public base station, which allows two to six users to communicate at the same time. The conventional CT2 terminal does not form a call link when the channel is all occupied by another CT2 terminal or when all the public telephone lines assigned to the public base station are occupied or when the CT2 terminal is out of the service area of the base station. In this case, the CT2 terminal outputs only a specific message (eg, "No Service") to the liquid crystal display and does not indicate the cause of the call failure.

In order to solve this problem, the previously applied application No. 97-69981 proposes a method of displaying the cause of the call failure by the method as shown in FIG. In detail, referring to FIG. 1, in step 101 where the reception mode is enabled, the controller checks whether a call key is input from the key input unit. At this time, when the call key is input from the key input unit, the control unit transmits a multiplex (hereinafter referred to as "MUX") 3 signal pattern to the base station according to a known CT2 communication protocol. The MUX3 signal pattern includes a signal channel and a synchronization channel, and includes channel (link) request data. After transmitting the MUX3 signal pattern, the controller proceeds to step 103 and determines whether a link is formed by checking whether a MUX2 signal pattern is received from a home base station or a public base station in response to the MUX3 signal pattern. . The MUX2 signal pattern includes channel grant data with a signal channel and a synchronization channel like the MUX3 signal pattern. When the MUX2 signal pattern is received in step 103 and a call is established, the controller proceeds to step 105 and displays a first link status message (eg, “SPEECH” or “call”) on the display unit 14. When the first link status message is displayed, the controller sets the active mode to supply power to the RF unit in step 107 to initiate a call.

On the other hand, if a call is not established because the MUX2 signal pattern is not received from the base station, the controller displays a second link status message (eg, “NO SERVICE”) on the display unit. When the second link status message is displayed, the control unit sets the active mode in step 111 and proceeds to step 113 to check whether the first predetermined time is exceeded. The first predetermined time is 30 sec as the time to maintain the active mode, and enables the reception mode for the first predetermined time. If the first schedule time is exceeded in step 113, the controller sets the CT2 terminal to the standby-by mode in step 115. The stand-by mode is maintained until an arbitrary key is input from the key input unit and repeats the sleep mode and the active mode. In the standby mode, the active mode is maintained for a second predetermined time, and the second predetermined time is typically maintained for 150 ms. The sleep mode is maintained for 1200 ms. The sleep mode is a mode for supplying power only to the receiver for measuring the received field strength (RSSI) and disabling the transmission mode. Therefore, the standby mode is a 150ms active mode and 1200ms sleep mode is repeated. In other words, the channel strength is detected by channel scanning for 150 ms. However, if the channel requested by the controller is used by another CT2 terminal, the active mode holding time exceeds 150 ms. Therefore, in order to implement the present invention, the controller proceeds to step 117 to check the channel scanning time interval to check whether the active mode holding time exceeds 150 ms. If the active mode holding time does not exceed 150 ms in step 117, the controller proceeds to step 121 and displays a call second cause of failure message (eg, Out Of Area). However, if the active mode holding time exceeds 150ms, the controller proceeds to step 119 and displays a first call failure cause message (eg, Busy or Channel Occupied).

However, although the method of FIG. 1 is alright to inform the above-mentioned problem, that is, the cause of the call failure, the time spent on the "display of the second link status message" and the setting in the active mode is too long (generally, There are disadvantages that do not inform the user more quickly and effectively the cause of the call failure.

Therefore, an object of the present invention is to detect the link state information included in the received signal strength indicator (RSSI) and the fixed length packet format transmitted from the base station to determine the cause of the call failure. It provides a method to quickly and effectively indicate the cause of the call failure.

In order to achieve the above object, the present invention provides a call failure cause display method of a next generation digital wireless telephone having a memory storing a message storing a constant received electric field strength and a call failure cause message. A first step of checking whether a call link is formed; a second step of detecting a received field strength if the call link is not formed, and checking whether the received field strength is greater than a predetermined received field strength previously stored in the memory; And if the detected received electric field strength is smaller than the predetermined received electric field strength, indicating that the service field is out of service range, and if the detected received electric field strength is smaller than the predetermined received electric field strength, and if the received electric field strength is large, determining whether an error according to channel occupancy is determined according to link state information transmitted from a base station. And a third process of detecting and displaying a corresponding call failure cause message. do.

1 is a flowchart illustrating a method of displaying a cause of a call failure in a next generation digital wireless telephone for solving the problem according to FIG. 1;

Figure 2 is a block diagram of a next generation digital radiotelephone to which the present invention is applied.

Figure 3 is a block diagram of a next generation digital wireless telephone according to an embodiment of the present invention.

4 is a diagram showing the configuration of a fixed length packet format applied to the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. First, in adding reference numerals to the components of each drawing, it should be noted that the same reference numerals have the same reference numerals as much as possible even if displayed on different drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

2 is a block diagram of a next generation digital radiotelephone to which the present invention is applied.

Hereinafter, the configuration according to the present invention will be described with reference to FIG. 2, and the controller 10 may control the overall operation and may be implemented as a one chip microprocessor. The memory 11 has a ROM for storing a predetermined program for controlling the overall operation and a RAM for temporarily storing data generated during the execution of the program. In particular, the memory 11 stores predetermined RSSI level values and link state traffic lights, and text and voice data indicating a cause of a call failure. The key input unit 13 includes a plurality of numeric keys and function keys and generates key data for the keys. The display unit 12 displays key data input from the key input unit 13, and displays an operation state and a plurality of information by an icon. The radio frequency unit (hereinafter referred to as an "RF unit") filters, modulates, and demodulates a radio signal transmitted and received through a CT2 antenna. The voice processor 14 processes the voice signal input through the microphone 15 and processes the signals received from the RF unit 20 and the wireless caller 20 to process the speaker 15 and the buzzer 16. Send out voice and buzzer sound.

The RF unit 20 will be described in more detail. The RF unit 20 includes a transmitter / receiver separator 24, a transmitter 21, a frequency synthesizer 22, and a receiver 23. The frequency combiner 22 generates a frequency for designating a transmission / reception channel of the transmitter 21 and the receiver 23 under the control of the controller 10. The transmission / reception separator 24 separates a signal to be transmitted through the CT2 antenna 25 and a signal received to the receiver 23 through the antenna 25. The receiver 23 performs a frequency conversion by filtering and low noise amplifying the radio signal separated by the transmitter / receiver separator 24 and outputs the frequency signal to the signal processor 14. In particular, the receiver 23 measures a receiver signal strength indicator (RSSI) level through a window. The transmitter 21 frequency-converts the signal input from the signal processor 14 and outputs the signal to the transmitter / receiver separator 24 in the form of a radio signal.

3 is a flowchart illustrating a method for displaying a call failure origin of a next generation digital wireless telephone according to an exemplary embodiment of the present invention, and FIG. 4 is a diagram illustrating a fixed length packet format applied to the present invention.

Before describing FIG. 3, the configuration of the fixed length packet format will be described with reference to FIG.

The fixed length packet format includes a handset identification code (HIC), a manufacturer identification code (MIC), a link identification code (LIC), and a check bit for checking an error. The handset identification code includes a signaling rate bit (SR), a link status bit (LS), a fixed length packet bit (FT), and an address code word. If the signaling rate bit is "1", it is MUX1, 4. If "0", it is MUX1, 2. The link status bit is composed of a first link status bit and a second link status bit, each of which consists of one bit. If the link status bit is "00 (first link status bit, second link status bit)", it is link request data, and if "1", it is channel grant data. And if the link status bit is " 10 " ID-OK, " 11 " If the link status bit is "10" or "11", it indicates that handshaking (Handshaking-initial call setup).

Hereinafter, referring to FIG. 3, first, the CT2 terminal should have a reception mode in an enabled state. In step 401, the enabled state, the controller 10 checks whether a call key is input from the key input unit 13. At this time, when the call key is input, the controller 10 transmits the MUX3 signal pattern to the base station according to a known CT2 communication protocol. The MUX3 signal pattern includes a signal channel and a synchronization channel, and includes link request data (LS = 00). After transmitting the MUX3 signal pattern, the controller 10 proceeds to step 403 and checks whether the MUX2 signal pattern is received from the base station in response to the MUX3 signal pattern. This is to check if the call link is formed. The MUX2 signal pattern has a signal channel and a synchronization channel like the MUX3 signal and includes channel grant data (Link Grand: LS = 01). When the MUX2 signal pattern is received, the controller 10 forms a call path in step 417 and displays a first link status message (for example, "call" or "SPEECH") on the display unit 12 or the buzzer 16 or the speaker through the signal processor 14. The user is informed via 15. After the call link is formed, the signal pattern of MUX1 is exchanged between the CT2 terminal and the base station according to a known CT2 communication protocol. At this time, the link state signal of FIG. 4 is composed of "10" (ID_Ok) or "11" (ID_Lost). This process is called handshaking. If the MUX2 signal is not received from the base station in step 403, the controller 10 proceeds to step 405 to switch to the second link state mode. The second link state mode is a state in which a call failure is determined and analyzes the cause of the call failure. When switching to the second link state mode, the controller 10 detects the RSSI in step 407 and compares a predetermined level of the RSSI (eg, -95 dBm) previously stored in the memory 11. As a result of the comparison, if the detected RSSI is equal to or larger than the predetermined level of the RSSI, the controller 10 proceeds to step 409 and checks the link status bit. If the detected RSSI is smaller than the predetermined level of the RSSI, the controller 10 proceeds to step 415. The two-call failure cause message ("out of call right" or "OUT OF RANGE") is displayed on the display unit 12, and the user is notified via the speaker 15 or the buzzer 16 through the signal processing unit 14.

After checking the link status bit in step 409, the controller 10 checks whether the second link status bit of the link status bit is “1” in step 411. This is to check if the CT2 terminal is handshaking. As a result of the check, if the second link status bit is "1", the flow proceeds to step 413 to display the first call failure cause message (Busy or Channel Occupied) on the display unit 12 or to another user through the speaker 15 or the buzzer 16. If the second link status bit is " 0 ", it proceeds to step 415 and displays the second call failure cause message on the display unit 12.

As described above, the present invention displays the cause of the call failure based on the received electric field strength and the link state information transmitted from the base station, so that the user can quickly determine the cause of the call failure.

Claims (1)

Claims [1] A method for displaying the cause of a call failure in a next generation digital cordless telephone having a memory for storing a message storing a certain received field strength and a cause for a call failure. A first step of checking whether a call link is formed when a call key is input; A second step of detecting a received electric field strength when the communication link fails to be formed, and checking whether the received electric field strength is greater than a predetermined received electric field strength previously stored in the memory; If the detected received electric field strength is smaller than the predetermined received electric field strength, it indicates that the service area is out of range, and if the received electric field strength is larger, the corresponding call fails from the memory by determining whether an error according to channel occupancy is determined according to link state information transmitted from the base station. And detecting the cause message and displaying the cause message.