TWI420868B - Method of supporting multiple codes in a wireless mobile communication system - Google Patents

Description

Method for supporting multiple encoding in a wireless mobile communication system

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

In a broadband wireless access system, an orthogonal frequency division multiple access (OFDMA) scheme is used to transmit data. When using the OFDMA scheme, the structure of the frame is defined as follows. First, the downlink frame indicates a preamble at the beginning of the frame, which can be used for time synchronization between a mobile station (MS) and a base station (BS), and simultaneously used in a physical layer for the channel. Equalization. The frame includes a downlink mapping (DL-MAP) message and an uplink mapping (UL-MAP) message, which defines the location and purpose of the allocated burst.

More specifically, the DL-MAP message defines the use of the bursts allocated in the downlink section below the frame. Similarly, the UL-MAP message defines the use of bursts allocated in the uplink section of the frame. An information element (IE) included in the DL-MAP is based on a downlink interval usage code (DIUC), a connection identification (CID), and a location of a burst signal (eg, a secondary channel offset). , symbol offset, number of secondary channels, and number of symbols are classified in a downlink traffic section under a group of users.

The use of the IE of the UL-MAP is determined by an uplink interval usage code (UIUC) for each CID. In addition, the corresponding location of an uplink traffic segment is defined by duration. Here, the use of each section is determined according to the UIUC value used by the UL-MAP. The starting point of each segment is one of the duration amounts set in the UL-MAP IE from the previous IE start offset.

The MS receives a Link Channel Descriptor (DCD) message and an Uplink Channel Descriptor (UCD) message for the network to enter or re-enter the network for handover or for other reasons. A unit periodically provides physical channel features for the downlink and uplink via DCD/UCD messages. Here, the unit can also be used to represent a base station (BS).

The BS configuration configures Downlink_Burst_Profile according to the received signal quality of each MS. In other words, the BS uses a channel quality information (CQI) transmitted from each MS, and configures a Downlink_Burst_Profile or an Adotive Modulation and Coding (AMC) according to the channel state of each MS. Alternatively, as a supportive method, Downlink_Burst_Profile can be used by using a downlink burst profile change (DBPC) request or response (ie DBPC-REQ/RSP), and a ranging request/response (RNG-REQ/) RSP) program to modify or change.

Figure 1 shows an example of a limit value for modifying a burst profile. The MS measures a signal-to-noise ratio (SINR), such as C/(N+1), and compares it to an average of the allowed application ranges. The range of applications is limited to a limited level. That is, if the SINR exceeds the allowable application range, the MS uses a DBPC scheme to request a new burst profile. Depending on whether the MS requests a more robust profile with stronger interference (eg, four-phase keying) or whether the MS requests a less robust profile with less interference (eg, 64 quad amplitude modulation), the BS targets The actual change of the modulation scheme to perform the transmission and reception of the message. Here, the term "more robust" means that there is a strong interference, and the noun "less robust" refers to less interference.

According to the prior art, if there is a complex coding type supported by the MS within the effective service area of the BS, and if the downlink/uplink burst configuration file is used to support various coding types, it corresponds to each AMC. The interval (or space) of SNR will increase. Therefore, a modulation scheme that can be provided for a coding type is reduced. As a result, the interval for changing the limit value of the AMC for each coding type is increased, and thus there is a problem in correctly applying the AMC in accordance with the channel state.

Accordingly, the present invention is directed to a method of supporting multiple coding types in a wireless mobile communication system that substantially obviates one or more of the problems due to the limitations and disadvantages of the prior art.

It is an object of the present invention to provide a method of supporting multiple coding types in a wireless mobile communication system.

Additional features and advantages of the invention will be set forth in part in the description which follows. The objectives and other advantages of the present invention can be realized and attained by the written description and the appended claims.

To achieve these and other advantages and in accordance with the purpose of the present invention (as encompassed and broadly described herein), a method of supporting multiple coding types in a wireless mobile communication system includes a mobile station (MS) from a base station The (BS) receives a channel descriptor, wherein the channel descriptor includes at least one burst profile including an encoding type and an interval usage code. Thereafter, the MS first identifies the type of encoding of the information included in the encoding scheme to be used by the BS or MS, and secondly identifies an interval usage code for classifying all bursts of data.

In another aspect of the invention, the MS receives a downlink channel descriptor (DCD) from a base station (BS), wherein the DCD includes at least one burst profile. After receiving, the MS recognizes a coding type of information included in the coding scheme to be used by the BS, and an interval usage code for classifying all data bursts.

In another aspect of the invention, the MS receives an uplink channel descriptor (UCD) from a mobile station (MS), wherein the UCD includes at least one burst profile. After receiving, the MS recognizes a coding type of information included in the coding scheme to be used by the MS, and an interval usage code for classifying all data bursts.

