Method and apparatus for controlling rate of voice service in a mobile communication system supporting voice service via packet network

Description

METHOD AND APPARATUS FOR CONTROLLING RATE OF VOICE SERVICE IN A MOBILE COMMUNICATION SYSTEM SUPPORTING VOICE SERVICE VIA PACKET NETWORK

Technical Field

The present invention relates generally to a mobile communication system supporting a voice service via a packet network. More particularly, the present invention relates to a method and apparatus for controlling a rate of a particular voice service.

Background Art

Mobile communication systems are evolving into high-speed, high-quality wireless data packet communication systems for providing not only the established voiceoriented service, but also data and multimedia services. A Universal Mobile Telecommunication Service (UMTS) system, which is the 3^rd generation mobile communication system that is based on Global System for Mobile Communications (GSM) and General Packet Radio Services (GPRS) and uses Wideband Code Division Multiple Access (CDMA), provides a service in which users of mobile phones or computers can transmit packet-based text, digitized audio/video and multimedia data at a high rate of 2 Mbps or higher anywhere in the world. The UMTS system employs a packet-switched access concept that uses a packet protocol such as Internet Protocol (IP).

In this context, in the 3^rd Generation Partnership Project (3GPP) that is responsible for standardization for the UMTS communication system, there is a discussion on Voice over Internet Protocol (VoIP) communications that support voice packets using Internet protocol in supporting a voice service.

VoIP refers to a communication technique for transmitting voice frames generated in a voice codec after converting the voice frames into IP/User Datagram Protocol (UDP)/Real time Transport Protocol (RTP) packets. With the use of VoIP, it is possible to provide voice service via the packet network.

FIG. 1 is a diagram illustrating a configuration of a conventional mobile communication system supporting VoIP.

Referring to FIG. 1, a user equipment (UE) 100 includes a codec 105 for converting a voice signal into a voice frame, an DP/UDP/RTP protocol layer 104 for making an IP/ UDP/RTP packet with the voice frame from the codec 105, a Packet Data Convergence Protocol (PDCP) layer 103 for compressing a header of the EP/UDP/RTP packet, a

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

Radio Link Control (RLC) layer 102 for converting the IP/UDP/RTP packet into an appropriate format to transmit it over a wireless channel, and a Medium Access Control (MAC)/Physical Layer (PHY) layer 101 for transmitting the packet data over the wireless channel.

The voice packet data transmitted from the UE 100 is delivered to a radio network controller (RNC) 120 via a Node B 110 over a wireless channel. The RNC 120, including a MAC/PHY layer 121, an RLC layer 122 and a PDCP layer 123, like the UE 100, converts the voice frame on the wireless channel into its original IP/UDP/RTP packet, and transmits the IP/UDP/RTP packet to a core network (CN) 130. The IP/ UDP/RTP packet delivered to the CN 130 is transmitted to a receiving UE (not shown) via an IP network 140. The receiving UE, having the same hierarchical structure as that of the transmitting UE 100, restores the transmitted voice data to its original voice signal in the opposite order.

3GPP provides voice service using a voice codec called an Adaptive Multi Rate (AMR) codec, and the AMR codec is characterized by its variable rate, so it can adjust the rate according to conditions of the wireless channel.

FIG. 2 is a diagram illustrating a conventional AMR rate control process.

In a downlink (DL) rate control process of FIG. 2, both ends of a VoIP communication exchange VoIP packets 265 with each other. The VoIP packet 265 is composed of an IP/UDP/RTP header 240, an AMR payload specific header 257 and voice data 260. The AMR payload specific header 257 is composed of a Change Mode Request (CMR) field 245, Frame Type (FT) field 250 and an OTHER field 255.

The voice data 260 can have various sizes according to an AMR codec mode, and the FT field 250 is filled with infonnation on the codec mode applied to the voice data. Therefore, a VoIP packet receiving party can ascertain a size and format of the voice data 260 by parsing the infonnation in the FT field 250. Table 1 below shows exemplary sizes of voice data according to various codec modes used in the AMR.

Table 1

<td> Frame Type</td><td> AMR codec mode</td><td> Voice data size (bits)</td>

<td> 0</td><td> AMR 4.75 kbit/s</td><td> 112</td>

<td> 1</td><td> AMR 5.15 kbit/s</td><td> 120</td>

<td> 2</td><td> AMR 5.90 kbit/s</td><td> 128</td>

<td> 3</td><td> AMR 6.70 kbit/s (PDC-EFR)</td><td> 144</td>

<td> 4</td><td> AMR 7.40 kbit/s(TDMA-EFR)</td><td> 160</td>

