MX2007012496A

MX2007012496A - Method of supporting multiple codes in a wireless mobile communication system.

Info

Publication number: MX2007012496A
Application number: MX2007012496A
Authority: MX
Inventors: Yong Suk Jin; Bin-Chul Ihm; Chang-Jae Lee; Ki-Seon Ryu
Original assignee: Lg Electronics Inc
Priority date: 2005-04-09
Filing date: 2006-02-28
Publication date: 2008-03-19
Also published as: CN101171877B; JP4955651B2; JP2008535439A; KR20060106540A; BRPI0612208A2; KR101084133B1; IL186479A; TW200642388A; IL186479A0; CN101171877A; TWI420868B

Abstract

A method of supporting multiple code types in a wireless mobile communication system is disclosed. More specifically, a mobile station (MS) receives a channel descriptor from a base station (BS), wherein the channel descriptor includes at least one burst profile which includes a code type and an interval usage code. Thereafter, the MS, first, recognizes the code type which includes information on coding scheme to be used by the BS or the MS, and recognizes, second, an interval usage code which is used for classifying all data bursts.

Description

METHOD OF SUPPORT OF MULTIPLE CODES IN A WIRELESS MOBILE COMMUNICATIONS SYSTEM Technical Field The present invention relates to a method of supporting code types, and more specifically, to a method of supporting multiple types of code in a wireless mobile communication system.

Prior art In a broadband wireless access system, an Orthogonal Frequeney Multiple Access Division (OFDMA, orthogonal frequency division multiple access) scheme is used to transmit data. When the OFDMA scheme is used, a structure of a frame is defined as follows. First, a low link frame represents 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 at the same time, for channel equalization in a physical layer. After the preamble, the frame includes a Downlink Map message (DL-MAP, Downlink Map) and a Uplink Map message (UL-MAP, link map of your life) which define the location and use of assigned bursts .

More specifically, the DL-MAP message defines the use of each burst assigned in the downlink section of the frame. In the same way, the UL-MAP message defines the use of the burst assigned in the link section of its life of the frame. An information element (IE), which is included in the DL-MAP, is classified in a downlink traffic section of a user group according to a Downlink Interval Usage Code (DIUC, Downlink Interval Use Code), a Connection Identification (CID, Identification of Connection) and the location of the burst signal (eg subchannel displacement, symbol offset, number of subchannels and symbol numbers).

The use of the IE of the UL-MAP is determined by means of a Uplink Interval Usage Code (UIUC, Code of Use of the Link Interval of your life), for each CID. Moreover, a corresponding location of a link traffic section of its life is defined by the duration, in this case, the use of each section is determined in accordance with the UIUC values used by the UL-MAP. A starting point of each section is moved by an amount of the duration set in the IE of the UL-MAP from the previous IE start point.

The MS receives a message from the Downlink Channel Descriptor (DCD, Downlink Channel Descriptor) and a Uplink Channel Descriptor (UCD, Upload Link Channel Descriptor) message for the network entry or to re-enter the network for the handover or for other reasons. A cell periodically provides the characteristics of the physical channel of the downlink and the uplink through the DCD / UCD message. In this case, the cell can also be used to represent a base station (BS).

The BS configures the Downlink_Burst_Profile based on the qualities of the signal received from each MS. In other words, the PS uses a Chanel Quality Information (CQI, Channel Quality Information) transmitted from the MS and configures the Downlink_Burst_Profile or an Adoptive Modulation and Coding (AMC, Modulation and Adoption Coding) according to the status of the channel of each MS. Otherwise as a support measure, the Downlink_Burst_Profile can be modified or changed using a Downlink Burst Profile Change request or response (DBPC, Downlink Burst Profile Change), ie DBPC-REQ / RSP) and procedures of reference request / response (RNG- REQ / RSP). Figure 1 is an example showing a threshold value for modifying the burst profile. The MS measures a Signal to Noise Ratio (SINR, Signal to Noise Ratio), for example, C / (N + 1) and compares an average value of allowed application range. The scope of the application is limited by a threshold level. That is, if the SNR exceeds the scope of application allowed, the MS uses a DBPC scheme to request a new burst profile. Based on whether the MS requests a more robust profile that has stronger interference (for example Quadrature Phase Shift Keying, Quadrature Phase Shift Modulation) or if the MS requests a less robust profile, which has less interference (eg 64 Quadrature) Amplitude Modulation, Quadrature Amplitude Modulation), the BS executes the transmission and reception of the message for the actual change of the modulation scheme. In this case the term "more robust" means that there is stronger interference, and the term "less robust" means that there is less interference.

