KR20090067559A - Access terminal and method for linking call thereof - Google Patents

Access terminal and method for linking call thereof Download PDF

Info

Publication number
KR20090067559A
KR20090067559A KR1020070135254A KR20070135254A KR20090067559A KR 20090067559 A KR20090067559 A KR 20090067559A KR 1020070135254 A KR1020070135254 A KR 1020070135254A KR 20070135254 A KR20070135254 A KR 20070135254A KR 20090067559 A KR20090067559 A KR 20090067559A
Authority
KR
South Korea
Prior art keywords
qos
qos setting
request
call connection
communication terminal
Prior art date
Application number
KR1020070135254A
Other languages
Korean (ko)
Inventor
김성식
김정림
Original Assignee
삼성전자주식회사
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 삼성전자주식회사 filed Critical 삼성전자주식회사
Priority to KR1020070135254A priority Critical patent/KR20090067559A/en
Publication of KR20090067559A publication Critical patent/KR20090067559A/en

Links

Images

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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The present invention relates to a communication terminal and a call connection method thereof, and to a wireless communication unit for connecting a call, requesting a quality of service (QoS) setting when a call connection request is requested, and re-requesting the QoS setting if the QoS setting fails. If the QoS setting is successful, a communication terminal including a control unit for controlling the call connection and a memory for storing the number of repetition requests set to re-request the QoS setting under the control of the control unit and requesting QoS setting when the call connection request is made. And if the QoS setting fails, changing the number of QoS setting requests, and if the number of QoS setting requests is equal to or less than the set number of repetitive requests, re-requesting the QoS setting, and if the QoS setting is successful, connect the call. It provides a call connection method comprising the step of. According to the present invention, even if the user of the communication terminal does not repeatedly generate a request for call connection, the communication terminal may repeatedly request the call connection. Thus, the user of the communication terminal does not have to generate a request for call connection again whenever the call connection fails. Accordingly, there is an advantage that the convenience of the communication terminal user is improved.

Description

ACCESS TERMINAL AND METHOD FOR LINKING CALL THEREOF

The present invention relates to a communication terminal and a call connection method thereof, and to a communication terminal and a call connection method thereof of a communication system for providing a packet data service.

In general, a communication system has been developed for a user to perform communication without being restricted by a specific place or a wired line. As an example of such a communication system, the Code Division Multiple Access (CDMA) 2000 1x system is an evolved communication system from a typical second generation CDMA system. The CDMA2000 1x system provides wireless data service at a rate of 144 Kbps, which is 56 Kbps faster than the second generation CDMA system. Furthermore, the CDMA2000 1xEVDO (Evolutionary Data in Data Only) system is a communication system proposed for high-speed data transmission at the International Mobile Telecommunications (IMT) -2000 level. The CDMA2000 1xEVDO system allows high-speed data transmission by allocating entire resources for data services only. In other words, the CDMA2000 1xEVDO system supports packet-based communication rather than circuit-based communication. In such a communication system, a communication terminal may perform communication by performing a call connection through a base station.

However, the communication terminal of the communication system as described above requests call connection only once, regardless of whether the call connection is successful or not, according to the call connection request of the user of the communication terminal. That is, the communication terminal requests a call connection and then, even if the call connection fails, does not request the call connection anymore. For this reason, when the user of the communication terminal generates a request for call connection again, the communication terminal requests the call connection again. Accordingly, there is a problem that the convenience of the communication terminal user is lowered.

In a call connection method of a communication terminal according to the present invention for solving the above problems, a process of requesting a Quality of Service (QoS) setting when a call connection request is made, and if the QoS setting fails, changing the number of QoS setting requests And if the QoS setting request number is less than or equal to the set repetition request number, re-requesting the QoS setting, and if the QoS setting is successful, connecting the call.