<td> 5</td><td> AMR 7.95 kbit/s</td><td> 176</td>

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

<td> 6</td><td> AMR 10.2 kbit/s</td><td> 216</td>

<td> 7</td><td> AMR 12.2 kbit/s (GMS-EFR)</td><td> 256</td>

<td> 8</td><td> AMR SID</td><td> 56</td>

The CMR field 245 is filled with information on a codec mode required for the other party. For example, if the other party desires to transmit voice data at 12.2 kbps, the CMR field 245 is filled with 7, which is an FT value associated with 12.2 kbps.

The OTHER field 255 is filled with such information indicating whether there is an error in the voice data. This field is not related to the gist of the exemplary embodiment present invention, so a description thereof will be omitted.

A description will now be made of a downlink rate control process performed in a UMTS network.

A VoIP communication is being performed between a UMTS terminal 205 and an IP entity 210 via an RNC 207. The IP entity 210 is a device for generating downlink VoIP packets, and can include, for example, a gateway or a VoIP terminal. In step 215, the IP entity 210 transmits a VoIP packet having a rate of y kbps to the UMTS terminal 205. In this case, an FT field of the VoIP packet is filled with a value x associated with the rate. In step 220, the UMTS terminal 205 desires to change the rate of the downlink VoIP packet. Exemplary reasons for the UMTS terminal 205 to change the rate of the downlink VoIP packet include, if there is a need to decrease the rate due to the deterioration of a downlink wireless channel, or to increase the rate due to the improvement of the downlink wireless channel.

In step 225, the UMTS terminal 205 inserts an FT value associated with a desired rate into a CMR field of an uplink (UL) VoIP packet before transmission. In step 230, upon receipt of the uplink VoIP packet, the IP entity 210 changes a rate of a downlink VoIP packet to x-1 according to a CMR field value. Thereafter, an FT of the downlink VoIP packet transmitted to the UMTS terminal 205 in step 235 becomes x-1. Disclosure of Invention

Technical Problem

Because the rate control in the conventional VoIP communication is performed on an end-to-end basis, the entity located in the middle of the transmission path cannot control the rate. However, in the UMTS network, there is a case where an RNC should be able to control an AMR rate so as to be closely associated with radio resources. Fot example, there is a possible case where the RNC should decrease a downlink/uplink AMR rate in order to limit to a specific level a ratio of VoIP traffic to all traffic of a particular cell. However, in conventional VoIP communications, the RNC cannot

2006276360 18 Aug 2009 control the AMR rate.

Technical Solution

Exemplary embodiments of the present invention address at least the above problems and/or disadvantages and provide at least the advantages described below.

Accordingly, an aspect of the present invention is to provide a method and apparatus for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network.

The present invention provides a method and apparatus in which a network entity, such as an RNC, controls a rate of a voice service in a mobile communication io system supporting the voice service via a network element.

Exemplary embodiments of the present invention provide a method and apparatus in which an RNC control an uplink AMR rate of a terminal by transmitting an Uplink AMR Rate Control message to the terminal.

Exemplary embodiments of the present invention provides a method and is apparatus in which an RNC transmits a Downlink AMR Rate Control message to a terminal so that the terminal may appropriately set a CMR field value of an uplink VoIP packet.

According to one aspect of the present invention, there is provided a method for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network, the method comprising the steps of:

receiving by a terminal a control message from a radio network controller (RNC);

determining type of the control message;

if the type is a downlink control message including a downlink rate, setting a 25 Change Mode Request (CMR) field of an uplink Voice over Internet Protocol (VoIP) packet according to the downlink rate, and transmitting the uplink VoIP packet from the terminal to the RNC.

According to further another aspect of the present invention, there is provided a method for controlling a rate of a voice service in a mobile communication system

0 supporting the voice service via a packet network, the method comprising the steps of:

determining a new at least one of a downlink and uplink rate to control information in a Change Mode Request (CMR) field or a frame type (FT) field of at least one of a downlink and uplink Voice over Internet Protocol (VoIP) packet for the voice service;

5 generating a downlink control message indicating the determined downlink to change the Change Mode Request (CMR) field of the uplink packet; and transmitting the generated control message to a terminal.

N:\Melbouma1Cases\Patenl\76OOO-76999\P76153.AU\SpacistP76153.AU Specification 2009-6-16 doc 24/06/09

2006276360 18 Aug 2009

According to yet another aspect of the present invention, there is provided an apparatus for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network, the apparatus comprising:

a control message receiver for detecting Desired Downlink (DL) Frame Type 5 information or Desired Uplink (UL) Frame Type information from a control message indicating control of at least one of a downlink and uplink rate received from a radio network controller (RNC);

