JP4955651B2 - Multiple code support method in wireless mobile communication system - Google Patents

Description

  The present invention relates to a method for supporting code types, and more particularly, to a method for supporting multiple code types in a wireless mobile communication system.

  In a broadband wireless access system, an Orthogonal Frequency Division Multiple Access (OFDMA) scheme is used for data transfer. When the orthogonal frequency division multiple access scheme is used, the frame structure is defined as follows. First, the downlink frame displays a preamble at a start position of a frame that can be used for synchronization between a terminal (MS) and a base station (BS) and equalization in a physical layer. The frame includes, following the preamble, a downlink map (DL-MAP) message and an uplink map (UL-MAP) message that define the location and usage of the allocated burst.

  More specifically, the DL-MAP message defines the usage of each burst allocated in the downlink section of the frame in the burst mode physical layer. The UL-MAP message similarly defines the usage of bursts allocated in the uplink section of the frame. An information element (Information Element: hereinafter referred to as “IE”) included in the DL-MAP is a downlink interval usage code (hereinafter referred to as “DIUC”) in the downlink traffic interval of the user group. ), CID (Connection ID) and burst position information (for example, subchannel offset, symbol offset, number of subchannels, number of symbols).

  The usage of the information elements constituting the UL-MAP message is determined by an uplink interval usage code (hereinafter referred to as 'UIUC') for each CID (Connection ID). And the applicable position of an uplink section is prescribed | regulated by duration (duration). Here, the usage of each section is determined by the UIUC value used in UL-MAP. The start point of each section starts from a point that is set at the duration specified by the UL-MAP IE from the previous IE start point.

  In order to enter the network (Network Entry) or to re-enter the network due to handover or other reasons (Network Re-Entry), the mobile terminal is referred to as a “downlink channel descriptor (hereinafter“ DCD ”). And an uplink channel descriptor (hereinafter referred to as 'UCD'). The cell periodically provides downlink and uplink physical channel characteristics to the mobile terminal via DCD / UCD messages. Here, the cell can be used to display a base station (BS).

  The base station configures a downlink burst profile (Downlink_Burst_Profile) based on the received signal quality of each mobile terminal. That is, using the channel quality information (Channel Quality Information; hereinafter referred to as 'CQI') transferred from each mobile terminal, a downlink burst profile (or adaptive modulation and coding (or As an auxiliary means, Downlink Burst Profile Change (DBPC) request or response (ie, DBPC-REQ / RSP) is configured as an auxiliary means. And the downlink burst profile may be modified or changed through a ranging request / response (RNG-REQ / RSP) process.

  FIG. 1 is an example showing a critical value for changing a burst profile. The mobile terminal measures the signal-to-noise ratio (SINR), eg C / (N + I), and compares it with the average value for the allowed operating range. The operating range is limited by a threshold level. That is, when the signal-to-noise ratio is out of the allowable operating range, the terminal requests a new burst profile using the DBPC method. Does the mobile terminal request a more robust profile with stronger interference (eg, Quadrature Phase Shift Keying; QPSK), or request a less robust profile with less interference ( For example, according to 64 Quadrature Amplitude Modulation (64QAM), the base station transfers and receives messages for substantial changes in modulation schemes. Here, the term 'stronger' means that there is stronger interference, and the term 'not stronger' means that there is less interference.

  According to the prior art, when there are a plurality of code types that can be supported by the mobile terminal within the service support range of the base station, and the downlink / uplink burst profile supports various code types. When used, the signal-to-noise ratio (SNR) interval (or space) corresponding to each AMC is increased. Therefore, the modulation schemes that can be provided for one coding type are reduced. As a result, the interval between the critical values used for changing the AMC for each coding type increases, and there is a problem in appropriately applying AMC according to the channel state.

  Accordingly, the present invention relates to a method for supporting multiple code types in a wireless mobile communication system, which eliminates one or more problems due to limitations and disadvantages in the prior art as described above.

  An object of the present invention is to provide a method for supporting multiple codes in a wireless mobile communication system.

  Additional advantages, objects and features of the invention will be set forth in part in the description which follows, and in part will be obvious to those of ordinary skill in the art relating to the description below, or It will become clear by the practice of the invention. The objectives and other advantages of the invention may be realized or attained by the structure particularly pointed out in the written description and drawings hereof.

  As embodied and comprehensively described herein, in order to achieve these and other advantages and to be consistent with the objectives of the present invention, as an aspect of the present invention, multiple codes are supported in a wireless mobile communication system. The method includes including a mobile terminal that receives a channel descriptor from a base station. Here, the channel descriptor includes at least one burst profile including a code type and a period use code. Therefore, first, the mobile terminal recognizes a code type including information on a coding scheme used by the base station or the terminal. Subsequently, the terminal recognizes a section usage code used to classify all data bursts.

  As another aspect of the present invention, the terminal receives a downlink channel descriptor (DCD) from a base station. Here, the DCD includes at least one burst profile. After receiving the DCD, the terminal recognizes a code type including information on a coding scheme used in the base station and a period use code used to classify all data bursts.

  As yet another aspect of the present invention, the terminal receives an uplink channel descriptor (UCD) from one terminal. Here, the UCD includes at least one burst profile. After receiving the UCD, the terminal recognizes a code type including information on a coding scheme used in the base station and an interval use code used to classify all data bursts.

  As yet another aspect of the present invention, the terminal receives a channel descriptor from the base station. Here, the channel descriptor includes at least one burst profile set including a plurality of burst profiles further including a period use code and at least one code type. Therefore, the terminal first recognizes at least one code type including information on the coding scheme used in the base station or the terminal. Subsequently, the terminal recognizes a section use code used for classifying all data bursts.

  It is to be understood that both the foregoing general description and the following detailed description of the invention are exemplary and explanatory and are intended to provide additional explanation of the invention as claimed. Should be understood.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same components are denoted by the same reference numerals as much as possible.

First, an example of a DCD message is shown in Table 1.
(Table 1)

表２には、ＵＣＤメッセージの一例を示す。
（表２）

Table 2 shows an example of a UCD message.
(Table 2)

該ＤＣＤ／ＵＣＤメッセージはそれぞれ、ダウンリンクとアップリンクに割り当てられたバースト区間のための物理階層パラメータを含む。該物理階層パラメータの一例に、変調タイプ（ｍｏｄｕｌａｔｉｏｎ ｔｙｐｅ）と順方向誤り訂正（Ｆｏｒｗａｒｄ Ｅｒｒｏｒ Ｃｏｒｒｅｃｔｉｏｎ；以下、‘ＦＥＣ’という。）コードタイプがある。また、これらのＦＥＣコードタイプのためのパラメータは、例えば、ＲＳ（Ｒｅｅｄ−Ｓｏｌｏｍｏｎ）コードのＫ、Ｒ値などによって表現されることができる。

Each of the DCD / UCD messages includes physical layer parameters for burst periods assigned to the downlink and uplink. Examples of the physical layer parameters include a modulation type and a forward error correction (hereinafter referred to as “FEC”) code type. The parameters for these FEC code types can be expressed by, for example, K, R values of RS (Reed-Solomon) codes.

  These parameters are mapped to UIUC or DIUC included in the downlink burst profile Downlink_Burst_Profile of the DCD message and the uplink burst profile Uplink_Burst_Profile of the UCD message. That is, the downlink burst profile Downlink_Burst_Profile information included in the DCD can define the characteristics of the physical layer used for a specific downlink burst using the corresponding DIUC.

Table 3 shows an example of a downlink burst profile TLV format.
(Table 3)

表３に示すように、ダウンリンクバーストプロファイルは、４ビット長のＤＩＵＣを含む。該ＤＩＵＣは４ビットの情報を持つから、１６個の相異なる情報（例えば、コーディング及び変調方式）をマッピングさせることができる。なお、基地局またはセルは、１３個のバーストプロファイルを選択してＤＩＵＣ０〜ＤＩＵＣ１２に割り当てることができ、ＦＥＣコードタイプをそれぞれのＤＩＵＣにマッピングさせることができる。

As shown in Table 3, the downlink burst profile includes a 4-bit DIUC. Since the DIUC has 4-bit information, 16 different pieces of information (for example, coding and modulation schemes) can be mapped. The base station or cell can select 13 burst profiles and assign them to DIUC0 to DIUC12, and can map the FEC code type to each DIUC.

  Meanwhile, the uplink burst profile included in the UCD message can define the characteristics of the physical layer used for the specific uplink burst using the corresponding UIUC.

Table 4 shows an example of the uplink burst profile TLV format.
(Table 4)

表４に示すように、アップリンクバーストプロファイルは、４ビット長のＵＩＵＣを含む。該ＵＩＵＣは４ビットの情報を持つから、１６個の相異なる情報（例えば、コーディング及び変調方式）をマッピングさせることができる。また、基地局またはセルは１０個のバーストプロファイルを選択してＵＩＵＣ０〜ＵＩＵＣ１０に割り当てることができ、ＦＥＣコードタイプをそれぞれのＵＩＵＣにマッピングさせることができる。その後、基地局は、ＤＣＤ／ＵＣＤメッセージを介して選択されたバーストプロファイルを通知する。表５及び表６に、ＴＬＶ（タイプ（Ｔｙｐｅ）、長さ（Ｌｅｎｇｔｈ）、値（Ｖａｕｌｅ））フォーマットのダウンリンクバーストプロファイルの一例を示す。
（表５）

As shown in Table 4, the uplink burst profile includes a 4-bit UIUC. Since the UIUC has 4-bit information, 16 different pieces of information (for example, coding and modulation schemes) can be mapped. Also, the base station or cell can select 10 burst profiles and assign them to UIUC0 to UIUC10, and the FEC code type can be mapped to each UIUC. Thereafter, the base station notifies the selected burst profile via the DCD / UCD message. Tables 5 and 6 show examples of downlink burst profiles in the TLV (Type (Type), Length (Length), Value (Value)) format.
(Table 5)

（表６）

(Table 6)

表７には、ＴＬＶ（タイプ（Ｔｙｐｅ）、長さ（Ｌｅｎｇｔｈ）、値（Ｖａｕｌｅ））フォーマットのアップリンクバーストプロファイルの一例を示す。
（表７）

Table 7 shows an example of an uplink burst profile in a TLV (type (Type), length (Length), value (Value)) format.
(Table 7)

表３を用いて、基地局はＦＥＣコードタイプを１３個のＤＩＵＣ（すなわち、ＤＩＵＣ０〜ＤＩＵＣ１２）にマッピングすることによってダウンリンクバーストプロファイルを構成する。マッピング方法は、加入者ステーション基本性能要請及び応答（Ｓｕｂｓｃｒｉｂｅｒ Ｓｔａｔｉｏｎ Ｂａｓｉｃ Ｃａｐａｂｉｌｉｔｙ ｒｅｑｕｅｓｔ ａｎｄ ｒｅｓｐｏｎｓｅ；ＳＢＣ−ＲＥＱ／ＲＳＰ）過程を用いて、移動端末が支援可能なコーディングタイプを話し合う（ｎｅｇｏｔｉａｔｉｎｇ）過程を含む。表８及び表９に、移動端末が支援可能な変調及び復調の一例を示す。
（表８）

Using Table 3, the base station configures the downlink burst profile by mapping FEC code types to 13 DIUCs (ie, DIUC0 to DIUC12). The mapping method includes a process of negotiating coding types that can be supported by the mobile terminal using a subscriber station basic capability request and response (SBC-REQ / RSP) process. Tables 8 and 9 show examples of modulation and demodulation that can be supported by the mobile terminal.
(Table 8)

（表９）

(Table 9)

ＦＥＣコードタイプと関連して、例えば、畳み込みコード（Ｃｏｎｖｏｌｕｔｉｏｎａｌ Ｃｏｄｅ；以下、‘ＣＣ’という。）、ブロックターボコーディング（Ｂｌｏｃｋ Ｔｕｒｂｏ Ｃｏｄｉｎｇ；以下、‘ＢＴＣ’という。）、畳み込みターボコード（Ｃｏｎｖｏｌｕｔｉｏｎａｌ Ｔｕｒｂｏ Ｃｏｄｅ；以下‘ＣＴＣ’という。）、ゼロテール畳み込みコード（Ｚｅｒｏ Ｔａｉｌ Ｃｏｎｖｏｌｕｔｉｏｎ Ｃｏｄｅ；以下、‘ＺＴＣＣ’という。）及び低密度パリティコード（Ｌｏｗ Ｄｅｎｓｉｔｙ Ｐａｒｉｔｙ Ｃｏｄｅ；以下、‘ＬＤＰＣ’という。）などがある。このようなＦＥＣタイプのうち、ＣＣは必須に考慮され、残りのタイプは選択的に考慮される。

In connection with the FEC code type, for example, a convolutional code (Convolutional Code; hereinafter referred to as 'CC'), a block turbo coding (Block Turbo Coding; hereinafter referred to as 'BTC'), a convolutional turbo code (Convolutional Turbo Code; Hereafter referred to as 'CTC'), zero tail convolutional code (hereinafter referred to as 'ZTCC'), and low density parity code (hereinafter referred to as 'LDPC'). Of these FEC types, CC is considered essential and the remaining types are selectively considered.

  Since the CC is essential in operation, the base station always uses the CC. Since the DIUC can be mapped to 16 different information, the CC is mapped to a maximum of 6 DIUC (for example, DIUC0 to DIUC5) values, and the remaining 6 values are any of BTC, CTC, ZTTC, or LDPC. Map selectively.

  Also in UIUC, a basic CC maps to a maximum of 6 UIUC (for example, UIUC0 to UIUC5) values, and the remaining 6 values are selectively mapped to any of BTC, CTC, ZTTC, or LDPC.

  As an embodiment of the present invention, a burst profile generation method is disclosed, the detailed contents of which are as follows. First, each critical value expressed in the TLV format is mapped to each DIUC / UIUC value on a one-to-one basis. The number of values mapped is the same as the number of DIUC / UIUC to be set. Here, the critical value is a standard for requesting change of the FEC code type and the burst profile. The burst profile includes information regarding the coding type of the burst profile.

Table 10 shows an example of a downlink burst profile.
(Table 10)

表１１には、アップリンクバーストプロファイルの一例を示す。
（表１１）

Table 11 shows an example of the uplink burst profile.
(Table 11)

図２は、コーディングタイプによってＡＭＣをＤＩＵＣにマッピングする方法を例示するダイヤグラムである。様々なコーディングタイプのうち、基地局は基本的にＣＣを使用する。言い換えると、ＣＣタイプは常に使用される（すなわち、基本的なＣＣ）。このように、基本的なＣＣのためのＤＩＵＣは、ｔｙｐｅ＝１のＤｏｗｎｌｉｎｋ＿Ｂｕｒｓｔ＿Ｐｒｏｆｉｌｅと呼ばれる。図２に示すように、基本的なＣＣは、ＤＩＵＣ０〜ＤＩＵＣ５とＵＩＵＣ０〜ＤＩＵＣ６（２１）にマッピングされるか割り当てられる。すなわち、例えば、表１０に示すように、“Ｃｏｄｉｎｇ Ｔｙｐｅ”フィールドは‘００１’に設定されることができ、これは基本的なＣＣを表す。そして、ＡＭＣは、６個のＤＩＵＣ／ＵＩＵＣ値にそれぞれマッピングさせることができる。

FIG. 2 is a diagram illustrating a method for mapping AMC to DIUC by coding type. Among various coding types, the base station basically uses CC. In other words, the CC type is always used (ie basic CC). Thus, the DIUC for a basic CC is called Downlink_Burst_Profile with type = 1. As shown in FIG. 2, basic CCs are mapped or assigned to DIUC0 to DIUC5 and UIUC0 to DIUC6 (21). That is, for example, as shown in Table 10, the “Coding Type” field can be set to “001”, which represents a basic CC. AMC can be mapped to each of six DIUC / UIUC values.

  Note that in order to assign different coding types to the remaining DIUCs, the base station assigns different coding types to DIUC6 to DIUC12. Here, the coding type assigned to DIUC6 to DIUC12 is different from the coding type (ie, CC) assigned to DIUC0 to DIUC5. For example, if the base station decides to use BTC in addition to the basic CC, the 'Coding Type' field is set to '010' as indicated by BTC in Table 10, and AMC is set to DIUC6 to DIUC12 ( 22). In addition to this, when the base station also supports CTC and LDPC, the 'Coding Type Set' field is set to '011' or '101', respectively, and AMC is mapped to each set of DIUC6 to DIUC12 ( 23, 24).

Table 12 shows another example of the downlink burst profile.
(Table 12)

表１３には、アップリンクバーストプロファイルの他の例を示す。
（表１３）

Table 13 shows another example of the uplink burst profile.
(Table 13)

図３は、コーディングタイプによってＡＭＣをＤＩＵＣにマッピングする方法を例示するダイヤグラムである。図３に示すように、各コーディングタイプの組合せは、バーストプロファイルを構成するのに用いられることができる。様々なコーディングタイプのうち、基地局は基本的にＣＣを割り当てる。このように、基地局は、基地局によって付加的に支援されるコーディングタイプによって‘Ｃｏｄｅ Ｔｙｐｅ Ｓｅｔ’フィールドを設定する。例えば、基地局が基本的なＣＣの外にＢＴＣを支援する場合、‘Ｃｏｄｅ Ｔｙｐｅ Ｓｅｔ’フィールドを‘００１’と設定する。このような設定下で、基本的なＣＣはＤＩＵＣ０〜ＤＩＵＣ５及びＵＩＵＣ１〜ＤＩＵＣ６に割り当てられ、ＢＴＣはＤＩＵＣ６〜ＤＩＵＣ１２に割り当てられる（３１）。

FIG. 3 is a diagram illustrating a method for mapping AMC to DIUC by coding type. As shown in FIG. 3, each coding type combination can be used to construct a burst profile. Of the various coding types, the base station basically assigns CCs. As such, the base station sets the 'Code Type Set' field according to the coding type additionally supported by the base station. For example, when the base station supports BTC in addition to the basic CC, the 'Code Type Set' field is set to '001'. Under such settings, basic CCs are assigned to DIUC0 to DIUC5 and UIUC1 to DIUC6, and BTCs are assigned to DIUC6 to DIUC12 (31).

  On the other hand, when the base station supports CTC in addition to the basic CC, the 'Code Type Set' field is set to '010', the basic CC is assigned to DIUC0 to DIUC5 and UIUC1 to DIUC6, and the CTC is assigned to DIUC6. Assign to DIUC 12 (32).

  On the other hand, when the base station supports LDPC in addition to the basic CC, the 'Code Type Set' field is set to '100', the basic CC is assigned to DIUC0 to DIUC5 and UIUC1 to DIUC6, and the LDPC is assigned to DIUC6. Assign to DIUC 12 (33).

  FIG. 4 is a diagram illustrating an example of a burst profile application method.

  As shown in FIG. 4, the mobile terminal receives a burst profile generated based on each coding type via a UCD / DCD message (S41). Thereafter, the mobile terminal and the base station discuss coding types that can be supported by the SBC-REQ / RSP process (S42, S43). After receiving the SBC-RSP message from the base station, the terminal analyzes a DIUC value corresponding to 'Coding Type' or 'Code Type Set' that can be supported by the terminal itself.

  After receiving a burst profile via a UCD / DCD message and discussing a coding type that can be supported with the base station, when the coding type is determined (eg, determined by LDPC), it represents the CC and LDPC types. The AMC is applied to a specific burst allocated to the mobile terminal, and the mobile terminal receives a downlink signal based on the AMC (S44).

  On the other hand, using the DL-MAP / UL-MAP IE, the mobile terminal using the specific coding type can be notified of the new coding type. When a new coding scheme is added via the extended DIUC / UIUC, the new FEC code type may be notified to all mobile terminals via the extended DIUC.

  FIG. 5 is a diagram illustrating another example of the burst profile application method. As shown in FIG. 5, the mobile terminal supports one basic coding type and two newly added improved coding types. The mobile terminal reports a coding scheme that the terminal itself can support via the SBC-REQ message (S51). In response to this, the base station informs the mobile terminal of the newly added improved coding type that the base station intends to support via the SBC-RSP message (S52). For application of the DIUC / UIUC, the mobile terminal recognizes the DIUC / UIUC value of the burst profile included in the DCD received from the base station.

  As shown in FIG. 5, the mobile terminal uses at least one CC, CTC, and LDPC. For example, if the mobile terminal uses basic CC and can support CTC and LDPC at the same time, the mobile terminal may indicate that this new coding type (eg, CTC or LDPC) is possible via the SBC-REQ. To report to. The base station receives this, selects one of the two coding types (ie, LDPC), and informs the terminal of this via the SBC-RSP message. Thereafter, the mobile terminal analyzes the DIUC / UIUC value so as to match the LDPC.

  The 'Type' field included in the DCD / UCD can be used to distinguish the type of information required for the mobile terminal. For example, as shown in Tables 3 and 4, the 'Type' field is set to '1'. Usually, the 'Type' field is used to determine the burst profile. As described above, the burst profile includes using at least one coding type including the basic coding type, and sets the 'Type' field to '1'. The burst profile with the new coding type can then be used to signal the new coding type.

Table 14 shows still another example of the downlink burst profile. Here, Table 14 defines the format of Downlink_Burst_Profile of Type = 153, and this format is used only in the DCD message for the MS. The DIUC field is associated with Downlink_Burst_Profile and a critical value. The DIUC value is used in the DL-MAP message to specify the burst profile to be used for a specific downlink burst.
(Table 14)

‘Ｔｙｐｅ’フィールドが‘１’に設定される時と同様に、ここでは、バーストプロファイルで‘Ｔｙｐｅ’フィールドを‘１５３’と設定する。移動端末は、‘Ｔｙｐｅ’フィールドが‘１’の値を持つバーストプロファイルを使用し、少なくとも一つのコーディングタイプ（すなわち、ＣＣ）のＡＭＣレベルマッピングがわかる（または、これに対する情報を受信する）。端末が、‘１５３’に設定された‘Ｔｙｐｅ’フィールドを持つバーストプロファイルを受信すると、端末は保有しているコーディング方式のみを選択できる。

In the same manner as when the “Type” field is set to “1”, here, the “Type” field is set to “153” in the burst profile. The mobile terminal uses a burst profile having a value of '1' in the 'Type' field and knows (or receives information about) an AMC level mapping of at least one coding type (ie, CC). When the terminal receives a burst profile having a “Type” field set to “153”, the terminal can select only the coding scheme that the terminal has.

Table 15 shows still another example of the uplink burst profile.
(Table 15)

表１６には、ＵＣＤに含まれる値の一例を示す。
（表１６）

Table 16 shows an example of values included in the UCD.
(Table 16)

表１７には、ＤＣＤに含まれる値の一例を示す。
（表１７）

Table 17 shows an example of values included in the DCD.
(Table 17)

上記の表１６及び１７に示すように、ＤＣＤやＵＣＤに含まれる‘Ｔｙｐｅ’フィールドの値が解析されることができる。なお、‘Ｔｙｐｅ’フィールドの値が定義されると、‘Ｔｙｐｅ’フィールドの値が１に設定されることを知らせるバーストプロファイルの他に、ＤＣＤ／ＵＣＤが新しいバーストプロファイルの存在を知らせるのに用いられることができる。

As shown in Tables 16 and 17 above, the value of the “Type” field included in the DCD or UCD can be analyzed. When the value of the 'Type' field is defined, the DCD / UCD is used to notify the existence of a new burst profile in addition to the burst profile that informs that the value of the 'Type' field is set to 1. be able to.

  It will be apparent to those skilled in the art that various modifications and variations of the present invention can be made without departing from the spirit and scope of the invention. Accordingly, the present invention includes any modifications and variations provided within the scope of the appended claims and their equivalents.

It is a figure which shows an example of the critical value for the change of a burst profile. 6 is a diagram illustrating a method for mapping AMC to DIUC according to coding type. 6 is a diagram illustrating a method for mapping AMC to DIUC according to coding type. It is a figure which shows an example of the burst profile application method. It is a figure which shows the other example of the burst profile application method.

Claims (14)

A method for supporting multiple code types in a wireless mobile communication system, comprising:
The method
The method comprising: receiving a downlink channel descriptor (DCD) from a base station (BS), the DCD is seen contains at least one downlink burst profile, the at least one downlink burst profile includes a type field And when the type field is set to 153, the at least one downlink burst profile includes a code type field and the type field is set to 1. Wherein the at least one downlink burst profile does not include the code type field; and
Recognizing the code type field when the code type field is included in the at least one downlink burst profile, the code type field being a downlink associated with the at least one downlink burst profile; Indicating the coding scheme used by the BS to encode link bursts;
Recognizing the DIUC field used to classify the at least one downlink burst profile used for the downlink burst;
Including the method. The coding scheme, block turbo coding (BTC), convolutional turbo code (CTC), at least one of Zeroteru convolutional codes (ZTCC) or low density parity code (LDPC), how according to claim 1 . The method of claim 1, wherein the DIUC field for a basic convolutional code is associated with the at least one downlink burst profile with the type field set to one. The code type field of the at least one downlink burst profile supports code types from multiple code classifications when the type field of the at least one downlink burst profile is set to a value 153. The method according to 1. The method of claim 1, wherein if the value of the type field of the at least one downlink burst profile is set to 153, the at least one downlink burst profile is used in the DCD for mobile stations only. The method according to claim 1, wherein if the value of the type field of the at least one downlink burst profile is set to 153, only the coding scheme maintained by the mobile station is selected by the mobile station. The at least one downlink burst profile further includes a type / length / value (TLV) encoding information field;
The method of claim 1, wherein the TLV encoded information field includes a forward error correction code type, a DIUC basic advance threshold, and a DIUC minimum entry critical value. A mobile station for a wireless mobile communication system that supports multiple code types, comprising:
The mobile station
A receiver for receiving a downlink channel descriptor (DCD) from a base station (BS), the DCD including at least one downlink burst profile, wherein the at least one downlink burst profile includes a type field and And when the type field is set to 153, the at least one downlink burst profile includes a code type field and the type field is set to 1. And wherein the at least one downlink burst profile does not include the code type field; and
Recognizing the code type field when the code type field is included in the at least one downlink burst profile, the at least one used for a downlink burst associated with the at least one downlink burst profile. A processor that recognizes the DIUC field used to classify one downlink burst profile, wherein the code type field indicates a coding scheme used by the BS to encode the downlink burst; With processor
A mobile station comprising: The mobile station according to claim 8, wherein the DIUC field for a basic convolutional code is associated with the at least one downlink burst profile in which the type field is set to one. The mobile station according to claim 8, wherein the coding scheme is at least one of block turbo coding (BTC), convolutional turbo code (CTC), zero tail convolutional code (ZTCC), or low density parity code (LDPC). . The code type field of the at least one downlink burst profile supports code types from multiple code classifications when the type field of the at least one downlink burst profile is set to a value 153. 8. The mobile station according to 8. The mobile according to claim 8, wherein if the value of the type field of the at least one downlink burst profile is set to 153, the at least one downlink burst profile is used in the DCD for only the mobile station. Bureau. The mobile station according to claim 8, wherein when a value of the type field of the at least one downlink burst profile is set to 153, only a coding scheme held by the mobile station is selected by the mobile station. . The at least one downlink burst profile further includes a type / length / value (TLV) encoding information field;
The mobile station according to claim 8, wherein the TLV encoded information field includes a forward error correction code type, a DIUC basic advance threshold, and a DIUC minimum entry critical value.

Images