In addition, the communication terminal according to the present invention for solving the above problems, the wireless communication unit for connecting a call, and when the call connection request, the QoS setting request, if the QoS setting fails, re-request the QoS setting And a control unit controlling to connect the call when the QoS setting is successful, and a memory storing the number of repetition requests set to re-request the QoS setting under the control of the control unit.

Therefore, the communication terminal and the call connection method according to the present invention as described above, even if the user of the communication terminal does not repeatedly generate a request for call connection, the communication terminal can repeatedly request the call connection. That is, after requesting a call connection, if the call connection fails, the communication terminal requests the call connection a set number of times. Thus, the user of the communication terminal does not have to generate a request for call connection again whenever the call connection fails. Accordingly, there is an advantage that the convenience of the communication terminal user is improved.

Hereinafter, exemplary embodiments will be described in more detail with reference to the accompanying drawings.

1 is a configuration diagram showing a schematic configuration of a communication system having a communication terminal according to an embodiment of the present invention. In the present embodiment, a description will be given on the assumption that the communication system is a CDMA2000 1xEVDO system.

Referring to FIG. 1, the communication system of the present embodiment includes a plurality of communication terminals (Access Terminals AT) 110 and 170, base stations Access Nodes 120 and 160, and packet data service nodes. PDSNs 130 and 150 and a Session Initiation Protocol server 140. At this time, each base station (120, 160) is connected to each communication terminal (110, 170) via a wireless channel. Each of the packet data service nodes 130 and 150 provides a packet data service to the communication terminals 110 and 170 through the base stations 120 and 160. In addition, the SIP server 140 transfers packet data between the communication terminals 110 and 170. Although not shown, the communication system provides a charging and authentication server (Authentification, Authorization, and Accounting; AAA) for exchanging necessary information with the packet data service node 130 to provide a packet data service to the communication terminal 100. And a data register (DR).

2 is a flowchart illustrating a signal flow when performing a call connection procedure in the communication system of FIG. 1. In the present embodiment, it is assumed that the first communication terminal, the first base station, and the first packet data service node are the calling party, and the second communication terminal, the second base station, and the second packet data service node are the receiving party of the call. do.

Referring to FIG. 2, the call connection procedure of the communication system according to the present embodiment starts from the first communication terminal 110 detecting a call origination request in step 211. Thereafter, the first communication terminal 110 establishes traffic with the first base station 120 in step 213.

Next, the first communication terminal 110 requests the QoS setting in step 215. In operation 217, the first communication terminal 110 performs QoS negotiation with the first base station 120. That is, the first communication terminal 110 proposes resources of a desired codec, such as audio, video, control flow, and QoS, to the first base station 120. At this time, the first base station 120 checks whether it is possible to provide resources and QoS of the proposed codec. And if it is possible to provide resources and QoS of the proposed codec, the first base station 120 provides the resources and QoS of the proposed codec to the first communication terminal 110. On the other hand, if it is impossible to provide resources and QoS of the proposed codec, the first base station 120 modifies the resources and QoS of the proposed codec according to a predetermined rule, and then checks whether it is possible to provide. Also, as a result of the check, if it is possible to provide the resource and QoS of the modified codec, the first base station 120 provides the resource and QoS of the modified codec to the first communication terminal 110. In other words, if one of the resources of the codec and the QoS is provided, the first communication terminal 110 considers that the QoS negotiation is successful. Or if the resource and the QoS of the codec are not provided, the first communication terminal 110 considers that the QoS negotiation has failed.

Next, in step 219, the first communication terminal 110 performs a reservation of the Resorce ReserVation Protocol (RSVP) with the first packet data service node 130. That is, the first communication terminal 110 requests the first packet data service node 130 for QoS support. At this time, the first packet data service node 130 checks whether it is possible to support the required QoS. Here, the first packet data service node 130 may establish an RSVP path or the like capable of supporting the required QoS. If it is possible to support the requested QoS as a result of the check, the first packet data service node 130 approves the requested QoS and notifies the first communication terminal 110. That is, if the requested QoS is approved, the first communication terminal 110 considers that the RSVP reservation is successful. Or if the required QoS is not approved, the first communication terminal 110 considers that the RSVP reservation has failed.

