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

Abstract

MULTIPLE CODE SUPPORT METHOD IN A WIRELESS MOBILE COMMUNICATION SYSTEM. A method of supporting multiple code types in a wireless mobile communication system is described. More specifically, a mobile station (EM) receives a channel descriptor from a base station (EB), wherein the channel descriptor comprises at least one data overflow profile which includes a code type and a code usage code. interval. Thereafter, MS first recognizes the type of code that includes the information about the coding scheme to be used by EB or MS, and then recognizes a range usage code that is used to classify all. Data overflows.

Description

"MULTI-CODE SUPPORT METHOD IN A WIRELESS MOBILE COMMUNICATION UMSYSTEM"

The present invention relates to a code type support method, and more particularly to a multiple code type support method in a wireless mobile communication system.

State of art

In a broadband wireless access system, an Orthogonal Frequency Division Multiple Access (AMDFO) scheme is used to transmit data. When the AMDFO scheme is used, a frame structure is defined as follows. First, a data download frame represents a preamble at the beginning of the frame that can be used for time synchronization between a mobile station (EM) and a base station (EB). ), and at the same time, for channel equalization in a physical layer. Following the preamble, the table includes a Data Download Map (MAPA-DD) message and a Data Load Map (MAPA-CD) message that defines the location and use of allocated data overflows.

More specifically, the MAP-DD message defines the use of each overflow allocated in the data offload section of the frame. Similarly, the MAP-CD message defines the use of the overflow allocated in the data load section of the frame. An Information Element (EI), which is included in MAPA-DD, is classified into a user group's data download traffic section according to a Data Download Interval Usage Code (CUID), a Connection (IC), and the location of the data overflow signal (for example, subchannel compensation, symbol compensation, number of subchannels, and number of symbols).

MAPA-CD EI usage is determined by a Data Load Interval Use Code (CUIC) for each IC. In addition, a corresponding location of a data load traffic section is defined by duration. Here, the use of each section is determined according to the CUIC values used by MAPA-CD. A start point of each section is compensated by an amount of the duration set in the ΜΔΡΑ-CD EI from the previous EI start point.

The MS receives a DataDiscal Channel Descriptor (DCD) message and a DataDiscal Channel Descriptor (DCC) message to enter the network or re-enter the network due to a connection transient or other reasons. A cell periodically provides the physical channel characteristics of data offloading and loading by the DCD / DCC message. Here, the cell can also be used to represent a base station (EB).

The EB configures the Burst_Dump Profile based on the signal qualities received from each MS. In other words, EB uses a Channel Quality Information (IQC) transmitted from each MS and sets the Burst_Discharge Profile or an Adoptive Modulation (MCA) according to the channel state of each MS.

Alternatively, as a support measure, Burst_DischargeProfile can be modified or changed by using a Download Burst Profile Change (MPED) request or response, that is, MPED-REQ / RSP and Comprehensive Requests / Response (ABR-REQ / RSP) procedures. ).