a Change Mode Request (CMR) field controller for determining a CMR field value indicating a downlink rate according to the Desired DL Frame Type information;

io a rate controller for determining an uplink rate according to the Desired UL

Frame Type information;

a header inserter for inserting the CMR field value received from the CMR field controller into a header of an uplink voice packet;

a voice codec for converting a voice signal into voice data according to the is determined uplink rate, and converting voice data included in a downlink packet into a voice signal;

a transceiver for transmitting an uplink voice packet including the header and the voice data to the RNC, receiving a downlink voice packet from the RNC, and providing the received downlink voice packet to the voice codec,

0 According to still another aspect of the present invention, there is provided an apparatus for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network, the apparatus comprising:

a rate decider for determining a new downlink rate to control information in a Change Mode Request (CMR) field of a downlink Voice over Internet Protocol (VoIP) packet for the voice service;

a control message generator for generating a downlink control message indicating the downlink rate provided from the rate decider to change the CMR field of the uplink packet; and a transceiver for transmitting the generated downlink control message to a

0 terminal.

According to still another aspect of the present invention, there is provided a computer-readable recording medium having recorded thereon a program for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network, comprising:

a first code segment, for causing a computing device to receive a control message from a radio network controller (RNC);

a second code segment, for causing a computing device to detect a downlink rate according to the control message, if the control message indicates control of a downlink rate;

839851J (GHMatters) 17/08/09

2006276360 18 Aug 2009

- 6 a third code segment, for causing a computing device to set a Change Mode Request (CMR) field of an uplink Voice over Internet Protocol (VoIP) packet according to the downlink rate, and to transmit the uplink VoIP packet from the terminal to the RNC;

a fourth code segment, for causing a computing device to detect an uplink rate according to the control message, if the received control message indicates control of an uplink rate; and a fifth code segment, for causing a computing device to generate an uplink VoIP packet including uplink voice data generated according to the determined uplink rate io and frame type (FT) infonnation indicating the determined uplink rate, and to transmit the uplink VoIP packet from the terminal to the RNC.

According to still another aspect of the present invention, there is provided a computer-readable recording medium having recorded thereon a program for controlling a rate of a voice service in a mobile communication system supporting the voice service via a packet network, comprising:

a first code segment, for causing a computing device to determine a new at least one of a downlink and uplink rate to control information in a Change Mode Request (CMR) field or a frame type (FT) field of at least one of a downlink and uplink Voice over Internet Protocol (VoIP) packet for the voice service;

0 a second code segment, for causing a computing device to generate a control message indicating the determined at least one of a downlink and uplink rate;

a third code segment, for causing a computing device to transmit the generated control message to a terminal.

Other aspects, advantages, and salient features of the invention will become 25 apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.

Advantageous Effects

As can be understood from the foregoing description, exemplary embodiments o of the present invention allow the network to control a rate of a VoIP packet, thereby efficiently managing the radio resources.

Brief Description of the Drawings

The above and other aspects, features, and advantages of certain embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a diagram illustrating a configuration of a conventional mobile communication system supporting VoIP;

FIG. 2 is a diagram illustrating a conventional AMR rate control process;

839851,1 (GHMatters) 17/08/09

- 6a 2006276360 18 Aug 2009

FIG. 3 is a diagram illustrating an AMR rate control operation according to a first exemplary embodiment of the present invention;

FIG. 4 is a flowchart illustrating an operation of a terminal according to the first exemplary embodiment of the present invention;

FIG. 5 is a diagram illustrating an AMR rate control operation according to a second exemplary embodiment of the present invention;

FIG. 6 is a flowchart illustrating an operation of a terminal according to the second exemplary embodiment of the present invention;

FIG. 7 is a diagram illustrating an AMR rate control operation according to a io third embodiment of the present invention;

839851J (GHMatters) 17/08/09

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

FIG. 8 is a flowchart illustrating an operation of an RNC according to the third embodiment of the present invention;

FIG. 9 is a diagram illustrating a structure of a terminal according to the first and second exemplary embodiments of the present invention;

FIG. 10 is a diagram illustrating a structure of an RNC according to the first and second exemplary embodiments of the present invention; and

FIG. 11 is a diagram illustrating a structure of an RNC according to the third exemplary embodiment of the present invention.

Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features, and structures.

Best Mode for Carrying Out the Invention

The matters defined in the description such as a detailed construction and elements are provided to assist in a comprehensive understanding of the embodiments of the invention and are merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

In a mobile communication system providing a voice service via a packet network according to exemplary embodiments of the present invention, a network entity, such as an RNC, controls a rate of the voice service.