In a further aspect of the invention, the MS receives a channel descriptor from a base station (BS), wherein the channel descriptor includes at least one burst profile set including a plurality of burst profiles, the burst profile It further includes an interval usage code and at least one coding type. Thereafter, the MS first identifies at least one coding type of information included in the coding scheme to be used by the BS or the MS, and secondly identifies an interval usage code for classifying all data bursts.

It is to be understood that the foregoing general description of the invention,

DETAILED DESCRIPTION OF THE INVENTION Reference will now be made in detail to the preferred embodiments embodiments The same reference numbers are used throughout the drawings to refer to the same or the like.

Table 1 is an example of a DCD message.

Table 2 is an example of a UCD message.

The DCD/UCD messages each include physical layer parameters for the uplink and downlink allocation burst intervals. As for the instance of the physical layer parameter, there is a modulation type and a forward error correction (FEC) coding type. Further, the parameters for the FEC encoding type can be expressed by, for example, the K and R values of the Reed-Solomon (RS) code.

These parameters are mapped to the DIUC included in the Downlink_Burst_Profile of the DCD message, and the UIUC included in the Uplink_Burst_Profile of the UCD message. That is, the Downlink_Burst_Profile information included in the DCD message can be used by DIUC to define certain features of the physical layer for a particular downlink burst.

Table 3 is an example of a Downlink_Burst_Profile TLV format.

As shown in Table 3, the downlink burst profile includes a DIUC having a 4-bit length. Because DIUC has a 4-bit length, it can represent 16 different information (eg, coding and modulation schemes). In addition, the BS or unit can select and assign 13 burst profiles to DIUC0-DIUC12, and the FEC type can be mapped to each DIUC. The BS can then publish the selected burst profile via the DCD/UCD message.

Alternatively, the uplink burst profile included in the UCD message may use UIUC to define certain features of the physical layer used by a particular uplink.

Table 4 is an example of the Uplink_Burst_Profile TLV format.

As shown in Table 4, the uplink burst profile includes a UIUC having a 4-bit length. Because UIUC has a 4-bit length, it can represent 16 different information (such as encoding and modulation schemes). In addition, the BS or the unit can select and assign 10 burst profiles to UIUC0_UIUC10, and the FEC type can be mapped to each DIUC. The BS can then publish the selected burst profile via the DCD/UCD message.

Tables 5 and 6 are examples of downlink burst configuration files in one of Type, Length, and Value (TLV) formats.

Table 7 is an example of an uplink burst profile in the Type, Length, Value (TLV) format.

Using Table 3, the BS maps the FEC encoding type to 13 DIUC (ie, DIUC0-DIUC12) to configure the downlink burst configuration file. The mapping procedure includes the type of encoding available for negotiation by the MS using a Subscriber Station Basic Capability Request and Response (SBC-REQ/RSP) procedure.

Tables 8 and 9 are examples of modulation and demodulation schemes that can be supported by the MS.

As far as the FEC coding type is concerned, only a few examples are given: a convolutional code (CC), a block acceleration code (BTC), a cyclotron accelerometer (CTC), a zero-tailed convolutional code (ZTTC), and a low density. Parity code (LDPC). Among these FEC types, CC is considered mandatory and other types are visually selectable.

In operation, the BS constantly uses the CC because of its compulsory. In addition, since DIUC can be mapped to 16 different information, CC is mapped to up to 6 values of DIUC (eg, DIUC0-DIUC5), while the remaining 6 values are selectively mapped by any of BTC, CTC, ZTTC, and LDPC. .

Even in the case of UIUC, the mandatory CC is mapped to a maximum of 6 values (eg, UIUC0-UIUC5), while the remaining 6 values are selectively mapped by any of BTC, CTC, ZTTC, and LDPC.

In connection with an embodiment of the present invention, a method of generating a burst profile has been described, the details of which are as follows. First, each threshold value expressed in the TLV format is mapped to each DIUC/UIUC value on a one-to-one basis. The number of mapped values is equal to the number of DIUC/UIUC to be configured. Here, the threshold is to correct (or change) the request based on the FEC encoding type and the burst profile. In addition, the burst profile includes information related to the encoding type of the burst profile.

Table 10 shows an example of a downlink burst profile.

Table 11 shows an example of an uplink burst profile.

Figure 2 is a diagram showing an example of mapping AMC to a DIUC according to a coding type. From among the various available coding types, the BS uses the CC as a preset, or in other words, always uses the CC type (ie, forcing CC). Therefore, the DIUC available type=1 for forcing the CC refers to Downlink_Burst_Profile. As shown in Fig. 2, the CC is forced to be mapped or assigned to DIUC0-DIUC5 and UIUC0-DIUC6 (21). That is, as shown in Table 10, for example, "encoding type", the field can be set to "001", which means that the mandatory CC and the AMC can be mapped to each of the 6DIUC/UIUC.

