Method of executing feedback of downlink channel measurement in OFDMA radio access system
Abstract
This record has no abstract on file.
Term
Term ended
Expired 27 December 2025, 0.7 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
25 claims: 17 independent, 8 dependent
- 1拡張されたサブヘッダを受信する 方法であって、 前記方法は、 拡張されたサブヘッダグループの存在を示すESF(Extended Subheader Format)フィールドを含む 媒体接続制御(MAC)ヘッダを含むプロトコルデータユニット(PDU)を受信する こと と、 前記 ESFフィールドから、前記 拡張されたサブヘッダグループが 存在するか否かを 決定する ことであって、前記拡張されたサブヘッダグループは、 前記MACヘッダ の直後かつ全てのサブヘッダの前に現れる、こと と、 前記拡張されたサブヘッダグループから、 拡張されたサブヘッダの少なくとも1つを識別することと を含 み、 前記拡張されたサブヘッダグループは、サービスデータユニットシーケンス番号(SDU SN)拡張サブヘッダ、下り回線(DL)スリープ制御拡張サブヘッダ、フィードバック要請拡張サブヘッダ、プロトコルデータユニットシーケンス番号(PDU SN)(短)拡張サブヘッダ、またはプロトコルデータユニットシーケンス番号(PDU SN)(長)拡張サブヘッダのうちの少なくとも1つを含む、 方法。
- 2前記拡張されたサブヘッダグループは、 暗号化なしで受信される 、請求項1に記載 の 方法。
- 3前記ESFフィールドの大きさ は、 1 ビット である、請求項 1 に記載 の 方法。
- 4前記拡張されたサブヘッダグループは、 拡張されたサブヘッダグループの総長さを示す 拡張されたサブヘッダグループ長、 拡張されたサブヘッダの様々なタイプを示す少なくとも1つの 拡張されたサブヘッダタイプ及び 拡張されたサブヘッダのうちの少なくとも1つの各々の内容を含む少なくとも1つの 拡張されたサブヘッダボディーを含む、請求項 3 に記載 の 方法。
- 5前記拡張されたサブヘッダボディーの大きさは、前記拡張されたサブヘッダの内容に 依存する 、請求項 4 に記載 の 方法。
- 6前記フィードバック要請拡張サブヘッダは、フィードバックタイプ、フレームオフセット、サブチャネルオフセット、直交周波数分割多重接続(OFDMA)シンボルオフセット、上り回線区間使用コード(UIUC)及びスロットの数を含む、請求項 4 に記載 の 方法。
- 7前記フィードバックタイプは、下り回線平均搬送波対干渉と雑音比(CINR)及び好ましい下り回線区間使用コード(DIUC)のうち の 一つ以上を含む、請求項 6 に記載 の 方法。
- 8前記フレームオフセットは、フィードバック情報を 送信 する開始フレームを 示し 、前記開始フレームは、 前記 フィードバック情報が 送信される フレームである、請求項 6 に記載 の 方法。
- 9前記フィードバック要請拡張サブヘッダは、 ファースト-フィードバックチャネルまたはフィードバックMACヘッダを用いて前記フィードバック情報を送信することを示す 割当タイプをさらに含む、請求項 4 に記載 の 方法。
- 10前記フィードバック情報は、前記ファースト-フィードバックチャネルを通して 送信 される、請求項 9 に記載 の 方法。
- 11拡張されたサブヘッダを送信する 方法であって、 前記方法は、 基地局(BS)において、媒体接続制御(MAC)ヘッダを含むプロトコルデータユニット(PDU)を構成することであって、前記MACヘッダは、拡張されたサブヘッダグループが存在するか否かを示すESF(Extended Subheader Format)フィールドを含む、ことと、 拡張されたサブヘッダグループが存在することを前記ESFフィールドが示す場合に、前記MACヘッダと前記拡張されたサブヘッダグループとを含む前記PDUを送信することと を含み、 前記拡張されたサブヘッダグループは、前記MACヘッダの直後かつ全てのサブヘッダの前に現れ、 前記拡張されたサブヘッダグループは、サービスデータユニットシーケンス番号(SDU SN)拡張サブヘッダ、下り回線(DL)スリープ制御拡張サブヘッダ、フィードバック要請拡張サブヘッダ、プロトコルデータユニットシーケンス番号(PDU SN)(短)拡張サブヘッダ、またはプロトコルデータユニットシーケンス番号(PDU SN)(長)拡張サブヘッダのうちの少なくとも1つを含む、 方法。
- 12前記拡張されたサブヘッダグループ は、暗号化なしで受信される 、請求項 11 に記載 の 方法。
- 13前記ESFフィールドの大きさは、1ビットである、請求項 11 に記載 の 方法。
- 14前記拡張されたサブヘッダグループは、 拡張されたサブヘッダグループの総長さを示す 拡張されたサブヘッダグループ長、 拡張されたサブヘッダの様々なタイプを示す少なくとも1つの 拡張されたサブヘッダタイプ及び 拡張されたサブヘッダのうちの少なくとも1つの各々の内容を含む少なくとも1つの 拡張されたサブヘッダボディーを含む、請求項 13 に記載 の 方法。
- 15前記フィードバック要請拡張サブヘッダは、フィードバックタイプ、フレームオフセット、サブチャネルオフセット、直交周波数分割多重接続(OFDMA)シンボルオフセット、上り回線区間使用コード(UIUC)及びスロットの数を含む、請求項 14 に記載 の 方法。
- 16拡張されたサブヘッダを受信する移動局(MS)であって、 前記MSは、 拡張されたサブヘッダグループの存在を示すESF(Extended Subheader Format)フィールドを含む媒体接続制御(MAC)ヘッダを含むプロトコルデータユニット(PDU)を受信することと、 前記ESFフィールドから、前記拡張されたサブヘッダグループが存在するか否かを決定することと、 前記拡張されたサブヘッダグループから、拡張されたサブヘッダの少なくとも1つを識別することと を実行するように構成され、 前記拡張されたサブヘッダグループは、前記MACヘッダの直後かつ全てのサブヘッダの前に現れ、 前記拡張されたサブヘッダグループは、サービスデータユニットシーケンス番号(SDU SN)拡張サブヘッダ、下り回線(DL)スリープ制御拡張サブヘッダ、フィードバック要請拡張サブヘッダ、プロトコルデータユニットシーケンス番号(PDU SN)(短)拡張サブヘッダ、またはプロトコルデータユニットシーケンス番号(PDU SN)(長)拡張サブヘッダのうちの少なくとも1つを含む、移動局。
- 17前記ESFフィールドの大きさは、1ビットである、請求項16に記載の移動局。
- 18前記拡張されたサブヘッダグループは、拡張されたサブヘッダグループの総長さを示す拡張されたサブヘッダグループ長、拡張されたサブヘッダの様々なタイプを示す少なくとも1つの拡張されたサブヘッダタイプ及び拡張されたサブヘッダのうちの少なくとも1つの各々の内容を含む少なくとも1つの拡張されたサブヘッダボディーを含む、請求項17に記載の移動局。
- 19前記拡張されたサブヘッダボディーの大きさは、前記拡張されたサブヘッダの内容に依存する、請求項18に記載の移動局。
- 20前記拡張されたサブヘッダグループは、暗号化なしで受信される、請求項18に記載の移動局。
- 21拡張されたサブヘッダを送信する基地局(BS)であって、 前記BSは、 媒体接続制御(MAC)ヘッダを含むプロトコルデータユニット(PDU)を構成することであって、前記MACヘッダは、拡張されたサブヘッダグループが存在するか否かを示すESF(Extended Subheader Format)フィールドを含む、ことと、 拡張されたサブヘッダグループが存在することを前記ESFフィールドが示す場合に、前記MACヘッダと前記拡張されたサブヘッダグループとを含む前記PDUを送信することと を実行するように構成され、 前記拡張されたサブヘッダグループは、前記MACヘッダの直後かつ全てのサブヘッダの前に現れ、 前記拡張されたサブヘッダグループは、サービスデータユニットシーケンス番号(SDU SN)拡張サブヘッダ、下り回線(DL)スリープ制御拡張サブヘッダ、フィードバック要請拡張サブヘッダ、プロトコルデータユニットシーケンス番号(PDU SN)(短)拡張サブヘッダ、またはプロトコルデータユニットシーケンス番号(PDU SN)(長)拡張サブヘッダのうちの少なくとも1つを含む、基地局。
- 22前記ESFフィールドの大きさは、1ビットである、請求項21に記載の基地局。
- 23前記拡張されたサブヘッダグループは、拡張されたサブヘッダグループの総長さを示す拡張されたサブヘッダグループ長、拡張されたサブヘッダの様々なタイプを示す少なくとも1つの拡張されたサブヘッダタイプ及び拡張されたサブヘッダのうちの少なくとも1つの各々の内容を含む少なくとも1つの拡張されたサブヘッダボディーを含む、請求項22に記載の基地局。
- 24前記拡張されたサブヘッダボディーの大きさは、前記拡張されたサブヘッダの内容に依存する、請求項23に記載の基地局。
- 25前記拡張されたサブヘッダグループは、暗号化なしで受信される、請求項23に記載の基地局。
Independent claims25
46 paragraphs, as filed
The present invention relates to a method of transferring feedback information, and more specifically to a method of transferring feedback information using an extended subheader.
FIG. 1 is a diagram illustrating the structure of a medium access control (hereinafter referred to as'MAC') protocol data unit (hereinafter referred to as'PDU').
As shown in FIG. 1, the MAC management PDU includes a MAC header 11, a management message type 12, and a MAC management payload 13. The bandwidth request PDU is also used by each user to dynamically request the bandwidth required to transfer uplink data. The bandwidth requesting PDU is characterized in that it contains only the bandwidth requesting header and no payload at all.
FIG. 2 shows the structure of the MAC PDU shown in FIG. Specifically, if a MAC PDU is formed, as shown in FIG. 2, the MAC service data unit (hereinafter referred to as'SDU') is formed without packing or fragmentation. For example, the MACPDU does not contain a packing subheader or a fragmented subheader.
Figure 3 shows another example of the structure of a MAC PDU. As shown in FIG. 3, MACSDU31 is fragmented to be included in the formation of two or more MACPDUs 30a and 30b. In the formation of MACPDUs 30a and 30b, fragmented subheaders 34a and 34b are attached after MAC headers 33a and 33b, respectively. Also, MACSDU35a and 35b are attached after the fragmented subheaders 34a and 34b, respectively, to form MACPDUs 30a and 30b.
FIG. 4 shows yet another example of the structure of the MAC PDU. In FIG. 4, the MACPDU is formed by packing two or more MACSDUs (eg, MACSDU # 1 41a and MACSDU # 2 41b). These MACS DU 44 and 46 are mounted after the packing subheaders 43 and 46, respectively. Here, the MAC PDU has a MAC header 42 before it, more specifically before the packing sub-header 43.
As mentioned above, when the MACSDU is fragmented or packed, a fragmented or packing subheader is attached to each MACPDU. In this way, MACPDUs can be categorized into their respective units and can also be categorized according to frame number.
In the prior art, only methods relating to fragmentation and packing are available. That is, the prior art does not include a MACPDU structure with various enhanced subheaders.
<p> Accordingly, the present invention relates to a method of transferring feedback information using an extended subheader that substantially eliminates one or more problems due to limitations and shortcomings of related techniques.</p><p> An object of the present invention is to provide a method for transferring feedback information.</p><p> Another object of the present invention is to provide a method of receiving feedback information.</p><p> Yet another object of the present invention is to provide a system for transferring and receiving feedback information.</p>
<p> The additional advantages, purposes and features of the present invention will be partially developed in the description below and will be partially revealed to those skilled in the art in the art of the present invention from the following contents, or of the present invention. Can be learned by implementation. The objects and other advantages of the present invention can be realized and acquired by the structures specifically pointed out in the following description and claims, in addition to the accompanying drawings.</p><p> In order to obtain such additional objectives and other advantages, and to achieve the objectives of the present invention, the method of transferring feedback information, as embodied and broadly described herein, is media connection. Includes a mobile station (hereinafter referred to as'MS') that receives a protocol data unit (PDU) including a control (MAC) header from a base station (Base Station; hereinafter referred to as'BS'). The mobile station then determines from the received MAC header whether the extended subheader group is located after the MAC header and also confirms the feedback request extended subheader from the extended subheader group. Finally, the MS transfers feedback information through the feedback request extension subheader.</p><p> In another aspect of the invention, the method of transferring feedback information includes a base station (BS) that transfers a protocol data unit (PDU) that includes a media connection control (MAC) that represents the presence of an extended subheader group. .. Here, the extended subheader group includes a feedback request extended subheader. The base station then receives feedback information from the mobile station (MS).</p><p> In yet another aspect of the invention, the system that transfers and receives feedback information is a protocol data unit that includes a media connection control (MAC) header that indicates whether or not an extended subheader group is located following the MAC header. Includes a base station (BS) that transfers (PDUs). Here, the extended subheader group indicates a feedback request extended subheader. The system also includes a mobile station (MS) that receives the PDU and subsequently determines whether or not an extended subheader is located from the MAC header to the MAC header. The mobile station then determines from the MCA header whether or not an extended subheader group is located following the MAC header. The mobile station also confirms the feedback request extended subheader from the extended subheader group. Finally, the mobile station transfers feedback information through a feedback request extension subheader.</p><p> Both the general description of the invention described above and the detailed description below are exemplary and descriptive, and it is self-evident that additional description of the invention can be provided as requested.</p>
It is self-evident to a skilled person in the art that various modifications and changes relating to the invention can be made without departing from the essence and scope of the invention. Accordingly, the present invention includes any amendments and modifications in accordance with the appended claims and their equivalents.
Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, the same reference number shall be used in common for the same component as much as possible.
FIG. 5 is a diagram showing an example of a MAC header. As shown in FIG. 5, MAC header 'Thailand represented by 6 bits contain flop (type)' field. Note that this'type'field can represent six different types of subheaders determined by the bitmap type. Different types of these subheaders can be attached following the MAC header, and the detailed type of subheader can be indicated in the'Type'field. This type field indicates 6 subheader types, each subheader having a size of 2 bytes.
Table 1 shows an example of six subheader types.
<tables num="1"><img file="JP4843618B2_D0001.tif" /></tables> As shown in Table 1, there are 6 types of subheaders, the most significant bit being # 5 and the least significant bit being # 0. Each type of subheader can be indicated as being present or being absent. More specifically, the '1' or '0' type bits indicate the current existence or absence of a particular subheader, respectively.
For example, if the'type'bit # 5 is indicated as '1', the MACPDU contains a mesh subheader. That is, in mesh mode, each mobile station is given a node identification (Node ID) so that each mobile station can be identified. From this point, the mesh subheader can be used to provide a node ID for each mobile station. When the'type'bit # 4 is indicated as 1, the MACPDU contains a subheader for an automatic repeat request (ARQ). When the'type'bit # 3 is indicated as 1, the MACPDU contains an extended packing subheader or an extended fragmentation subheader. When the'type'bit 2 and the'type'bit # 1 are each designated as '1', the packet PDU corresponding to the user is mapped to the MACSDU payload. In addition, the MAC PDU includes a MAC header and a cyclic redundancy check (Cyclic Redundancy Check; hereinafter referred to as'CRC') attached to the MAC header.
Finally, the bit application of'type'bit # 0 is different for uplink and downlink transfers. When the'type'bit # 0 is indicated as '1', the MACPDU contains a first-feedback allocation subheader. Here, the first-feedback allocation subheader is located at the end of all subheaders. To receive feedback values from mobile stations, the fast-feedback assignment subheader is used to assign resources and feedback information types within the fast feedback channel (ie, channel quality indicator channel).
Table 2 shows an example of the first-feedback allocation subheader.
<tables num="2"><img file="JP4843618B2_D0002.tif" /></tables> As shown in Table 2, the First-Feedback Assignment subheader uses the'Assignment Offset'to allocate the Channel Quality Indicator Channel (CQICH) for forwarding feedback information, which is the First Feedback Channel Information Element ( Directed by IE). Here, the CQICH allocation can be represented by a slot. The type of feedback information can be selected by'feedback type'. After the mobile station receives the first feedback allocation subheader, the mobile station can use the feedback value to request a change to Multi Input Multi Output (MIMO) mode or Permutation mode. ..
On the uplink, the MACPDU contains an authorization management subheader when the'type'bit # 0 is indicated as '1'. This approval management subheader is used to convey information about managing uplink resources. Also, the use of approval management subheaders varies depending on the subheader type. Based on the type of service, a piggyback request, a bandwidth allocation request using bandwidth stealing and polling techniques can be determined.
As shown in FIG. 5, the MAC header contains two reserved bits, each with a bit length of 1. Here, both of the two reserved bits can be used to contain the information in the enhanced first-feedback allocation subheader. That is, the reserved bits can be used to indicate whether or not an enhanced first-feedback allocation subheader is attached.
When the reserved bit is indicated as 1, the MAC header contains information that there is an enhanced first-feedback allocation subheader, or when the reserved bit is indicated as '0', the MAC header is Does not contain any information on the enhanced First-Feedback Assignment subheader.
Table 3 shows an example of an enhanced First-Feedback Assignment subheader.
<tables num="3"><img file="JP4843618B2_D0003.tif" /></tables> According to Table 3, the enhanced fast-feedback allocation subheader forwards data packets to the mobile station. In addition, the enhanced fast-feedback assignment subheader requests feedback on information about forwarding channel and antenna weight values. Here, additional information can be requested in much the same manner as the method of transferring feedback information.
In Table 3, the'Assignment Type'field can be used to select how to transfer feedback information. For example, if the'Assignment Type'field is indicated by '0', the mobile station uses the first feedback channel to transfer the feedback information. In this case, the'allocated offset'field is used to indicate the location of the first feedback channel and the'CQICH_num' field is used to determine the number of slots used to transfer the feedback information.
Also, the'feedback type'field is used to indicate the content of the feedback information. For example, if a BS uses two antennas, the BS can request weight values corresponding to the first and second antennas while allocating the two slots. Then, the MS can send the weight value of the first antenna and the weight value of the second antenna using the assigned slot.
The'frame offset'field can also be used to provide information about when the MS should send feedback information. That is, the MS can send feedback information after a specified time period or a specified number of frames after receiving the subheader.
On the other hand, when the'assignment type'field is indicated by '1', the MS uses the MAC header to forward the feedback information. Here, the'duration'field is used to provide information about the radio resources allocated within the uplink, and the'feedback type'is used to indicate the type of feedback information.
Table 4 shows an example of feedback information corresponding to the'Feedback Type'field value.
<tables num="4"><img file="JP4843618B2_D0004.tif" /></tables> As mentioned above, if the'Assignment Type'field is indicated by '1', the MS has been assigned to receive the enhanced First-Feedback Assignment subheader and transfer feedback information through the MAC header. Uses uplink wireless resources.
FIG. 6 is a diagram showing another example of the MAC header. As shown in FIG. 6, the MAC header contains an extended subheader format (ESF) field to better represent the extended subheader group. That is, when the ESF field value is set to '1', the extended subheader group is provided between the six types of MAC headers and subheaders (immediately after the MAC header), which is the'type' field. It is expressed by. Alternatively, the extended subheader group can appear between the subheader and the payload. Hereinafter, the terms'extended subheader'and'extended subheader group' are used interchangeably.
FIG. 7 is a diagram showing an example of MAC PDU. As shown in the figure, MACPDU includes MAC header 71, ESF72, subheader 73, payload 74 and CRC75. The ESF72 can be located between the header 71 and the subheader 73, and the length of the ESF72 can be determined based on the number of attached subheaders. Alternatively, the ESF 72 may be positioned or mounted after the subheader 73.
BS can set the ESF type value in the MAC header to '1' so that the MS can receive notifications about the existence of ESF between the MAC header and the subheader. Also, the ESF must not be encrypted. However, the MS can perform an error detection operation using the CRC located at the end of the PDU.
FIG. 8 is a diagram showing the structure of the extended subheader group. As shown in FIG. 8, the extended subheader group includes an extended subheader length field 81, a reserved bitfield 82, and an extended subheader type to provide the total length of the extended subheader group. It consists of a field 83 and an extended subheader body 84. Preferably, the extended subheader length field must be displayed in 8 bits and the total length of the extended subheader is expressed in bytes. Here, the total length is up to 2<sup>7</sup>Can be displayed in bytes. There can also be as many as 128 extended subheader types.
Table 5 shows an example of extended subheader types.
<tables num="5"><img file="JP4843618B2_D0005.tif" /></tables> Here, Table 5 shows the addition of two extended subheaders. That is, based on the extended subheader type field 83, the type corresponding to '0' has an extended subheader_1 with a length of 1 byte, while the type corresponding to '1' has 2 bytes. It has an extended subheader_2 with a length. Depending on the type, the extended subheader can be categorized as whether the subheader is for uplink transfer or downlink transfer. For example, the subheader used in the uplink is formed by the MS and transferred to the BS, and when the MS receives this subheader, the MS ignores it.
FIG. 9 is a diagram showing an example of the ESF format. See FIGS. 7 and 8 here along with Table 2. In FIG. 9, the MACPDU contains an extended subheader group, and the extended subheader length field 91 is used to indicate the total length of the subheaders. In the figure, the total length of the subheader is 6 bytes.
Specifically, the new extended subheader_1 includes reserved bits 92 and extended subheader type 93. Here, the extended subheader type is '0', which has the same length as 1 byte. Also, the body 94 of the extended subheader is represented by type '0' and contains information on the subheader having a length of 1 byte.
Also, the new extended subheader_2 includes reserved bits 95 and extended subheader type 97. Here, the extended subheader type is '1' and has a length of 2 bytes. Body 97 of the extended subheader_2 has two subheaders with a length of 2 bytes, which are different from the new extended subheader_1.
Table 6 is an example of a downlink extended subheader attached to a MACPDU.
<tables num="6"><img file="JP4843618B2_D0006.tif" /></tables> As shown in Table 6, one or more subheaders are attached to the MACPDU before they are forwarded. For example, if the ESF type field specifies a value of '00000010', a feedback request extension subheader with a 3-bit length will be attached to the MACPDU.
Table 7 shows other examples of uplink-extended subheader groups attached to MACPDUs.
<tables num="7"><img file="JP4843618B2_D0007.tif" /></tables> As shown in Table 7, one or more subheaders are attached to the MACPDU before they are transferred. For example, if there is a request to change the MIMO mode, the MIMO mode feedback extended subheader is transferred after the desired mode is selected.
Table 8 shows an example of the feedback request extended subheader format from the uplink extended subheader.
<tables num="8"><img file="JP4843618B2_D0008.tif" /></tables> As shown in Table 8, the feedback request extended subheader format can be 3 bytes in length. When the feedback request extension subheader format is transferred to the MS, the MS uses the allocated uplink radio resources to transfer feedback information based on the content of the feedback request extension subheader. Additionally, the'OFDMA symbol offset'field and the'subchannel offset'field provide the location of uplink resources for feedback information. In addition, the'No.slot'field represents the number of slots assigned to the number of busts or slots to be used from the specified position. Here, the method of encoding the feedback information is determined by the uplink section usage code (UIUC). Finally, the'frame offset'field provides a start frame for transferring the feedback information, which is the frame at which the feedback information begins to transfer.
<figref num="1">It is a figure which illustrates the structure of the medium connection control (MAC) protocol data unit (PDU).</figref><figref num="2">It is a figure which shows the structure of the MAC PDU of FIG.</figref><figref num="3">It is a figure which shows another example of the structure of MACPDU.</figref><figref num="4">It is a figure which shows still another example of the structure of MACPDU.</figref><figref num="5">It is a figure which shows an example of a MAC header.</figref><figref num="6">It is a figure which shows another example of a MAC header.</figref><figref num="7">It is a figure which shows an example of MACPDU.</figref><figref num="8">It is a diagram showing the structure of the extended subheader group.</figref><figref num="9">It is a figure which shows an example of the extended subheader format (ESF).</figref>
Every citation, both waysCites: the store holds 4 of 5
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2001045012A | Cites | Japan | Search report |
| JP2002135231A | Cites | Japan | Search report |
| JP2002135231A | Cites | Japan | – |
| JP2001045012A | Cites | Japan | – |
| IEEE Computer Society, IEEE Microwave Theory and Techniques Society,IEEE Std. 802.16-2004, IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems,IEEE STANDARD,米国,IEEE,2004年10月 1日,P. 1,35-42,121-133,463,539-545 | Non-patent | – | – |
| Balachandran, K 他,Medium Access Control and Radio Resource Management for Packet Data Services over IS-136 Channels,Vehicular Technology Conference, 1999 IEEE 49th,米国,IEEE,1999年 5月16日,Vol. 1,P.133-139 | Non-patent | – | – |
77 members in 13 offices
Priority claims24
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020040112927 | Republic of Korea | – | |
| 20040112927 | Republic of Korea | A | |
| 20040112927 | Republic of Korea | A | |
| 1020050000930 | Republic of Korea | – | |
| 20050000930 | Republic of Korea | A | |
| 20050000930 | Republic of Korea | A | |
| 60647594 | United States of America | – | |
| 64759405 | United States of America | P | |
| 64759405 | United States of America | P | |
| 60663347 | United States of America | – | |
| 66334705 | United States of America | P | |
| 66334705 | United States of America | P | |
| 2005004579 | Republic of Korea | W | |
| 2005004579 | Republic of Korea | W | |
| 20042004112927 | – | – | – |
| 2005647594 | – | – | – |
| 2005663347 | – | – | – |
| 2005200500930 | – | – | – |
| 2005004579 | – | – | – |
| KR20040112927 | – | – | – |
| KR20050000930 | – | – | – |
| US20050647594P | – | – | – |
| US20050663347P | – | – | – |
| WO2005KR04579 | – | – | – |
Members77
| Document | Office | Kind | |
|---|---|---|---|
| US792843A | United States of America | A | |
| KR20060033957A | Republic of Korea | A | |
| AU2005296409A1 | Australia | A1 | |
| CA2583194A1 | Canada | A1 | |
| WO2006043773A2 | World Intellectual Property Organization (WIPO) | A2 | |
| KR20060039804A | Republic of Korea | A | |
| US2006111129A1 | United States of America | A1 | |
| KR20060074795A | Republic of Korea | A | |
| AU2005320420A1 | Australia | A1 | |
| CA2590670A1 | Canada | A1 | |
| WO2006071052A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20060080542A | Republic of Korea | A | |
| US2006171417A1 | United States of America | A1 | |
| TW200635308A | Taiwan Province of China | A | |
| TW200704035A | Taiwan Province of China | A | |
| US2007041378A1 | United States of America | A1 | |
| WO2006043773A3 | World Intellectual Property Organization (WIPO) | A3 | |
| IL182560A0 | Israel | A0 | |
| IL182560D0 | Israel | D0 | |
| EP1810424A2 | European Patent Office (EPO) | A2 | |
| MX2007007798A | Mexico | A | |
| EP1832029A1 | European Patent Office (EPO) | A1 | |
| CN101040461A | China | A | |
| IL183917A0 | Israel | A0 | |
| IL183917D0 | Israel | D0 | |
| CN101116274A | China | A | |
| JP2008517518A | Japan | A | |
| JP2008526093A | Japan | A | |
| BRPI0516362A | Brazil | A | |
| BRPI0517580A | Brazil | A | |
| KR20080108395A | Republic of Korea | A | |
| AU2008252030A1 | Australia | A1 | |
| CN101447814A | China | A | |
| JP2009153160A | Japan | A | |
| US7564831B2 | United States of America | B2 | |
| EP2081315A2 | European Patent Office (EPO) | A2 | |
| US2009207831A1 | United States of America | A1 | |
| EP2081315A3 | European Patent Office (EPO) | A3 | |
| TW200943838A | Taiwan Province of China | A | |
| AU2005296409B2 | Australia | B2 | |
| KR100932487B1 | Republic of Korea | B1 | |
| AU2005320420B2 | Australia | B2 | |
| US2010067475A1 | United States of America | A1 | |
| US7684762B2 | United States of America | B2 | |
| US2010118821A1 | United States of America | A1 | |
| US2010118822A1 | United States of America | A1 | |
| US2010118823A1 | United States of America | A1 | |
| US2010118824A1 | United States of America | A1 | |
| AU2008252030B2 | Australia | B2 | |
| KR100970646B1 | Republic of Korea | B1 | |
| US7826439B2 | United States of America | B2 | |
| US7860077B2 | United States of America | B2 | |
| US7860078B2 | United States of America | B2 | |
| US7864746B2 | United States of America | B2 | |
| US7869419B2 | United States of America | B2 | |
| US7873023B2 | United States of America | B2 | |
| CN101040461B | China | B | |
| US7885247B2 | United States of America | B2 | |
| EP1810424A4 | European Patent Office (EPO) | A4 | |
| KR101029812B1 | Republic of Korea | B1 | |
| IL183917A | Israel | A | |
| CN101116274B | China | B | |
| JP4832444B2 | Japan | B2 | |
| JP4843618B2This record | Japan | B2 | |
| IL182560A | Israel | A | |
| JP4897841B2 | Japan | B2 | |
| TWI367010B | Taiwan Province of China | B | |
| KR101154988B1 | Republic of Korea | B1 | |
| EP1832029B1 | European Patent Office (EPO) | B1 | |
| CN101447814B | China | B | |
| ES2392447T3 | Spain | T3 | |
| TWI383623B | Taiwan Province of China | B | |
| TWI385979B | Taiwan Province of China | B | |
| KR101253618B1 | Republic of Korea | B1 | |
| CA2590670C | Canada | C | |
| CA2583194C | Canada | C | |
| EP2081315B1 | European Patent Office (EPO) | B1 |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4843618
- Publication, DOCDB
- 4843618
- Publication, EPODOC
- JP4843618B
- Application
- 2007548098
- Application, DOCDB
- 2007548098
- Application, EPODOC
- JP20070548098
Titles2
- Japanese
- 拡張されたサブヘッダを用いるフィードバック情報を転送する方法
- English
- How to transfer feedback information with extended subheaders
Classification
- CPC, 4
- H04L1/0028
- H04L1/1685
- H04L1/0026
- H04J11/00
- IPC, 1
- H04L29 08