Exemplary embodiments of the present invention propose a scheme in which an RNC transmits an Uplink AMR Rate Control message to a terminal to control an uplink AMR rate of the terminal. In addition, the present invention proposes a scheme in which an RNC transmits a Downlink AMR Rate Control message to a terminal so that the terminal may appropriately set a CMR field value of an uplink VoIP packet.

Although exemplary embodiments of the present invention will be described with reference to an RNC in a 3GPP UMTS network, it can also be applied to an entity located in the middle of a transmission path in almost every VoIP communication network such as 3GPP Long Term Evolution (LTE) network. That is, a particular entity of a network that manages radio transmission resources can use a control message proposed in the exemplary embodiments of the present invention to control an uplink/downlink AMR rate of a particular terminal.

First Embodiment

FIG. 3 is a diagram illustrating an AMR rate control operation according to a first

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 exemplary embodiment of the present invention.

Referring to FIG. 3, in step 312, a VoIP communication is being performed between a UMTS terminal 305 and an IP entity 310. It is assumed that a downlink frame type (FT) is 5, a downlink AMR rate is 7.95 kbps, an uplink frame type is 4, and an uplink AMR rate is 7.40 kbps. Therefore, a frame type of a downlink VoIP packet transmitted from the IP entity 310 to the UMTS terminal 305 in step 315 is 5.

Thereafter, in step 320, an RNC 307 desires to change the downlink AMR rate to 5.90 kbps at a particular time. For example, the RNC 307 can decrease an AMR rate of the terminal, if it intends to accommodate traffic of a new terminal in the cell, but has insufficient downlink transmission resources. Because the downlink AMR rate is set by the IP entity 310 and direct communication is not possible between the IP entity 310 and the RNC 307, the RNC 307 controls the AMR rate of the IP entity 310 via the UMTS terminal 305 and is controllable by RNC 307 itself. More specifically, in step 325, the RNC 307 sets a desired FT in a Downlink AMR Rate Control message to 2 associated with 5.90 kbps, and then transmits the Downlink AMR Rate Control message with the desired FT=2 to the UMTS terminal 305.

In step 330, upon receipt of the Downlink AMR Rate Control message, the UMTS terminal 305 sets a CMR field of an uplink VoIP packet according to the desired FT information in the received message. As a result, the CMR field of the uplink VoIP packet transmitted to the IP entity 310 in step 335 is set to '2'

In step 340, if the VoIP packet arrives at the IP entity 310, the IP entity 310 sets a frame type of a downlink VoIP packet according to the CMR field information in the received VoIP packet. That is, by setting the frame type of the downlink VoIP packet transmitted in step 345 to '2' the IP entity 310 sets the downlink AMR rate to 5.90 kbps.

Thereafter, in step 350, the RNC 307 desires to change the uplink AMR rate from 7.40 kbps to 10.2 kbps at a particular time. For example, the RNC 307 can increase the uplink AMR rate, if it has sufficient available uplink transmission resources and thus desires to allow more uplink transmission resources for the terminal.

In step 355, the RNC 307 sets a desired FT in an Uplink AMR Rate Control message to '6' associated with 10.2 kbps, and transmits the Uplink AMR Rate Control message with desired FT=6 to the UMTS terminal 305.

In step 360, upon receipt of the Uplink AMR Rate Control message, the UMTS terminal 305 sets a frame type of an uplink VoIP packet according to the desired FT information in the received message.

That is, the frame type of the uplink VoIP packet transmitted to the IP entity 310 in step 365 is set to '6'

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

FIG. 4 is a flowchart illustrating an operation of a tenninal according to the first exemplary embodiment of the present invention.

In an operation of FIG. 4, a tenninal receives a Downlink AMR Rate Control message and an Uplink AMR Rate Control message.

The tenninal receives a control message from an RNC in step 405, and determines a type of the control message in step 410. If the control message is the Uplink AMR Rate Control message, the tenninal proceeds to step 430. If the control message is the Downlink AMR Rate Control message, the terminal proceeds to step 420. If the control message is another message, the tenninal proceeds to step 415.

In step 415, the terminal performs a rate control operation according to the information in the control message. This step is equal to its corresponding step in the conventional method, so a detailed description thereof will be omitted.

In step 420, the tenninal, if the received message is the Downlink AMR Rate Control message, forwards Desired DL Frame Type information included in the Downlink AMR Rate Control message to an AMR header inserter. In step 425, the AMR header inserter sets a CMR field of an uplink VoIP packet generated later according to the Desired DL Frame Type information prior to transmission.