Figure 1 is an example illustrating a bound value for modifying the overflow profile. MS measures a Signal to Noise Ratio (RSR), for example, C / (N + 1), and compares an allowable application scope mean value. The scope of application is limited by a threshold level. That is, if RSR exceeds the allowed application scope, EM uses an MPED scheme to request a new data overflow profile. Based on whether EM requires a stronger profile having stronger interference (eg Quadrature Phase Shift Switching

Quadrature Phase Shift Keying (QPSK) or if EM requires a less robust profile with less interference (eg Quadrature Amplitude Modulation 64 - QAM), EB performs transmission and reception of the message for a current change. of the modulation scheme. Here the term 'more robust' means there is stronger interference, and the term 'less robust' means less interference. According to the conventional state of the art, there are a plurality of code types that can be supported by MS within the scope. available from EB, and if the data download / upload overflow profiles are used to support various types of code, the RSR ranges (or spaces) corresponding to each MCA increase. Therefore, a modulation scheme that can be provided for a decoding type decreases. As a result, the range of the boundary values used to change the MCA for each type of encoding increases, and therefore there is a problem in properly applying MCA according to channel state.

Description of the Invention

Suitably, the present invention is directed to a method of supporting multiple code types in a mobile wireless communication system that substantially obviates one or more problems due to the limitations and disadvantages of the state of the arterelate. An object of the present invention is to provide a method of supporting multiple code types in a wireless mobile communication system.

Additional advantages, objectives, and features of the invention will be seen in part in the following description and in part will be apparent to those having common skills in the art under consideration, or may be learned from the practice of the invention. The objects and other advantages of the invention may be realized and attained by the structure particularly set forth in the written description and claims as well as in the accompanying drawings.

In order to achieve these objectives and other advantages according to the purpose of the invention, as fully incorporated herein, a method of supporting multiple code types in a wireless mobile communication system comprises a mobile station (EM) receiving a channel descriptor from a base station. (EB), wherein the channel descriptor includes at least one data overflow profile that includes a code type and a range usage code. Thereafter, EM first recognizes the type of code that includes the coding scheme information to be used by EB or EM, and then recognizes a range usage code that is used to classify all data overflows. .

In another aspect of the present invention, EM receives a data download channel descriptor (DCD) from a base station (EB), wherein the DCD includes at least one data overflow profile. Upon receipt, EM recognizes a decode type that includes information about a coding scheme to be used by EB and a range usage code that is used to classify all data overflows.

In yet another aspect of the present invention, the EM receives a data loading channel (DCC) descriptor from a mobile station (EM), wherein the DCC includes at least one data overflow profile. Upon receipt, EM recognizes a decode type that includes information about a coding scheme to be used by EB and a range usage code that is used to classify all data overflows.

In a further aspect of the present invention, EM receives a channel descriptor from a base station (EB), wherein the channel descriptor includes at least one data burst profile set that includes a plurality of burst profiles in addition to a usage code. range and at least one type of code. After that, MS first recognizes at least one type of code that includes information about a coding scheme to be used by EB or MS, and then recognizes a range usage code that is used to classify all overflows. of data.

It will be understood that the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanations of the invention as claimed.

Brief Description of the Drawings

The accompanying drawings are included to provide a better understanding of the invention and are incorporated herein as a part of this application, illustrating embodiments of the invention and together with the description serving to explain the principle of the invention. In the drawings: Fig. 1 is an example illustrating a delimit value for modifying the overflow profile;

Fig. 2 is an exemplary diagram illustrating the mapping of MCA to a CUID according to a decoding type;

Fig. 3 is an exemplary diagram illustrating MCA to CUID mapping according to a decoding type;

Fig. 4 illustrates an example of a method of applying a data overflow profile; and

Fig. 5 illustrates an example of a method of applying another data overflow profile.

Best Mode for Carrying Out the Invention

Reference will now be made in detail to preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Where possible, the same reference numerals will be used in the drawings to refer to the same or equal parts.

Table 1 is an example of the DCD message. [Table 1]

<table> table see original document page 6 </column> </row> <table>

Table 2 is an example of the DCC message. [Table 2]

<table> table see original document page 7 </column> </row> <table>

DCD / DCC messages each include physical layer parameters for an allocated data unload and overflow interval. As examples of the physical layer parameters, there are a modulation type and Error Correction Ahead (CEA) code types. In addition, the parameters for CEA code types can be represented by, for example, K and R values from a Reed-Solomon (RS) code.

Parameters are mapped to the CUID included in a DCC Message Burst_Profile Profile and the CUIC is included in a DCC Message Burst_Profile Profile.

That is, Profile_Dump_Dump information, which is included in the DCD message, can use the CUID to define certain physical layer characteristics used in a specific dataDump overflow.

Table 3 is an example of a Download_Profile Overflow VCT format. [Table 3]

<table> table see original document page 8 </column> </row> <table>

As shown in table 3, the offload overflow profile includes a CUID having a length of 4 bits. Because the CUID is 4 bits long, 16 different information (eg coding and modulation schemes) can be represented. In addition, the EB or cell can select and allocate 13 overflow profiles in CUIDO - CUID12, and the CEA type can be mapped to each CUID. After that, EB announces the selected burst profiles through the DCD / DCC messages.

Alternatively, the data-load overflow profile included in the DCC message can use CUIC to define certain physical layer characteristics used in a specific data load bin.

Table 4 is an example of an Overload_ProfileProfile VCT format.

[table 4]

<table> table see original document page 8 </column> </row> <table>

As shown in table 4, the data load overflow profile includes a CUIC having a 4-bit length. Since CUIC has a length of 4 bits, 16 different information (for example, coding schemes and modulation) can be represented. In addition, the EB or cell can select and allocate 10 burst profiles in CUICO - CUIC10, and the type of CEA can be mapped to each CUIC. After that, EB announces the selected burst profiles through the DCD / DCC messages. Tables 5 and 6 are examples of Data Discharge Overflow (VCT) profiles of Type, Length, andValue.

[Table 5]

<table> table see original document page 9 </column> </row> <table> [Table 6]

<table> table see original document page 9 </column> </row> <table>

Table 7 is an example of Type, Length, and eValue format data load overflow (VCT) profiles.

[Table 7]

<table> table see original document page 10 </column> </row> <table> <table> table see original document page 11 </column> </row> <table>

Using table 3, EB maps CEA code types to 13 CUIDs (that is, CAUTION - CUID12) to configure the data offload overflow operfil. The mapping procedure includes negotiating the coding types available by EM using a Subscriber Station Basic Capacity (CBE-REQ / RSP) request and response procedure. Tables 8 and 9 are examples of modulation and demodulation schemes that may be supported by EM.

[table 8]

<table> table see original document page 11 </column> </row> <table> <table> table see original document page 12 </column> </row> <table>

With respect to CEA code types there are, to name but a few, a Convolutional Code (CC), a Block Turbo Code (TCB), a Convolutional Turbo Code (TCC), a Final Zero Convolution Code (CCFZ) , and a Low Density Parity Code (CPBD). Among these CEA types, CC is considered mandatory, while the other types are optional.

In operation, EB always uses CC since it is mandatory. In addition, since CUID can be mapped to 16 different information, CC is mapped to a maximum of 6 CUID values (for example, CUIDO - CUID5), and the remaining 6 values are selectively mapped by any TCB, TCC, CCFZ, or CPBD. .

Even in the case of CUIC, the required CC is mapped to a maximum of 6 values (for example, CUICO - CUIC5) while the remaining 6 values are selectively mapped by anyTCB, TCC, CCFZ, or CPBD.

As an embodiment of the present invention, a method for generating a Data Overflow Profile is presented, its details being as follows. First, each of the threshold values, represented in a VCT format, is mapped on a one-to-one basis for each CUID / CUIC value. The number of mapped values is equal to the number of CUID / CUIC to be set. Here, the threshold value is based on the CEA code type and the override profile modification (or change) request. In addition, the overflow profile includes information related to the encoding type of the overflow profile.

Table 10 is an example illustrating a data download overflow profile.

[table 10]

<table> table see original document page 12 </column> </row> <table> <table> table see original document page 13 </column> </row> <table>

Table 11 is an example illustrating a data load overflow profile.

[table 11]

<table> table see original document page 13 </column> </row> <table>

Figure 2 is an exemplary diagram illustrating the mapping of MCA to a CUID according to a decoding type. Among the various types of coding available, EBusa CC as default code or, on the other hand, the CC type is always used (ie CC is required). As such, the CUID for the mandatory CC can be referred to as a Burst_ProfileProfile with type = 1. As shown in Figure 2, the mandatory CC is mapped or allocated to CUIDO - CUID5e CUICO - CUIC6 (21). That is, as shown in table 10, for example, the 1 Encoding Type 'field can be set to 1001', which represents the required CC, and the MCA can be mapped to every 6 CUID / CUICs.

In addition to allocating encoding types other than the remaining CUIDs, EB allocates different encoding types for CUID6 - CUID12. Here, the encoding type (s) allocated for CUID6 - CUID12 are different from the decoding (ie CC) type allocated for CUIDO - CUID5. For example, if EB decides to use TCB in addition to the required CC, the 'Encode Tip' field is set to '010', which represents TCB as indicated in table 10, and the MCA is mapped to CUID6 - CUID12 (22). Alternatively, if EB supports TCC or CPBD, the 'Encoding Type' field can be set to '011' or '101', respectively, and the MCA is mapped to each set of CUID6 -CUID12 (23,24).

Table 12 is another example of a data download overflow profile.

[table 12]

<table> table see original document page 14 </column> </row> <table>

Table 13 is another example of a data load overflow profile. [Table 13] <table> table see original document page 15 </column> </row> <table>

Figure 3 is an exemplary diagram illustrating the mapping of MCA to CUID according to a decoding type. As shown in Figure 3, a combination of each encoding type can be used to set up an overflow profile. Among many types of coding, EB allocates the CC. As such, EB configures a 'Code Type Setting' field according to code types supported by EBadditionally. For example, if EB supports TCB in addition to CC, which is obviously required, the 'Code Type Setting' field is set to λ001 '. Under this configuration, the CC is assigned to CUIDO - CUID5 and CUICl - CUIC6 while TCB is allocated to CUID6 - CUID12 (31).

Alternatively, if EB supports TCC beyond CC, the 'Code Type Setting1' field is set to Λ010 ', the required CC is allocated to CUIDO -CUID5 and CUICl - CUIC6 while TCC is allocated to CUID6 - CUID12 (32) .

Alternatively, if EB supports CPBD in addition to CC, the Code Type Setting field 'is set to' 100 ', the required CC is allocated to CUIDO -CUID5 and CUICl - CUIC6 while CPBD is allocated to CUID6 - CUID12 (33) Figure 4 illustrates an example of a method for applying an overflow profile. As illustrated in Figure 4, EM receives the generated burst profile based on each decoding type by the DCD / DCC message (S41). After that, EM and EB use the CBE-REQ / RSP process to negotiate decoding types that can be respectively supported (S42, S43). After receiving EB's CBE-RSP message, EM interprets the CUID value. which corresponds to 'Encoding Type' or 'Code Type Setting1' that can be supported by EM.

After receiving the DCD / DCC message Overflow Profile and negotiating with EB the encoding types that can be supported, if the encoding type is determined (eg CPBD type), then the MCA, representing CC and CPBD types, is applied to the specific data overflow allocated to MS, and MS receives the data download signal based on the MCA (S44).

Alternatively, you can use the MAPA-DD / MAPA-CD EI to provide MS, currently using a specific decoding type, with a new encoding type. When a new encoding type is added by extended CUID / CUIC, a new CEA code type can be provided to all EMs by the expanded CUU.

Figure 5 illustrates an example of a method for applying another data overflow profile. As shown in Figure 5, EM supports one default encoding type and two newly added encoding types. AEM uses the CBE-REQ message to inform the encoding types that may be supported by EM (S51). In response, EB uses CBE-RSP messaging to notify MS about which recently added enhanced decoding types EB wants to support (S52). To apply CUID / CUIC, EM recognizes the CUID / CUIC values of the data overflow profile included in the EB transmitted DCD with the encoding type allocated by EB.

As illustrated in Figure 5, MS uses at least one of the CC, TCC, and CPBD encoding types. For example, if MS uses mandatory CC and at the same time TCC and CPBD may be supported, MS reports the availability of these two encoding types (for example, TCC or CPBD) to EB by the CBE-REQ message. On reception, the EB selects one of two decoding types (ie CPBD) and transmits the selection by the message fromCBE-RSP to the MS. After that, MS recognizes the CUID / CUIC values according to the CPBD.

In addition, a 'Type' field included in DCD / DCC can be used to distinguish the types of information required for MS. For example, as illustrated in tables3 and 4, the field of 1Type1 is set to '1'. Conventionally, the 1Type 'field is used to determine the data overflow profile. As described above, the overflow profile includes using at least one encoding type, including a default encoding type, while setting the field from 1Type to '1'. In addition, the overflow profile using a new decoding type can be used to notify about a new decoding type.

Table 14 is another example illustrating a data download overflow profile. Here, table 14 defines the Format of the Burst_Discharge Profile with Type = 153, which is only used in the DCD message for MS. The CUID field is associated with the Burst_Dump Profile and Thresholds. The CUID value is used in the MAP-DD message to specify data overflow operation to be used for a specific data discharge overflow.

[table 14]

<table> table see original document page 17 </column> </row> <table> Similar to when the ΛΤίρο 'field is set to' 1 ', here the' Type 'field is set to' 153'in the profile overflow. EM uses the overflow profile having the 'Type' field set to 'I1 to learn (or receive information) from MCA level mapping of at least one decoding type (ie CC). If MS receives the burst profile with 'Type1 set to' 153 ', MS can only select the type (s) of coding retained by MS.

Table 15 is another example of a data load overflow profile.

[table 15]

<table> table see original document page 18 </column> </row> <table>

Table 16 is an example illustrating the values of a DCC.

[table 16]

<table> table see original document page 18 </column> </row> <table> <table> table see original document page 19 </column> </row> <table>

Table 17 is an example illustrating the values included in a DCD.

[table 17]

<table> table see original document page 19 </column> </row> <table>

As illustrated in Tables 16 and 17, the field xType 'included in the DCD or DCC can be interpreted. In addition, when the value of the' Type 'field is set, in addition to the Overflow Profile indicating the value of the field of λΤίρο' set to 1I ', DCD / DCC can be used to indicate the existence of a new Data Overflow Profile.

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 invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided within the scope of the appended claims and their equivalents.

Claims (26)

1. "MULTI-CODE SUPPORT METHOD IN A MOBILE WIRELESS COMMUNICATION SYSTEM", characterized in that it comprises: receiving a channel descriptor from a base station (EB), wherein the channel descriptor comprises at least one data burst profile which includes a code type and an interval goddess code: first recognizing the code type which includes information about the coding scheme to be used by EB or a mobile station (EM); and then recognize an interval usage code that is used to classify all data overflows. "Method" according to claim 1, characterized in that the channel descriptor is a Data Download Channel Descriptor (DCD). "Method" according to claim 2, characterized in that the DCD includes a Data Download Interval Usage Code (CUID). "Method" according to claim 1, characterized in that the channel descriptor is a Data Load Channel Descriptor (DCC). "Method" according to claim 4, characterized in that the DCC includes a Data Load Interval Use Code (CUIC). "Method" according to claim 1, characterized in that the code type is a forward error correction (CEA) code type. 7. "METHOD" according to claim 6, characterized in that the CEA code type includes at least one Convolutional Coding (CC), a Block Turbo Code (TCB), a Convolutional Turbo Code (TCC) ), a Zero End Conflict Code (CCFZ), and a Low Density Parity Code (CPBD). 8 "METHOD" according to claim 1, characterized in that the interval usage code is a Data Offload Interval Use Code (CUID). "Method" according to claim 1, characterized in that the interval usage code is a Data Load Interval Use Code (CUIC). "Method" according to claim 1, characterized in that at least one data overflow profile is classified into at least two groups, where a first group includes interval usage codes and coding types having more than one. a coding scheme, and a second group included range usage codes and a single code type. "Method" according to claim 10, characterized in that it comprises a third group including interval use codes and a single code type, wherein the unique code of the third group is different from the unique code of the second group. 12. "MULTI-CODE SUPPORT METHOD IN A WIRELESS MOBILE COMMUNICATION SYSTEM", characterized by the fact that it comprises: receiving a data channel download descriptor (DCD) from a base station (EB), wherein the DCD includes at least one profile data overflow; recognize a code type that includes information about the coding scheme to be used by EB; and recognize a range usage code that is used to classify all data overflows. "Method" according to Claim 12, characterized in that the overflow profile includes a data offload interval (CUID) usage code. "Method" according to claim 12, characterized in that the overflow profile includes a code type. "Method" according to claim 12, characterized in that the code type is a forward error correction (CEA) code type. 16. "METHOD" according to claim 15, characterized in that the CEA code type includes at least one Convolutional Coding (CC), a Block Turbo Code (TCB), a Convolutional Turbo Code (TCC) ), a Zero End Conflict Code (CCFZ), and a Low Density Parity Code (CPBD). 17. "MULTI-CODE SUPPORT METHOD IN A MOBILE WIRELESS COMMUNICATION", characterized by the fact that it comprises: receiving a mobile station (EM) data channel descriptor (DCC), in which the DCC includes at least one profile data overflow; recognizing a type of code that includes information about a coding scheme to be used by EB; and recognize a range usage code that is used to classify all data overflows. "Method" according to claim 17, characterized in that the overflow profile includes a data offload interval (CUID) usage code. "Method" according to claim 17, characterized in that the overflow profile includes a code type. "Method" according to claim 17, characterized in that the code type is a forward error correction (CEA) code type. 21. "METHOD" according to claim 20, characterized in that the CEA code type includes at least one Convolutional Coding (CC), a Block Turbo Code (TCB), a Convolutional Turbo Code (TCC) ), a Zero End Conflict Code (CCFZ), and a Low Density Parity Code (CPBD). 22. "WIRELESS MOBILE COMMUNICATION MULTI-CODE SUPPORT METHOD", characterized in that it comprises: receiving a channel descriptor from a base station (EB), wherein the channel descriptor comprises at least one set of overflow profile which includes a plurality of overflow profiles that include a range usage code and at least one code type, first recognizing at least one code type that includes information about the coding scheme to be used by the EB or a station mobile (MS); and then recognize an interval usage code that is used to classify all data overflows. "Method" according to claim 22, characterized in that a first group includes all available code types. "Method" according to claim 23, characterized in that a second group or a third group each includes a type of code. "Method" according to claim 24, characterized in that a specified code type included in the first group is shared by all groups. "Method" according to claim 25, characterized in that the code type is a forward error correction (CEA) code type.