Next, if QoS negotiation and RSVP reservation succeed, the first communication terminal 110 sets QoS in step 221. Although not shown at this time, if at least one of QoS negotiation or RSVP reservation fails, the first communication terminal 110 may repeat steps 215 to 219. Thereafter, the first communication terminal 110 transmits an invitation message in step 223. When receiving the invitation message, the SIP server 140 transmits the invitation message in step 225. In addition, when receiving the invitation message, the second base station 160 establishes traffic with the second communication terminal 170 in step 227 and then transmits the invitation message in step 229.

Subsequently, upon receiving the invitation message, the second communication terminal 170 requests QoS setting in step 231. Thereafter, the second communication terminal 170 performs QoS negotiation with the second base station 160 in step 233. That is, the second communication terminal 170 proposes resources of a desired codec, such as audio, video, control flow, and QoS, to the second base station 160. At this time, the second base station 160 checks whether it is possible to provide resources and QoS of the proposed codec. If it is possible to provide resources and QoS of the proposed codec, the second base station 160 provides the resources and QoS of the proposed codec to the second communication terminal 170. On the other hand, if it is impossible to provide the resources and QoS of the proposed codec, the second base station 160 modifies the resources and QoS of the proposed codec according to a predetermined rule, and then provides the resources and QoS of the modified codec. Check if it is possible. Also, as a result of the check, if it is possible to provide the resource and QoS of the modified codec, the second base station 160 provides the resource and QoS of the modified codec to the second communication terminal 170. That is, if one of the resources of the codec or QoS is provided, the second communication terminal 170 considers that the QoS negotiation is successful. Or if the resource and the QoS of the codec are not provided, the second communication terminal 170 considers that the QoS negotiation has failed.

In operation 235, the second communication terminal 170 performs RSVP reservation with the second packet data service node 150. That is, the second communication terminal 170 requests the second packet data service node 150 for QoS support. At this time, the second packet data service node 150 checks whether it is possible to support the required QoS. Here, the second packet data service node 150 may establish an RSVP path or the like capable of supporting the required QoS. If it is possible to support the requested QoS as a result of the check, the second packet data service node 150 approves the requested QoS and notifies the second communication terminal 170. That is, if the requested QoS is approved, the second communication terminal 170 considers that the RSVP reservation is successful. Or if the requested QoS is not approved, the second communication terminal 170 considers that the RSVP reservation has failed.

Finally, if QoS negotiation and RSVP reservation succeed, the second communication terminal 170 establishes QoS in step 237. Although not shown at this time, if at least one of QoS negotiation or RSVP reservation fails, the second communication terminal 170 may repeat steps 231 to 235. Thereafter, the second communication terminal 170 transmits a response message in step 239. Thereafter, the first communication terminal 110 and the second communication terminal 170 perform a call connection in step 241.

3 is a block diagram showing a schematic internal configuration of a communication terminal according to an embodiment of the present invention. In the embodiment of the present invention, it is assumed that the communication terminal is a mobile phone.

Referring to FIG. 3, the communication terminals 110 and 170 include a wireless communication unit 310, a key input unit 320, a control unit 330, a memory 340, an audio processing unit 350, and a display unit 360.

The wireless communication unit 310 performs a wireless communication function of the communication terminals 110 and 170. The wireless communication unit 310 includes an RF transmitter for upconverting and amplifying a frequency of a transmitted signal, and an RF receiver for low noise amplifying and downconverting a received signal. At this time, the wireless communication unit 310 performs a communication function required for call connection.

The key input unit 320 is composed of keys for inputting numeric and character information and function keys for setting various functions. The key input unit 320 may include a key for call connection, for example, call origination or call reception, through the wireless communication unit 310.