In step 430, the tenninal, if the received message is the Uplink AMR Rate Control message, forwards Desired UL Frame Type information included in the Uplink AMR Rate Control message to an AMR codec. In step 435, the AMR codec sets a codec rate of an uplink VoIP packet generated later according to the Desired UL Frame Type before transmission.

In the first embodiment of the present invention, the RNC should be aware of an AMR codec rate used at a corresponding time and an available AMR codec rate. Therefore, in order for the RNC to recognize the AMR codec rate information, signaling should be preferentially performed between a Serving GPRS Support Node (SGSN) and the RNC.

Second Embodiment

A second embodiment of the present invention proposes a scheme in which an RNC controls a downlink/uplink AMR codec rate without information on an AMR codec rate.

In summary of the second embodiment, an RNC simply provides the information indicating the fact that there is a need to change the current codec rate to a higher codec rate or a lower codec rate, instead of inserting desired FT information into a Downlink AMR Rate Control message and an Uplink AMR Rate Control message. Upon receipt of the Uplink AMR Rate Control message, a terminal adjusts a codec rate of an uplink VoIP packet to a codec rate higher or lower than the current codec rate.

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

Upon receipt of the Downlink AMR Rate Control message, the tenninal inserts a value associated with a codec rate higher or lower than the current codec rate into a CMR field of an uplink VoIP packet, under the control of the RNC.

FIG. 5 is a diagram illustrating an AMR rate control operation according to a second exemplary embodiment of the present invention.

It is assumed that VoIP communication is being performed between a UMTS tenninal 505 and an IP packet 510, a downlink frame type is 5, a downlink AMR rate is 7.95 kbps, an uplink frame type is 4, and an uplink AMR rate is 7.40 kbps.

Therefore, a frame type of a downlink VoIP packet transmitted from the IP entity 510 to the UMTS terminal 505 in step 515 is 5.

In step 520, an RNC 507 desires to change the downlink AMR rate to a lower rate at a particular time. For example, the RNC 507 can change an AMR rate of a terminal located in a cell, if it intends to accommodate traffic of a new tenninal in the cell, but has insufficient downlink transmission resources in the cell.

Because the downlink AMR rate is conventionally set by the IP entity 510 and direct communication is not possible between the IP entity 510 and the RNC 507, the RNC 507 controls the AMR rate of the IP entity 510 via the UMTS tenninal 505 that is controllable by RNC 507 itself. More specifically, in step 525, the RNC 507 inserts Lower DL codec rate information in a Downlink AMR Rate Control message, and sends the Downlink AMR Rate Control message to the UMTS tenninal 505. Here the Lower DL codec rate information indicates a decrease in a downlink AMR codec rate. However, if the RNC 507 desires to increase the downlink AMR rate, it inserts Higher DL codec rate information in the Downlink AMR Rate Control message. In this case, Higher DL codec rate information indicates an increase in a downlink AMR codec rate.

In step 530, upon receipt of the Downlink AMR Rate Control message, the UMTS terminal 505 sets a CMR field of an uplink VoIP packet according to the information included in the received message. That is, if Lower DL codec rate is included in the Downlink AMR Rate Control message, the UMTS tenninal 505 sets the CMR field to a value associated with a codec rate lower than the codec rate of the previous downlink VoIP packet. Otherwise, if Higher DL codec rate is included in the Downlink AMR Rate Control message, the UMTS terminal 505 sets the CMR field to a value associated with a codec rate higher than the codec rate of the previous downlink VoIP packet.

In this embodiment, because Lower DL codec rate is included in the Downlink AMR Rate Control message and the FT of the downlink VoIP packet received from the IP entity 510 in step 515 is 5, a CMR field of an uplink VoIP packet transmitted in step

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009

535 is set to 4. In step 540, if the uplink VoIP packet arrives at the IP entity 510, the IP entity 510 sets a frame type of a downlink VoIP packet according to the CMR field of the uplink VoIP packet. That is, by setting the frame type of the VoIP packet transmitted in step 545 to '4' the IP entity 510 sets the downlink AMR rate to 7.40 kbps.

Thereafter, in step 550, the RNC 507 desires to increase the uplink AMR rate at a particular time. For example, the RNC 507 can increase the uplink AMR rate, if it has sufficient available uplink transmission resources and thus desires to allow more uplink transmission resources for the UMTS terminal 505.

In step 555, the RNC 507 inserts Higher UL codec rate information in an Uplink AMR Rate Control message, and transmits the Uplink AMR Rate Control message to the UMTS terminal 505. The Higher UL codec rate information indicates an increase in an uplink AMR codec rate.