According to the traditional technique, if there is a plurality of code types that can be supported by the MS within the scope of the services available by the BS, and if the link burst profiles of the Downlink / uplink are used to support various types of code, the intervals (or space) of the SNR that correspond to each AMC increases. Therefore, a modulation scheme that can be provided for one type of coding decreases. As a result, the ranges of the threshold values, which are used to change the AMC for each type of coding, increase, and consequently, there is a problem in properly applying the AMC according to the status of the channel.

Disclosure of the Invention Accordingly, the present invention is directed to a method of supporting multiple types of code in a wireless mobile communication system that substantially eliminates one or more problems due to the limitations and disadvantages of the related art.

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

Advantages, objectives and additional features of the invention will be set forth in part in the following description and in part will be evident to those who have Ordinary skills in the technique after examination of the following or can be learned from the practice of the invention. The objects and other advantages of the invention can be realized and achieved by the structure particularly indicated in the written description and the claims as well as the attached drawings.

To achieve these objectives and other advantages and in accordance with the purpose of the invention, as widely incorporated and described herein, a method of supporting multiple types of code in a wireless mobile communication system includes a mobile station (MS) which receives a channel descriptor from a base station (BS) wherein the channel descriptor includes at least one burst profile that includes a code type and an interval usage code. Then, the MS, first, recognizes the type of code which includes information about the coding scheme to be used by the BS or the MS, and recognizes, second, a use code of the interval which is used to classify all bursts of data.

In another aspect of the present invention, the MS receives a downlink channel (DCD) descriptor from a station (BS), where the DCD includes at least one burst profile. After receipt, the MS recognizes the type of code that includes information about the coding scheme to be used by the BS and an interval usage code that is used to classify all bursts of data.

However, in another aspect of the present invention, the MS receives a upload link channel descriptor (UCD) from the mobile station (MS), wherein the UCD includes at least one burst profile. Upon receipt, the MS recognizes a type of code that includes information about the coding scheme to be used by the BS and a range use code that is used to classify all bursts of data.

In another aspect of the present invention, the MS receives a channel descriptor from a base station (BS), wherein the channel descriptor includes at least a series of burst profiles that includes a plurality of burst profiles that also includes an interval usage code and at least one type of code. Next, the MS recognizes, first, the at least one type of code that includes information about the coding schemes to be used by the BS or the MS, and recognizes, second, an interval usage code which is used to classify all bursts of data.

It will be understood that the aforementioned general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide another explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included to provide more understanding of the invention and are incorporated into and constitute a part of this application, the illustrated embodiment or modalities of the invention and together with the description serve to explain the principle of the invention. In the drawings: FIGURE 1 is an example demonstrating a threshold value for modifying the burst profile; FIGURE 2 is an exemplary diagram showing the mapping of the AMC for a DIUC according to a type of coding; FIGURE 3 is an exemplary diagram illustrating mapping of the AMC for DIUC according to a type of coding; FIGURE 4 illustrates an example of a method of applying the burst profile; Y FIGURE 5 demonstrates an example of a method of applying another burst profile.

BEST MODE FOR CARRYING OUT THE INVENTION Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. When possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts.

Table 1 is an example of the DCD message.

Table 1 Table 2 is an example of the UCD message.

Table 2 The DCD / UCD messages each include parameters of the physical layer for the burst interval assigned to the upload link and download link. As examples of the parameters of the physical layer, there is a type of modulation and Forward Error Correction code types (FEC, Progress Error Correction). In addition, the parameters for the FEC code types can be represented by, for example, KIR values of a Reed-Solomon (RS) code.

The parameters are mapped for the DIUC included in a Downlink_Burst_Profile of the DCD message and the UIUC included a Uplink_Burst_Profile of the UCD message. That is, the Downlink_Burst_Profile information, which is included in the DCD message, can use the DIUC to define certain characteristics of the physical layer that is used in a specific downlink burst.

Table 3 is an example of a TLV Downlink_Burst_Profile format.

Table 3 As shown in Table 3, the downlink burst profile includes a DIUC having a length of 4 bits, since the DIUC has a length of 4 digits, 16 different information (for example, coding and modulation schemes). ) can be represented. In addition, the BS or the cell can select and assign 13 burst profiles on the DIUC0-DIUC12, and the FEC type can be mapped for each DIUC. Then, the BS announces the burst profiles selected through the DCD / UCD messages.