The controller 330 performs a function of controlling the overall operation of the communication terminal 330. The controller 330 includes a data processor including a transmitter for encoding and modulating a transmitted signal, a receiver for demodulating and decoding a received signal, and the like. In this case, the data processing unit may be configured of a modem and a codec. The codec includes a data codec for processing packet data and the like and an audio codec for processing audio signals such as voice.

According to an embodiment of the present invention, the controller 330 requests QoS setting when a call connection request is made. At this time, the controller 330 counts the number of QoS setting requests when the QoS setting request is made according to an embodiment of the present invention. If the QoS setting fails according to an embodiment of the present invention, the controller 330 re-requests the QoS setting. At this time, the control unit 330 may re-request the QoS setting at a predetermined number of repetition requests in response to one call connection request according to an embodiment of the present invention. That is, the controller 330 re-requests the QoS setting when the number of QoS setting requests is equal to or less than the set number of repetition requests according to an embodiment of the present invention. At this time, the controller 330 changes the number of QoS setting requests when re-requesting QoS settings according to an embodiment of the present invention. In addition, the control unit 330 controls to connect a call if the QoS setting is successful according to an embodiment of the present invention.

The memory 340 may be composed of a program memory and data memories. The program memory stores programs for controlling general operations of the communication terminals 110 and 170. In this case, the program memory may store programs for repeatedly requesting the QoS setting when the QoS setting fails according to an embodiment of the present invention. The data memory performs a function of storing data generated while executing programs. In addition, the memory 340 stores the number of re-request possible, that is, the number of repetition requests of the QoS setting set under the control of the control unit 330 according to the embodiment of the present invention.

The audio processor 350 reproduces a received audio signal output from the audio codec of the data processor through the speaker SPK or transmits a transmission audio signal generated from the microphone MIC to the audio codec of the data processor. .

The display unit 360 displays user data output from the controller 330. The display unit 360 may use an LCD. In this case, the display unit 360 may include an LCD controller, a memory capable of storing image data, and an LCD display device. In this case, when the LCD is implemented using a touch screen method, the LCD may operate as an input unit.

4 is a flowchart illustrating a call connection procedure of the communication terminal according to the first embodiment of the present invention. In the present embodiment, it is assumed that the communication terminal is the calling party.

Referring to FIG. 4, the call connection procedure of this embodiment starts from the controller 330 detecting a call origination request in step 411. In this case, the controller 330 counts the number of QoS setting requests X as 1 in step 413.

Next, the controller 330 requests QoS setting in step 415. The controller 330 performs QoS negotiation in step 417. That is, the controller 330 negotiates the resources and QoS of the codec. At this time, the controller 330 proposes a resource of a desired codec, for example, audio, video, control flow, and QoS. In operation 419, the controller 330 determines whether the QoS negotiation succeeds. That is, when receiving a resource and QoS of a desired codec within a set time interval, the controller 330 may determine that the QoS negotiation is successful. Alternatively, the controller 330 may determine that the QoS negotiation is successful when receiving the modified QoS from the resource of the codec or the modified QoS from the resource of the desired codec within a set time interval.

Subsequently, if it is determined that the QoS negotiation is successful in step 419, the controller 330 performs RSVP reservation in step 421. That is, the controller 330 requests reservation of the provided QoS. In operation 423, the controller 330 determines whether the RSVP reservation is successful.

In step 423, if the RSVP reservation is determined to be successful, the controller 330 sets QoS to the corresponding QoS in step 425. That is, if the reservation of the provided QoS is approved, the controller 330 may determine that the RSVP reservation is successful.

On the other hand, if it is determined in step 419 that the QoS negotiation has failed or in step 423 it is determined that the RSVP reservation has failed, the controller 330 changes the QoS setting request number X in step 427. That is, the controller 330 increases the number of QoS setting requests X by one. In operation 429, the controller 330 determines whether the QoS setting request number X is less than or equal to the set repetition request number N. At this time, if it is determined in step 429 that the QoS setting request number X is less than or equal to the set repetition request number N, the control unit 330 repeats steps 415 to 423. In addition, according to the determination result in step 423, the control unit 330 may repeat step 425 or repeat steps 427 and 429.