In step 560, upon receipt of the Uplink AMR Rate Control message, the UMTS terminal 505 sets a codec rate of an uplink VoIP packet to a codec rate higher than the current codec rate because the Higher UL codec rate information is included in the received message. In addition, the UMTS terminal 505 sets a frame type of the uplink VoIP packet according to the adjusted value. For example, when the frame type of the previous uplink VoIP packet is 5, the frame type of the uplink VoIP packet transmitted to the IP entity 510 in step 565 is set to '6'

FIG. 6 is a flowchart illustrating an operation of a terminal according to the second exemplary embodiment of the present invention.

The terminal receives a control message from an RNC in step 605, and determines a type of the control message in step 610. If the control message is an Uplink AMR Rate Control message, the terminal proceeds to step 635. If the control message is a Downlink AMR Rate Control message, the terminal proceeds to step 620. If the control message is another message, the terminal proceeds to step 615.

In step 615, the terminal performs a rate control operation according to the information in the control message. This step is equal to its corresponding step in the conventional method, so a detailed description thereof will be omitted.

In step 620, the terminal examines Desired DL Frame Type information included in the Downlink AMR Rate Control message. If the Desired DL Frame Type information is Higher DL codec rate information, the terminal proceeds to step 625. If the Desired DL Frame Type information is Lower DL codec rate information, the terminal proceeds to step 630.

In step 625, the terminal selects an AMR rate that is higher than the AMR rate of the previous downlink VoIP packet received prior to the Downlink AMR Rate Control

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 message, and inserts the selected MAR rate into a CMR field of an uplink VoIP packet. In step 630, the terminal selects an AMR rate that is lower than the AMR rate of the previous downlink VoIP packet, and inserts the selected AMR rate into the

CMR field of the uplink VoIP packet.

In step 635, the terminal examines Desired UL Frame Type information included in the Uplink AMR Rate Control message. If the Desired UL Frame Type information is Higher UL codec rate information, the terminal proceeds to step 640. If the Desired UL Frame Type information is Lower UL codec rate information thereby indicating a decrease in an uplink AMR codec rate, the terminal proceeds to step 645. In step 640, the terminal adjusts a rate of an uplink VoIP packet so as to have an AMR rate that is higher than the AMR rate of the previous uplink VoIP packet. In step 645, the terminal adjusts the rate of the uplink VoIP packet to an AMR rate that is lower than the AMR rate of the previous uplink VoIP packet.

Although the Downlink AMR Rate Control message and the Uplink AMR Rate Control message are separately used in the first and second exemplary embodiments of the present invention, one of the two messages may perform both of the two functions. That is, it is possible to include both downlink/uplink AMR rate change information in one control message, or control both downlink/uplink AMR rates based on the rate change information included in the one control message.

In addition, the RNC includes the current state information of the terminal, rather than the rate change information, in the control message before transmission, so that the terminal receiving the control message can recognize its uplink transmission environment and perform rate control according thereto.

Third Embodiment

A third embodiment of the present invention proposes a scheme in which an RNC personally adjusts a CMR field of a VoIP packet without using an AMR Rate Control message.

FIG. 7 is a diagram illustrating an AMR rate control operation according to the third embodiment of the present invention.

It is assumed that VoIP communication is being performed between a UMTS terminal 705 and an IP entity 710 in step 712. A downlink frame type is 5, a downlink AMR rate is 7.95 kbps, an uplink frame type is 4, and an uplink AMR rate is 7.40 kbps.

Therefore, a frame type of a downlink VoIP packet transmitted from the IP entity 710 to the UMTS terminal 705 in step 715 is 5.

In step 720, an RNC 707 desires to change the downlink AMR rate to a lower rate

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 at a particular time. For example, the RNC 707 can change an AMR rate of the terminal 705, if it intends to accommodate traffic of a new terminal, but has insufficient downlink transmission resources to do so.

To change a downlink rate, the RNC 707 changes a CMR field of an uplink VoIP packet received from the UMTS terminal 705 to its desired value.

For example, upon arrival of an uplink VoIP packet with CMR=5 in step 725, the

RNC 707 changes the CMR field of the uplink VoIP packet to a value associated with the desired rate in step 730, and transmits the uplink VoIP packet to the IP entity 710 in step 735. In the embodiment of FIG. 7, the value in the CMR field is changed from 5 to 4. In this case, the RNC 707 newly calculates a UDP header checksum value of the uplink VoIP packet taking the new CMR field value into account, and updates the uplink VoIP packet using the UDP header checksum value.

In step 740, the IP entity 710 changes a frame type of the downlink VoIP packet according to the CMR field value of the uplink VoIP packet. In step 745, the IP entity 710 sets the frame type of the downlink VoIP packet to 4 and transmits the downlink VoIP packet with FT=4 to the UMTS terminal 705.