In another version, the burst profile of the upload link included in the UCD message may use the UIUC to define some characteristics of the physical layer that is used in a specific upload link burst.

Table 4 is an example of a Uplink Burst Profile TLV format.

Table 4 As shown in Table 4, the upload link burst profile includes a UIUC that is 4 bits long. Since the UIUC has a length of 4 bits, it is possible to represent 16 different information (for example coding and modulation schemes). Furthermore, the BS or the cell can select and assign 10 burst profiles on UIUC0-UIUC10, and the FEC type can be mapped for each UIUC. Then, the BS announces the selected burst profiles through the DCD / UCD messages. Tables 5 and 6 are examples of downlink burst profiles in the Type, Length, Value (TLV) format.

Table 5 Table 6 Table 7 is an example of upload link burst profiles in the Type, Length, Value (TLV) format.

Table 7 By using Table 3, the BS maps the FEC code types to 13 DIUCs (ie, DIUC0-DIUC12) to configure the downlink burst profile. The mapping procedure includes negotiating the types of coding available through the MS using a request and response procedure of the Subscriber Station Basic Capability (SBC-REQ / RSP, Request and Response of the Basic Capacity of the Subscriber's station). Tables 8 and 9 are examples of modulation and demodulation schemes that can be supported by the MS.

Table 8 Table 9 With respect to FEC code types, there is, to name a few, a Convolutional Code (CC, convolutional code), a Block Turbo Coding (BTC, Turbo Block Coding), a Convolutional Turbo Code (CTC, Convolutional Turbo Code), a Zero Tail Convolution Code (ZTTC, Zero Tail Convolutional Code) and Low Density Parity (LDPC, Low Density Parity Code). Among these types of FEC, CC is considered mandatory while the other types are optional.

During operation, the BS always uses CC since it is mandatory. Furthermore, since the DIUC can be mapped to 16 different pieces of information, CC maps to a maximum of 6 DIUC values (eg DIUC0-DIUC5), and the remaining 6 values are mapped to choice by any of the BTC, CTC, ZTTC and LDPC.

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

As an embodiment of the present invention, a method of generating a Burster Profile is introduced, the detail of which is as follows. First, each of the threshold values, represented in a TLV format, is mapped one by one for each value DIUC / UIUC. The number of mapped values is equal to the number of DIUC / UIUC that has to be configured. In this case, the threshold value is based on the type of FEC code and the request for modification (or change) of the burst profile. In addition, the burst profile includes information related to the type of burst profile coding.

Table 10 is an example illustrating a downlink burst profile.

Table 10 Table 11 is an example illustrating a rise link burst profile.

Table 11 Figure 2 is an exemplary diagram showing AMC mapping for a DIUC according to a type of coding. From the different types of coding available, the BS uses CC as default or put another way, CC type is always used (that is, mandatory CC). As such, the DIUC for the mandatory CC can be mentioned as Downlink_Burst_Profile with type = 1. As shown in Figure 2, the mandatory CC is mapped or assigned for DIUC0-DIUC5 and UIUC0-DIUC6 (21). That is, as shown in Table 10, for example, the "Coding Type" field can be set to? 001, which represents mandatory CC and the AMC can be mapped for each of the 6 DIUCs / UIUC.

In addition, to assign different coding types for the remaining DIUCs, the BS assigns different coding types for DIUC6-DIUC12. In this case, the coding type (s) assigned for DIUC6-DIUC12 are different from the type of coding (ie, CC) assigned for DIUC0-DIUC5. For example, if the BS decides to use BTC in addition to the mandatory CC, the? Coding Type 'field is set to ^ 010', which represents BTC as indicated in table 10, and the AMC is mapped for DIUC6-DIUC12 (22) .

Otherwise, if the BS supports CTC or LDPC, the xCoding Type Set field can be set to? 011 'or 101', respectively, and the AMC is mapped for each series of DIUC6-DIUC12 (23, 24).

Table 12 is another example of a downlink bursts profile.

Table 12 Table 13 is another example of a rise link burst profile.

Table 13 Figure 3 is an exemplary diagram illustrating mapping of the AMC for DIUC according to a type of coding. As illustrated in Figure 3, a combination of each type of coding can be used to configure a burst profile. Of many types of coding, the BS assigns the mandatory CC. As such, the BS configures a 'Code Type Set' field according to the types of coding that the BS additionally supports. For example, if the BS supports BTC in addition to, of course, the mandatory CC, the field "Code Type Set" is set to? 001. According to this setting, the mandatory CC is assigned for DIUC0-DIUC5 and UIUC1-DIUC6 while BTC is assigned for DIUC6-DIUC12 (31).

In another version, if the BS supports CTC in addition to the mandatory CC, the field "Code Type Set" is set to 010 '.

The mandatory CC is assigned for DIUC0-DIUC5 and UIUC1-DIUC6 while CTC is assigned for DIUC6-DIUC12 (32).

In another version, if the BS supports LDPC in addition to the mandatory CC, the field "Code Type Set" is set to? 100, the mandatory CC is assigned for DIUC0-DIUC5 and UIUC1-DIUC6 while LDPC is assigned for DIUC6-DIUC12 (33).

Figure 4 shows an example of a method of application of the burst profile. As shown in Figure 4, the MS receives the burst profile, generated based on each type of coding, through the DCD / UCD message (S41). Then, the MS and the BS use the SBC-REQ / RSP process to negotiate the types of coding that can be supported respectively (S42, S43). After receiving the SBC-RSP message from the BS, the MS interprets the value DIUC corresponding to the "Coding Type" (type of coding) or the "Code Type Set" (series of coding types) that can be supported by the MS.

After receiving the burst profile, through the DCD / UCD message and negotiating with the BS the types of coding that can be supported, if the type of coding is determined (for example the LDPC type), then the AMC, which represents the types CC and LDPC, is applied to the specific burst assigned to the MS, and the MS receives the downlink signal based on the AMC (S44).

In another version, it is possible to use the IE (information element) of the DL-MAP / UL-MAp to provide the MS, currently using a specific type of coding, with a new type of coding. When a new type of coding is added through the extended DIUC / UIUC, a new FEC code can be provided to all the MCs through the extended DIUC.

Figure 5 shows an example of an application method of another burst profile. As shown in Figure 5, the MS supports a predetermined encoding type and two newly added enhanced encoding types. The MS uses the SBC-REQ message to support the types of encoding that can be supported by the MS (S51). In response, the BS uses the SBC-RSP message to notify the MS of which types of newly added enhanced coding the BS intends to support (S52). To apply DIUC / UIUC, the MS recognizes the DIUC / UIUC values of the burst profile included in the DCD transmitted by the BS with the coding type assigned by the BS.

As shown in Figure 5, the MS uses at least one of the CC, CTC and LDPC coding types. For example, if the MS uses mandatory CC and at the same time can support CTC and LDPC, the MS reports the availability of these two types of coding (for example CTC or LDPC) for the BS through the SBC-REQ message. Upon receipt, the BS selects one of the two types of encoding (ie, LDPC) and transmits the selection through the SBC-RSP message for the MS. Then, the MS, recognizes the DIUC / UIUC values according to the LDPC.

In addition, a 'Type' field included in the DCD / UCD can be used to distinguish the types of information needed for the MS. For example, as shown in Tables 3 and 4, the Type 'field is set to l'. Conventionally, the "Type" field is used to determine the burst profile. As described above, the burst profile includes the use of at least one type of encoding, including a default encoding type, while setting the field? Type 'to l'. Moreover, the burst profile using a new type of coding can be used to notify a new type of coding.

Table 14 is another example showing a downlink bursts profile. In this case, Table 14 defines the Downlink_Burst_Profile format with Type = 153, which is used in the DCD message for the MS only. The DIUC field is associated with the Downlink_Burst_Profile and the thresholds. The value DIUC is used in the DL-MAP message to specify the burst profile to be used for a specific downlink burst.

Table 14 As when the 'Type' field is set to '1', in this case, the 'Type' field is set to '153' in the burst profile. The MS uses the burst profile that the 'Type' field set to '1' has to learn (or receive information) from the AMC level mapping of at least one type of coding (ie, CC). If the MS receives the burst profile having the 'Type' set to '153', the MS can only select the type or coding types retained by the MS.

Table 15 is another example of a rise link burst profile.

Table 15 Table 16 is an example that illustrates the values of a UCD.

Table 16 Table 17 is an example that shows the values included in a DCD.

Table 17 As shown in Tables 16 and 17, the value of the 'Type' field included in the DCD or UCD can be interpreted. Moreover, when the value of the 'Type' field is defined, in addition to the burst profile that indicates the value of the 'Type' field is set to '1', the DCD / UCD can be used to indicate the existence of a new profile of bursts.

It will be apparent to those skilled in the art that various modifications and variations may be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is proposed that the present invention cover the modifications and variations of this invention as long as they fall within the scope of the appended claims and their equivalents.

Claims

1. A method of supporting multiple types of code in a wireless mobile communication system, the method consists in: receiving a channel descriptor from a base station (BS), wherein the descriptor of the channel includes at least one burst profile that includes a type of code and an interval usage code; recognizing, first, the type of code that includes information about the coding scheme to be used by the BS or a mobile station (MS); and recognize, second, an interval usage code which is used to classify all bursts of data.

2. The method of claim 1, characterized in that the descriptor of the channel is a Downlink chanel Descriptor (DCD, downlink channel descriptor).

3. The method of claim 2, characterized in that the DCD includes a Downlink Interval Usage Code (DIUC, Downlink Interval Use Code).

4. The method of claim 1, characterized in that the channel descriptor is an uplink Chanel Descriptor (UCD, Descriptor of the Upload Link Channel).

5. The method of claim 4, characterized in that the UCD includes a Uplink Interval Usage Code (UIUC, Submission Link Interval Use Code).

6. The method of claim 1, characterized in that the type of code is a type of Forward Error Correction code (FEC, Progress Error Correction).

7. The method of claim 6, characterized in that the FEC code type includes at least one of the following: Convolutional Coding (CC), Block Turbo Coding (BTC), Convolutional Turbo Code (CTC), Zero Tail Convolution Code (ZTTC) , and Low Density Parity Code (LDPC).

8. The method of claim 1, characterized in that the interval usage code is a Downlink Interval Usage Code (DIUC, Downlink Interval Use Code).

9. The method of claim 1, characterized in that the interval usage code is a Uplink Interval Usage Code (UIUC, Use Code of Upload Link Interval).

10. The method of claim 1, characterized in that the at least one burst profile is classified into at least two groups, a first group that includes the interval usage codes and the code types that have more than one coding scheme , and a second group includes the interval usage codes and a unique code type.

11. The method of claim 1 further comprises a third group that includes the interval usage codes and a unique code type, wherein the unique code of the third group is different from the unique code of the second group.

12. A method of supporting multiple types of code in a wireless mobile communication system, the method consists of: receiving a downlink channel (DCD) descriptor from a base station (BS), wherein the DCD includes at least a profile of gusts; recognize a type of code that includes information about the coding scheme that is to be used by the BS; and recognizing an interval usage code which is used to classify all bursts of data.

13. The method of claim 12, characterized in that the burst profile includes a downlink interval (DIUC) usage code.

14. The method of claim 12, characterized in that the burst profile includes a type of code.

15. The method of claim 12, characterized in that the type of code is a type of code Forward Error Correction (FEC, forward error correction).

16. The method of claim 15, characterized in that the FEC code type includes at least one of: Convolutional Coding (CC), Block Turbo Coding (BTC), Convolutional Turbo Code (CTC), Zero Tail Convolution Code (ZTTC), and Low Density Parity Code (LDPC).

A method of supporting multiple types of code in a wireless mobile communication system, the method consists of: receiving a upload link channel descriptor (UCD) from a mobile station (MS), wherein the UCD includes at least minus a burst profile; recognize a type of code that includes information about the coding scheme that is to be used by the BS; and recognizing an interval usage code which is used to classify all bursts of data.

18. The method of claim 17, characterized in that the burst profile includes a downlink interval (DIUC) usage code.

The method of claim 17, characterized in that the burst profile includes a type of code.

20. The method of claim 17, characterized in that the type of code is a type of Forward Error Correction code (FEC, Progress Error Correction).

21. The method of claim 20, characterized in that the FEC code type includes at least one of Convolutional Coding (CC), Block Turbo Coding (BTC), Convolutional Turbo Code (CTC), Zero Tail Convolution Code (ZTTC), and Low Density Parity Code (LDPC).

22. A method of supporting multiple types of code in a wireless mobile communication system, the method consists of: receiving a channel descriptor from a base station (BS), wherein the descriptor of the channel includes at least a series of profiles of bursts including a plurality of burst profiles which further include an interval usage code and at least one type of code; recognizing, first, the at least one type of code which includes information on coding schemes to be used by the BS or a mobile station (MS); and recognize, second, an interval usage code which is used to classify all bursts of data.

23. The method of claim 22, characterized in that a first group includes all available types of code.

24. The method of claim 23, characterized in that a second group or a third group each includes a type of code.

25. The method of claim 24, characterized in that a specified code type, included in the first group, is shared by all the groups.

26. The method of claim 25, characterized in that the type of code is a type of Forward Error Correction code (FEC, Progress Error Correction).