Furthermore, in order to assign different coding types to the remaining DIUC, the BS assigns different coding types to DIUC6-DIUC12. Here, the coding type assigned to DIUC6-DIUC12 is different from the coding type (ie, CC) assigned to DIUC0-DIUC5. For example, if the BS decides to use BTC in addition to the mandatory CC, the "Code Type" field is set to "010", which represents the BTC indicated in Table 10, and the AMC is mapped to DIUC6-DIUC12 (22). Alternatively, if the BS supports CTC or LDPC, the ┌Encoding Type Group field can be set to "011" or "101", respectively, and the AMC is mapped to each group of DIUC6-DIUC12 (23, 24).

Table 12 is another example of a downlink burst profile.

Table 13 is another example of an uplink burst profile.

Figure 3 shows an example diagram of mapping AMC to DIUC according to a coding type. As shown in Figure 3, a burst profile can be configured with a combination of encoding types. Among many coding types, the BS assigns a mandatory CC. Therefore, the BS configures the "Code Type Group" field according to the type code additionally supported by the BS. For example, if the BS supports BTC in addition to the CC, of course, the "Code Type Group" field is set to "001". Under this setting, the CC system is assigned to DIUC0-DIUC5 and UIUC1-DIUC6, and the BTC is assigned to DIUC6-DIUC12 (31).

Or, if the BS supports the CTC in addition to the mandatory CC, the "Code Type Group" field is set to "010", the CC system is assigned to DIUC0-DIUC5 and UIUC1-DIUC6, and the CTC is assigned to DIUC6-DIUC12 (32). ).

Alternatively, if the BS supports LDPC in addition to the mandatory CC, the "Code Type Group" field is set to "100", the CC system is assigned to DIUC0-DIUC5 and UIUC1-DIUC6, and the LDPC is assigned to DIUC6-DIUC12 (33). ).

Figure 4 shows an example of a method of applying a burst profile. As shown in FIG. 4, the MS receives the burst profile generated based on each coding type via the DCD/UCD message (S41). Thereafter, the MS and the BS use the SBC-REQ/RSP method to negotiate the types of codes that can be separately supported (S42, S43). After receiving the SBC-RSP message from the BS, the MS interprets the DIUC value corresponding to the "coding type" or "encoding type group" that can be supported by the MS.

After receiving the burst profile via the DCD/UCD message and negotiating the supported coding type with the BS, if the coding type (eg, LDPC type) has been determined, the AMC system representing the CC and LDPC types is applied to the MS. The specific burst is transmitted, and the MS receives the downlink signal according to the AMC (S44).

Alternatively, an IE of DL-MAP/UL-MAP may be used to provide a new coding type to an MS currently using a particular coding type. When a new encoding type is added via the extended DIUC/UIUC, a new FEC encoding type can be provided to all MSs via the extended DIUC.

Figure 5 illustrates an example of a method of applying another burst profile. As shown in Figure 5, the MS supports a preset encoding type and two new enhanced encoding types. The MS uses the REG-REQ message to report the type of coding that can be supported by the MS (S51). In response, the BS uses the SBC-RSP message to inform the MS of the new enhanced coding type that the BS is expected to support (S52). In order to apply DIUC/UIUC, the MS recognizes the DIUC/UIUC value of the burst profile included in the DCD transmitted by the BS, which has the coding type assigned by the BS.

As shown in FIG. 5, the MS uses at least one of CC, CTC, and LDPC type codes. For example, if the MS uses a mandatory CC and can support both CTC and LDPC, the MS reports to the BS via the SBC-REQ message that the availability of the two coding types (eg, CTC or LDPC) is transparent. When receiving, the BS selects one of the two coding types (ie, LDPC) and transmits the selection to the MS via the SBC-RSP message. After that, the MS recognizes the DIUC/UIUC value according to the LDPC.

In addition, a "type" field included in the DCD/UCD can be used to distinguish the type of information that the MS needs. For example, as shown in Tables 3 and 4, the "Type" field is set to "1". The conventional "type" field is used to determine the burst configuration file. As described above, the burst configuration file includes using at least one encoding type (including a preset encoding type) and configuring the "type" field to be "1". In addition, a burst profile using a new encoding type can be used to notify a new encoding type.

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

Similar to when the "Type" field is set to "1", the "Type" field in the burst configuration file is set to "1". The MS uses the burst configuration file with the "Type" field set to "1" to understand (or receive information) the AMC layer mapping of at least one encoding type (ie, CC). If the MS receives a burst profile with "Type" set to "153", the MS can only select the type of encoding held by the MS.