Finally, the controller 330 transmits an invitation message at step 431. After receiving the response message, the controller 330 detects this in step 433, connects the call in step 435, and ends the call connection procedure.

On the other hand, if it is determined in step 429 that the QoS setting request number X exceeds the set repetition request number N, the controller 330 ends the call connection procedure.

 5 is a flowchart illustrating a call connection procedure according to a second embodiment of the present invention. In the present embodiment, it is assumed that the communication terminal is the receiving side of the call.

Referring to FIG. 5, the call connection procedure of the present embodiment starts from the controller 330 detecting call reception in step 511. That is, when the reception of the invitation message is detected, the controller 330 detects this as a call reception. In this case, the controller 330 counts the number of QoS setting requests Y as 1 in step 513.

Next, the controller 330 requests QoS setting in step 515. The controller 330 performs QoS negotiation in step 517. That is, the controller 330 negotiates the resources and QoS of the codec. At this time, the controller 330 proposes resources of a desired codec, such as audio, video, control flow, and QoS. In step 519, the controller 330 determines whether the QoS negotiation succeeds. That is, when receiving a resource and QoS of a desired codec within a set time interval, the controller 330 may determine that the QoS negotiation is successful. Alternatively, when receiving the modified QoS from the resource of the codec or the modified QoS from the resource of the desired codec within the set time interval, the controller 330 may determine that the QoS negotiation is successful.

Subsequently, if it is determined that the QoS negotiation is successful in step 519, the controller 330 performs RSVP reservation in step 521. That is, the controller 330 requests reservation of the provided QoS. In operation 523, the controller 330 determines whether the RSVP reservation is successful.

In step 523, if the RSVP reservation is determined to be successful, the controller 330 sets QoS to the corresponding QoS in step 525. That is, if the reservation of the provided QoS is approved, the controller 330 may determine that the RSVP reservation is successful.

On the other hand, if it is determined in step 519 that the QoS negotiation has failed or in step 523 it is determined that the RSVP reservation has failed, the controller 330 changes the QoS setting request number Y in step 527. That is, the controller 330 increases the number of QoS setting requests Y by one. In step 429, the controller 330 determines whether the QoS setting request number Y is less than or equal to the set repetition request number N. In this case, if it is determined in step 429 that the QoS setting request number Y is less than or equal to the set repetition request number N, the control unit 330 repeats steps 515 to 523. In addition, according to the determination result in step 523, the controller 330 may repeat step 525 or may repeat steps 527 and 529.

Finally, the controller 330 transmits a response message in step 531. After that, the controller 330 connects the call in step 533 and ends the call connection procedure.

In contrast, if it is determined in step 529 that the number of QoS setting requests Y exceeds the set number of repetition requests N, the controller 330 ends the call connection procedure.

According to the present invention, even if the user of the communication terminal does not repeatedly generate a request for call connection, the communication terminal may repeatedly request the call connection. That is, after requesting a call connection, if the call connection fails, the communication terminal requests the call connection a set number of times. Thus, the user of the communication terminal does not have to generate a request for call connection again whenever the call connection fails. Accordingly, there is an advantage that the convenience of the communication terminal user is improved.

1 is a configuration diagram showing a schematic configuration of a communication system having a communication terminal according to an embodiment of the present invention;

2 is a flow chart illustrating a signal flow in the communication system of FIG. 1;

3 is a block diagram showing a schematic internal configuration of a communication terminal according to an embodiment of the present invention;

4 is a flowchart showing a call connection procedure according to the first embodiment of the present invention; and

5 is a flowchart illustrating a call connection procedure according to a second embodiment of the present invention.

Claims (9)