An uplink rate change operation is equal to the downlink rate change operation, so a detailed description thereof will be omitted.

FIG. 8 is a flowchart illustrating an operation of an RNC according to the third embodiment of the present invention.

If there is a need to change an AMR rate in step 805, an RNC proceeds to step 810. ι In step 810, the RNC determines whether it needs to change an uplink AMR rate or a downlink AMR rate. If there is a need to change an uplink AMR rate, the RNC proceeds to step 815. If there is a need to change a downlink AMR rate, the RNC proceeds to step 820.

I In step 815, to change the uplink AMR rate, the RNC changes a CMR field of a downlink VoIP packet to be transmitted to a terminal to value associated with the desired rate.

In step 820, to change the downlink AMR rate, the RNC changes a CMR field of an uplink VoIP packet received from a terminal to value associated with the desired rate.

In step 825, the RNC recalculates a UDP checksum of the downlink/uplink VoIP packet whose CMR field has changed. The UDP header has a 2-byte UDP checksum field, and this field is filled with a checksum value for a UDP header, an AMR header and an AMR data part. Therefore, if the CMR field is changed, the checksum value should be recalculated.

In step 830, the RNC sends a downlink/uplink VoIP packet with the changed CMR field and the newly calculated UDP checksum value to the corresponding destination

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 entity.

FIG. 9 is a diagram illustrating a structure of a terminal according to the first and second exemplary embodiments of the present invention.

The terminal includes an AMR codec 905, an AMR header inserter 915, a user data processor 925, an AMR rate controller 910, a CMR field controller 920, a control message receiver 930, and a transceiver 935.

The AMR codec 905 converts a voice signal into AMR data, or converts AMR data into a voice signal. The AMR header inserter 915 inserts an AMR header such as CMR and FT into the AMR data. The user data processor 925 is a device for appropriately processing an AMR packet so as to transmit it over a wireless channel, and is composed of a UDP/IP protocol entity and PDCP, RLC, MAC entities.

The transceiver 935 transmits uplink data and receives downlink data over a wireless channel.

The control message receiver 930 receives a control message, and takes an appropriate action according to control information in the control message. Upon receipt of a Downlink AMR Rate Control message, the control message receiver 930 delivers the control information in the control message to the CMR field controller 920. Upon receipt of an Uplink AMR Rate Control message, the control message receiver 930 delivers the control information in the control message to the AMR rate controller 910.

Operations of the CMR field controller 920 and the AMR rate controller 910 are slightly different in the first and second embodiments. A description will first be made of an operation of each device in the first embodiment.

I Upon receipt of Desired DL Frame Type information, the CMR field controller 920 delivers the received information to the AMR header inserter 915, and the AMR header inserter 915 sets a CMR field of an uplink VoIP packet to the value delivered by the CMR field controller 920.

Upon receipt of Desired UL Frame Type information, the AMR rate controller 910 delivers the received information to the AMR codec 905. The AMR codec 905 adjusts an uplink AMR rate according to the provided information, and converts a voice signal into AMR data according to the adjusted uplink AMR rate.

A description will now be made of an operation of the CMR field controller 920 in the second embodiment.

If Higher DL codec rate information is included in the Desired DL Frame Type information, the CMR field controller 920 determines an appropriate value to be inserted in a CMR field. In this case, the following details can be taken into consideration by way of example.

, l.A new CMR field value should be higher than the AMR rate of the current

I ί

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 downlink VoIP packet.

2. The new CMR field value should be one of the AMR rates supported in the other party s IP entity.

3. The CMR field controller selects the value nearest to the AMR rate of the current downlink VoIP packet among the CMR values satisfying the above two conditions.

If Lower DL codec rate information is included in the Desired DL Frame Type information, the CMR field controller 920 determines an appropriate value to be inserted in a CMR field. In this case, the following details can be taken into consideration by way of example.

1. A new CMR field value should be lower than the AMR rate of the current downlink VoIP packet.

2. The new CMR field value should be one of the AMR rates supported in the other party s IP entity.

3. The CMR field controller selects the value nearest to the AMR rate of the current downlink VoIP packet among the CMR values satisfying the above two conditions.

A description will now be made of an operation of the AMR rate controller 910 in the second embodiment.

If Higher UL codec rate information is included in the Desired UL Frame Type information, the AMR rate controller 910 determines a new uplink AMR rate. In this case, the following details can be taken into consideration by way of example.

1. A new uplink AMR rate should be higher than the current uplink AMR rate.

2. A new uplink AMR rate should be one of the AMR rates supported by the terminal.

3. The AMR rate controller should select the value nearest to the current uplink AMR rate among the AMR rates satisfying the above two conditions.