Table 15 shows another example of an uplink burst profile.

Table 16 is an example showing the value of UCD.

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

As shown in Tables 16 and 17, the values included in the "Type" field in the DCD or UCD can be interpreted. Furthermore, when defining the value of the "Type" field, the DCD/UCD is also used to indicate a new burst profile in addition to the burst profile that indicates that the value of the "Type" field is set to "1". presence.

A person skilled in the art will appreciate that various modifications and changes can be made to the invention without departing from the spirit and scope of the invention. Accordingly, the present invention is intended to cover such modifications and variations of the invention

The accompanying drawings, which are included in the claims In the drawings: Figure 1 shows an example of a limit value for modifying a burst profile; Figure 2 shows an exemplary diagram of mapping AMC to a DIUC according to a code type; Figure 3 shows a Example Patterns of Encoding Type Mapping AMC to DIUC: Figure 4 shows an example of a method of applying a burst configuration file; and Figure 5 shows an example of a method of applying another burst configuration file.

Claims (10)

A method of supporting multiple coding types in a wireless mobile communication system, the method comprising the steps of: receiving, by a mobile station, a downlink channel descriptor (DCD) from a base station, wherein the DCD includes at least one of the following lines a burst burst profile, the at least one downlink burst profile including a type field of the at least one downlink burst profile, a downlink link usage code (DIUC) field And a type/length/value (TLV) encoded information field; wherein the at least one downlink burst configuration file, when the value of the type field is set to 153, includes an encoding type field for specifying a coding scheme, and the at least one downlink burst profile, when the value of the type field is set to 1, the coding type field is not included; and if the at least one downlink profile is configured The code type field is included, and the code type field is identified by the mobile station, wherein the code type field specifies an encoding scheme to be used by the base station to encode the at least one downlink link Hair profile Related to the downlink burst; wherein the coding scheme is at least one of a block acceleration code, a cyclotron acceleration code, a zero-tailed convolutional code, and a low-density parity code, wherein the DIUC is used for Designating one of the at least one downlink burst profiles for use by a particular burst of data, and a DIUC field for a mandatory wrap code, for values having a type field set to At least one of the downlink bundles Fixed file. The method of claim 1, wherein the TLV encoded information field includes a forward error correction coding type, a DIUC forced leaving limit, or a DIUC minimum entry limit. The method of claim 1, wherein the code of the at least one downlink burst profile is set when the value of the type field of the at least one downlink burst profile is set to 153 Type field that supports encoding types from multiple encoding classifications. The method of claim 1, wherein the at least one downlink burst profile is only used when the value of the type field of the at least one downlink burst profile is set to 153 The action station is in the DCD. The method of claim 1, wherein when the value of the type field of the at least one downlink burst profile is set to 153, the mobile station selects only the coding scheme maintained in the mobile station. A mobile station supporting multiple coding types in a wireless mobile communication system, the mobile station comprising: a receiver receiving a downlink channel descriptor (DCD) from a base station, wherein the DCD includes at least a downlink a burst profile, the at least one downlink burst profile including a type field of the at least one downlink burst profile, a downlink The interval use code (DIUC) field, and the type/length/value (TLV) coded information field; wherein the at least one downlink link burst profile, when the value of the type field is set to 153, includes one An encoding type field for specifying a coding scheme, and the at least one downlink burst configuration file, when the value of the type field is set to 1, the coding type field is not included; and a processor, If the encoding type field is included in the at least one downlink burst configuration file, the processor identifies the encoding type field, wherein the encoding type field specifies an encoding scheme to be used by the base station to Encoding a downlink burst associated with the at least one downlink burst profile; wherein the coding scheme is a block acceleration code, a cyclotron code, a zero-tailed convolutional code, and a low-density parity code At least one of the DIUCs is used to designate one of the at least one downlink burst profiles for use by a particular burst of data, and a DIUC field for a mandatory wraparound code , applicable to types with fields The value is set to 1 for at least the downlink burst configuration file. For example, the mobile station described in claim 6 wherein the TLV encoded information field includes a forward error correction coding type, a DIUC forced leaving limit, or a DIUC minimum entry limit. For example, the mobile station described in claim 6 wherein at least one When the value of the type field of the downlink burst profile is set to 153, the encoding type field of the at least one downlink burst profile supports the encoding type from the multiple encoding classification. The mobile station of claim 6, wherein when 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 only In the DCD of the mobile station. The mobile station of claim 6, wherein when the value of the type field of the at least one downlink burst profile is set to 153, the mobile station selects only the coding scheme maintained in the mobile station. .