Requesting a quality of service (QoS) setting when a call connection request is made, If the QoS setting fails, changing the number of QoS setting requests; Re-requesting the QoS setting if the number of QoS setting requests is less than or equal to a set number of repetition requests; And if the QoS setting is successful, connecting the call. The method of claim 1, wherein the QoS setting re-request process includes: And performing at least one of QoS negotiation or Resorce ReserVation Protocol (RSVP) reservation. The method of claim 2, wherein the QoS setting request process comprises: And counting the number of QoS setting requests. The method of claim 2, wherein the QoS setting request process comprises: When a call originates, The call connection process, Sending an invitation message, Receiving a response message, connecting the call. The method of claim 2, wherein the QoS setting request process comprises: When an invitation message is received, The call connection process, Call connection method comprising the step of transmitting a response message. A wireless communication unit for connecting a call, A controller for requesting QoS setting upon request of the call connection, re-requesting the QoS setting if the QoS setting fails, and controlling to connect the call if the QoS setting is successful; And a memory for storing the number of repetition requests set to re-request the QoS setting under the control of the controller. The method of claim 6, wherein the control unit, When the QoS setting request, the number of the QoS setting request is counted, And when the QoS setting request number is less than or equal to the repetition request number, re-request the QoS setting and change the QoS setting request number. The method of claim 7, wherein And at least one of a QoS negotiation or an RSVP reservation fails, the QoS setting fails. The method of claim 7, wherein And a display unit for displaying a message for notifying failure of the QoS setting when the number of QoS setting requests exceeds the number of repetition requests under the control of the control unit.
KR1020070135254A 2007-12-21 2007-12-21 Access terminal and method for linking call thereof KR20090067559A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020070135254A KR20090067559A (en) 2007-12-21 2007-12-21 Access terminal and method for linking call thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020070135254A KR20090067559A (en) 2007-12-21 2007-12-21 Access terminal and method for linking call thereof

Publications (1)

Publication Number Publication Date
KR20090067559A true KR20090067559A (en) 2009-06-25

Family

ID=40995263

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020070135254A KR20090067559A (en) 2007-12-21 2007-12-21 Access terminal and method for linking call thereof

Country Status (1)

Country Link
KR (1) KR20090067559A (en)

Similar Documents

Publication Publication Date Title
RU2317647C2 (en) System and method for switching a call from packet commutation network to channel commutation network
US20060268838A1 (en) Authentication of an application layer media flow request for radio resources
KR101104500B1 (en) Method for signalling voice call of mobile terminal
EP2086185B1 (en) Method and apparatus for allocation of an uplink resource
US7349685B2 (en) Method and apparatus for generating service billing records for a wireless client
KR100915781B1 (en) Network-initiated service change from speech to multimedia
KR100770828B1 (en) Method for providing 1:1 call during conference call in mobile terminal
EP1825663B1 (en) Method, apparatus and computer program for providing services and services usage information for a wireless subscriber unit
KR100894361B1 (en) Method for processing call of mobile communication system
KR20090067559A (en) Access terminal and method for linking call thereof
JP4385025B2 (en) DTM communication apparatus and method
KR101069059B1 (en) method for verifying counsel using verification code
KR100462026B1 (en) Apparatus of proxy server and method of policy controling for mobile multimedia service
US20110221859A1 (en) Method and apparatus for video telephony in mobile communication system
KR100640325B1 (en) Method of communication using push to talk scheme in mobile communication terminal
CN113489853B (en) Voice communication method and device, terminal and storage medium
WO2012148424A1 (en) Method for setting up a communication connection
KR20080072304A (en) Method and terminal for sharing packet data protocol
KR100429289B1 (en) Method for waiting data call
KR20090049229A (en) Apparatus and method for call setup in ip multimedia subsystem
KR20090008897A (en) Method for registration of internet protocol multimedia subsystem and portable device using the same
KR20070111849A (en) Mobile communication terminal for transmitting and receiving multimedia packet data regardless of packet data call connection state
KR20050117856A (en) Point to point protocol server authentication method in a roaming service

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E601 Decision to refuse application