If Lower UL codec rate information is included in the Desired UL Frame Type information, the AMR rate controller 910 determines a new uplink AMR rate. In this case, the following details can be taken into consideration by way of example.

1. A new uplink AMR rate should be lower than the current uplink AMR rate.

2. A new uplink AMR rate should be one of the AMR rates supported by the terminal.

3. The AMR rate controller should select the value nearest to the current uplink AMR rate among the AMR rates satisfying the above two conditions.

FIG. 10 is a diagram illustrating a structure of an RNC according to the first and

WO 2007/015596

PCT/KR2006/002584

2006276360 18 Aug 2009 second exemplary embodiments of the present invention.

The RNC includes a user data processor 1005, an AMR rate decider 1010, a radio resource manager 1015, a control message generator 1020, and a transceiver 1025.

The user data processor 1005 is a device for processing downlink/uplink user data, and is comprised of PDCP, RLC and MAC entities.

The transceiver 1025 is a device for transmitting/receiving downlink/uplink data. The control message generator 1020 is a device for generating a control message.

Upon receipt of a request for change in the AMR rate from the AMR rate decider 1010, the control message generator 1020 generates a Downlink AMR Rate Control message or an Uplink AMR Rate Control message.

The radio resource manager 1015 is a device for managing radio resources of the cells managed by the RNC, and performs, for example, a Call Admission Control operation. If there is a need to withdraw the radio resources of the cell or there is a need to allocate more radio resources, the radio resource manger 1015 notifies the need to the AMR rate decider 1010.

Upon receipt of a withdraw request for radio resources of a particular cell from the radio resource manager 1015, the AMR rate decider 1010 decreases an AMR rate of a terminal located in the cell. Upon receipt of a notification indicating the possibility of allocating more radio resources in a particular cell from the radio resource manager 1015, the AMR rate decider 1010 increases an AMR rate of a terminal located in the cell. In the first embodiment, the AMR rate decider 1010 determines downlink desired FT information and uplink desired FT information to be inserted into a Downlink AMR Rate Control message and an Uplink AMR Rate Control message, and delivers the determined information to the control message generator 1020.

In the second embodiment, the AMR rate decider 1010 determines Lower DL codec rate information and Higher DL codec rate information, or Lower UL codec rate information and Higher UL codec rate information to be inserted into a Downlink AMR Rate Control message and Uplink AMR Rate Control message, and delivers the detennined information to the control message generator 1020.

FIG. 11 is a diagram illustrating a structure of an RNC according to the third exemplary embodiment of the present invention.

The RNC includes a CMR field adjuster 1105, an uplink UDP checksum calculator 1102, a downlink UDP checksum calculator 1110, a user data processor 1125, a transceiver 1130, an AMR rate decider 1115, and a radio resource manager 1120.

The CMR field adjuster 1105, under the control of the AMR rate decider 1115, resets CMR fields of an uplink VoIP packet and a downlink VoIP packet to a new value.

- 17 2006276360 18 Aug 2009

The radio resource manager 1120 is a device for managing radio resources of the cells managed by the RNC, and performs, for example, a Call Admission Control operation. If there is a need to withdraw the radio resources of the cell or there is a need to allocate more radio resources, the radio resource manger 1120 notifies the need to the

AMR rate decider 1115.

The downlink UDP checksum calculator 1110 recalculates a UDP checksum value of a downlink VoIP packet delivered from the CMR field adjuster 1105. The downlink VoIP packet processed in the downlink UDP checksum calculator 1110 is transmitted to the terminal via the user data processor 1125. The user data processor io 1125 is a device for processing downlink/uplink user data, and is composed of PDCP, RLC and MAC entities. The transceiver 1130 transmits/receives downlink/uplink data.

The uplink UDP checksum calculator 1102 recalculates a UDP checksum value of the uplink VoIP packet delivered from the CMR field adjuster 1105. The uplink VoIP packet processed in the uplink UDP checksum calculator 1102 is delivered to the is other party s IP entity via, for example, an SGSN.

The downlink VoIP packet is directly input to the CMR field adjuster 1105 without passing through the uplink UDP checksum calculator 1102, and the uplink VoIP packet is directly input to the CMR field adjuster 1105 without passing through the downlink UDP checksum calculator 1110.

While the invention has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word “comprise” or variations such as “comprises” or “comprising” is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

It is to be understood that, if any prior art publication is referred to herein, such

0 reference does not constitute an admission that the publication forms a part of the common general knowledge in the art, in Australia or any other country.

839851_1 (GHMatters) 17/08/09

- 18 2006276360 18 Aug 2009