A method of performing polling procedure in a wireless communication system

The present invention relates to a wireless communication system. More specifically, it relates to a method of generating data blocks for executing an inquiry procedure in a wireless communication system, and also relates to a method of transmitting data and a method of executing an inquiry procedure.

Various types of data retransmission methods can be used to ensure the reliability of data transmission to the receiving end in a wireless communication system. In particular, when the receiving end needs to receive non-real-time packet data, such as signaling data or TCP/IP data, the need to use the retransmission method is increased.

An example of the data transmission method used in the wireless communication system will be described below. The receiving end sends a status report to the sending end to report that at least one or more data blocks have been successfully received from the sending end. The transmitting end uses the status report to transmit to the receiving end the data block that the receiving end failed to receive successfully. In order to apply the retransmission method, the data that has been transmitted once should be stored in the buffer for a certain period of time without discarding it. Correspondingly, a transmission buffer and a retransmission buffer are required. The data that has never been transmitted to the receiving end is stored in the transmission buffer, and the data that has been transmitted to the receiving end but needs to be kept in a standby state for retransmission is stored In the retransmission buffer.

The transmitting end can request the receiving end to transmit a status report. This procedure is called an interrogation procedure. If the status report transmitted by the receiving end is lost during the transmission, or the receiving end does not transmit the status report to the transmitting end in time, the transmitting end can execute the inquiry procedure. Another option is that the transmitter can periodically execute the interrogation procedure.

The transmitter must use additional radio resources to perform the interrogation procedure. Accordingly, in order to effectively use radio resources, unnecessary use of interrogation procedures should be avoided. To this end, reasonable standards need to be established to determine when the transmitting end should perform the inquiry procedure.

Therefore, the present invention aims at the following methods: a method of generating data blocks for executing an interrogation procedure in a wireless communication system; a method of transmitting data and a method of executing an interrogation procedure, which can generally be avoided due to related technologies. One or more problems caused by limitations and shortcomings.

One object of the present invention is to provide the following methods: a method for generating data blocks for executing an interrogation program in a wireless communication system; a method for transmitting data and a method for executing an interrogation program, wherein the interrogation program can still be executed while the interrogation program is executed. Effective use of radio resources.

Another object of the present invention is to provide the following methods: a method for generating data blocks for executing an inquiry procedure in a wireless communication system; a method for transmitting data and a method for executing an inquiry procedure, wherein the transmitting end can execute the inquiry in time Program to avoid unexpected interruption of communication.

In a wireless communication system, a specific protocol layer performs the data retransmission function. In order to perform the data retransmission function, the protocol layer has a transmission buffer and a retransmission buffer. The protocol layer can consider the status of the transmission buffer and the retransmission buffer, that is, the amount of data stored in the transmission buffer and the retransmission buffer, to determine whether to execute the inquiry procedure.

In one aspect of the present invention, if there is no data to be transmitted to the receiving end in both the transmission buffer layer and the retransmission buffer layer, the protocol layer executes an inquiry procedure to request the receiving end to send a status report. When determining whether there is no data to be transmitted to the receiving end in the retransmission buffer, it is better to exclude the data block that has not received the retransmission request information from the receiving end.

In another aspect of the present invention, the protocol layer considers the amount of data sent to the receiving end and executes the inquiry procedure. That is, if the amount of data sent to the receiving end reaches a certain amount or higher, the protocol layer executes the inquiry procedure. This procedure can be executed repeatedly.

According to the present invention, radio resources can be effectively used during the execution of the interrogation program, and the transmitting end can execute the interrogation program in time, thereby preventing the communication from stopping unexpectedly.

In the following, it is easy to understand the structure, operation and other features of the present invention through the preferred embodiments of the present invention. Examples of the present invention are illustrated in the accompanying drawings. The specific embodiments described later are examples in which the technical features of the present invention are applied to E-UMTS (Evolved Universal Mobile Telecommunieations System). However, please note that the specific embodiments of the present invention can be applied to other wireless communication systems other than E-UMTS.

Figure 1 is a block diagram illustrating the network structure of an E-UMTS. E-UMTS is a system evolved from the conventional WCDMA UMTS. Its basic standard is currently used by 3GPP (3^rd Generation Partnership Project, the third-generation partnership project). E-UMTS can also be referred to as an LTE (Long Term Evolution) system.

Referring to Figure 1, E-UTRAN includes base stations (hereinafter referred to as'eNode B'or'eNB'), in which individual eNBs are connected to each other via an X2 interface. In addition, each of the eNBs is connected to user equipment (UE) via a radio interface, and is connected to an EPC (Evolved Packet Core) via an S1 interface. The EPC includes a mobile management entity/system architecture evolution (MME/SAE) gateway.

Based on the three lower layers of the widely known OSI (open system interconnection) standard model in communication systems, the radio interface protocol layer between the user equipment and the network can be divided into the first layer L1, the second layer L2, and the second layer L2. The third layer is L3. The physical layer belonging to the first layer L1 uses physical channels to provide information transmission services. The radio resource control (radio resource control, hereinafter abbreviated as "RRC") located in the third layer is used to control the radio resources between the user equipment and the network. To this end, the RRC layer can be used to exchange RRC messages between the user equipment and the network. The RRC layer can be distributed at network nodes (which include Node B, AG, and similar nodes) or can be independently located at Node B or AG.

Figure 2 is a schematic diagram illustrating E-UTRAN (Evolved Universal Terrestrial Radio Access Network). In Figure 2, the shaded part represents the functional entity of the user plane, and the non-shaded part represents the functional entity of the control plane.

Figures 3A and 3B illustrate the structure of the radio interface protocol between user equipment (UE) and E-UTRAN. Figure 3A is a schematic diagram of a control plane protocol, and Figure 3B is a schematic diagram of a user plane protocol . Referring to Figures 3A and 3B, a radio interface protocol level includes a physical layer, a data link layer, and a network layer, and vertically includes a user plane for data information transmission and a signal transmission layer. Control plane. Based on the three lower layers of the well-known Open System Interconnection (OSI) standard model in communication systems, the protocol layers of Figure 3A and Figure 3B can be divided into L1 (first layer), L2 (second layer), and L3 (second layer). Three layers).

As the first layer, the physical layer provides information transmission services to an upper layer by using physical channels. The physical layer (PHY) is connected to the medium access control (Medium Access control, hereinafter abbreviated as "MAC") layer above the physical layer via a transmission channel. Data is transmitted between the media access control layer and the physical layer through the transmission channels. In addition, data is transmitted between different physical layers via these physical channels, more specifically, data is transmitted between one physical layer at the transmitting end and another physical layer at the receiving end. The E-UMTS downlink physical channel is modulated according to an Orthogonal Frequency Division Multiplexing (OFDM) mechanism, and time and frequency are used as radio resources.

The medium access control (hereinafter abbreviated as'MAC') layer of the second layer provides services to the radio link control (hereinafter abbreviated as RLC) layer above the MAC layer via a logical channel. The RLC layer of the second layer supports reliable data transmission. In order to use IP packets (for example, IPv4 or IPv6) to efficiently transmit data during radio communication with narrow bandwidth, the PDCP layer of the second layer (L2) performs header compression to reduce the size of redundant control information.

The radio resource control (hereinafter abbreviated as'RRC') located on the lowest part of the third layer is only defined in the control plane, and is related to the configuration and reconfiguration of radio bearer (hereinafter abbreviated as'RB'). Configure and publish associations to control the logic, transmission and physical channels. In this case, RB means a service provided by the second layer, used to transmit data between the user equipment and UTRAN.

Examples of downlink transmission channels that carry data from the network to user equipment include a broadcast channel (BCH) that carries system information, a paging channel (PCH) that carries paging information, and a carrier The downlink shared channel (SCH) for sending user communication traffic or control messages. The communication flow or control signal of the downlink multicast or broadcast service can be transmitted via the downlink SCH or the additional downlink multicast channel (multicast channel, MCH). At the same time, examples of uplink transmission channels that carry data from user equipment to the network include a random access channel (RACH) that carries initial control information and a user communication flow or control Message uplink shared channel (uplink shared channel, UL-SCH).

Examples of logical channels located on the transmission channel and corresponding to the transmission channels include a broadcast control channel (BCCH), a call control channel (PCCH), a common control channel (CCCH), and a multicast control channel (MCCH). ) And a multicast traffic channel (MTCH).

As mentioned above, the RLC layer of the second layer supports reliable data transmission. In addition, the RLC is used to divide and/or concatenate the data received from the upper layer to control the size of the data, so that the lower layer can transmit data to a radio interval. In addition, in order to ensure the various quality of service (QoS) required for each radio transmission, the RLC layer of the second layer provides three types of operation modes: transparent mode (TM), un-acknowledged mode (un-acknowledged mode) , UM) and acknowledged mode (acknowledged mode, AM). Specifically, for reliable data transmission, the AM RLC layer performs a retransmission function through the automatic repeat and request (ARQ) function. In the following, the UM mode and AM mode of the RLC layer will be described in more detail.

The UM RLC layer transmits PDUs by adding a PDU header to each PDU, so that the receiving end can recognize which PDUs have been lost during transmission. The PDU header includes a sequence number (hereinafter abbreviated as " SN"). According to this function, the UM RLC layer is mainly used to transmit broadcast/multicast data or real-time data on the user plane, such as a string of voice (for example, VoIP) or packet service domain (hereinafter abbreviated as "PS domain") flow. The UM RLC layer is also used in a control plane to transmit RRC messages that do not require confirmation among the RRC messages transmitted to a specific user equipment or a specific user equipment group in a unit.

Similar to the UM RLC layer, the AM RLC layer forms an RLC PDU by adding a PDU header including SN to the RLC PDU. However, the AM RLC layer is also different from the UM RLC layer, that is, the receiving end performs an acknowledgment operation in response to the PDU sent from the transmitting end. The reason why the receiving end performs acknowledgment in the AM RLC layer is to request the transmitting end to retransmit the PDU that the receiving end has not received. This retransmission function is the main feature of the AM RLC layer. Correspondingly, the AM RLC layer will ensure correct data transmission through retransmission. For this reason, the AM RLC layer is used to transmit non-real-time packet data in the user plane, such as TCP/IP in the PS domain. The AM RLC layer is also used in the control plane to transmit RRC messages that do not require confirmation among the RRC messages transmitted to specific user equipment in a unit.

From the perspective of communication directionality, the UM RLC layer is used for one-way communication, while the AM RLC layer is used for two-way communication because of feedback from the receiving end. From a structural point of view, the UM RLC layer is also different from the AM RLC layer. That is, the UM RLC layer allows an RLC entity to perform the transmission function or the reception function, and the AM RLC layer allows the entity performing the transmission function and the entity performing the reception function to exist in an RLC entity at the same time.

The complexity of the AM RLC layer is due to the retransmission function. To perform retransmission management, the AM RLC entity includes a retransmission buffer in addition to the transmission buffer, and uses a transmission and reception window for flow control. The AM RLC of the transmitting end executes an inquiry procedure to request the peer RLC entity of the receiving end to transmit a status report, and the receiving end transmits the status report to the transmitting end to report receipt confirmation information. In addition, the AM RLC entity performs the function of forming status PDUs to transmit status reports.

The AM RLC entity uses a plurality of protocol parameters, status parameters, timers, etc. to support the above-mentioned functions. In the AM RLC layer, PDUs or status PDUs used to control the transmission of data such as status reports will be called control PDUs, and PDUs used to transmit user data will be called data PDUs.

As mentioned above, the AM RLC entity at the transmitting end includes two buffers, namely a transmission buffer and a retransmission buffer. Among the data transmitted from the upper-layer entity, the data not included in the RLC PDU is stored in the transmission buffer. The RLC PDU transmitted to the underlying entity is stored in the retransmission buffer until the receiving end confirms that the RLC PDU has been successfully received in it.

Figure 4 is a block diagram illustrating an example of the functional blocks of the RLC AM entity.

Referring to FIG. 4, the RLC SDU (Service Data Unit) transmitted from the upper layer (RRC layer or PDCP sublayer) is stored in the transmission buffer 41. The segmentation/concatenation module 42 segments and/or concatenates at least one RLC SDU from the transmission buffer 41. According to the transmission block size reported from the lower layer, segmentation and/or concatenation are performed at a specific transmission timing. As a result, the RLC PDU generated by the RLC AM entity can have the size expected by the lower layer. The RLC header adding module 43 adds an RLC header to the data block transmitted by the segmentation/concatenation module 42. Generate an RLC AMD PDU as the RLC PDU header added to the data block.

Figure 5 is a block diagram illustrating the basic structure of AMD PDU. The ADM PDU includes a PDU header part and a data field part. The header may include a fixed part and an extended part, where the fixed part exists in all AMD PDUs, and the extended part is included in the AMD PDU only when necessary. If one or more data field elements exist in the AMD PDU, the extended part is included in the AMD PDU.

The fixed part includes a D/C field, a re-segmentation flag (re-segmentation flag, RF) field, a polling (P) field, a frame information (framing info, FI) field, and a Extension bit (E) field and a serial number (SN) field. The D/C field includes information identifying whether the corresponding AMD PDU is a data PDU or a control PDU. The RF field includes information indicating whether the corresponding RLC PDU is a single full AMD PDU or a part of another AMD PDU. The query field includes information indicating whether the AM RLC entity at the transmitting end requests the peer AM RLC entity at the receiving end to transmit a status report. The FI field includes information indicating that the RLC SDU included in the AMD PDU has been divided from the beginning part and/or the end part of the data field. The E field includes information indicating whether the data field starts after the fixed part, or whether the additional E field and the LI field follow after the fixed part. The SN field includes the serial number of the AMD PDU.

Referring again to FIG. 4, the AMD PDU generated as a header added by the RLC header adding module 43 is transmitted to the lower layer, for example, the MAC layer. Before the AMD PDU is transmitted to the lower layer, additional procedures such as encryption can be performed on the AMD PDU if necessary. The AMD PDU transmitted to the lower layer is stored in the retransmission buffer 44 to perform the retransmission function.

If the RLC AM entity performs the receiving function, the routing module 46 will route the RLC PDU according to the type of the received RLC PDU to transmit the control PDU to the RLC control module 45 and to the receiving buffer/HARQ reordering module 47 Transmit AMD PDU. The receiving buffer/HARQ reordering module 47 stores the AMD PDUs transmitted by the routing module 46. If the AMD PDUs are not received in the order of SN, they are adjusted in the order of SN. The RLC header removal module 48 removes the RLC header from the AMD PDU, and transmits the obtained data to the SDU reassembly module 49. The SDU reassembly module 49 uses the data transmitted from the RLC header removal module to reassemble at least one or more RLC SDUs, and then transmits the obtained data to the upper layer.

The RLC AM entity at the receiving end transmits a status report to the transmitting end through the status PDU to report whether at least one or more RLC PDUs transmitted from the transmitting end have been successfully received.

Figure 6 is a flowchart illustrating a procedure according to a specific embodiment of the present invention. The specific embodiment in Fig. 6 is about an example, which determines whether the RLC AM entity executes the inquiry procedure according to the status of the transmission buffer and the retransmission buffer. That is, if there is no data to be transmitted to the receiving end in the transmission buffer and the retransmission buffer, the RLC AM entity executes an inquiry procedure to request the receiving end to send a status report. When determining whether there is data to be transmitted to the receiving end in the retransmission buffer, the data block that has not received the retransmission request information from the receiving end is excluded.

Referring to Figures 4 and 6, the AM RLC entity checks the status of the transmission buffer 41 [S61], and confirms whether the data to be transmitted to the receiving end is stored in the transmission buffer 41 [S62]. If the data to be transmitted to the receiving end is stored in the transmission buffer 41, the AM RLC entity does not perform the inquiry procedure. That is, the AM RLC entity sets the P field to "0", where the P field exists in the header of the AMD PDU to be transmitted to the receiving end [S66]. If the P field receives an AMD PDU set to "0", the receiving end considers that the transmitting end has not requested a transmission status report.

If the data to be transmitted to the receiving end is not stored in the transmission buffer 41, that is, if the transmission buffer 41 is empty, the AM RLC entity checks the status of the retransmission buffer 44 [S63] to confirm that it is to be transmitted Whether the data of the receiving end is stored in the retransmission buffer [S64]. When determining whether there is data to be transmitted to the receiving end in the retransmission buffer 44, the data blocks that have not received the retransmission request information from the receiving end are excluded. In other words, even if at least one RLC PDU is stored in the retransmission buffer 44, if at least one RLC PDU status report or confirmation is not received from the receiving end, the retransmission buffer 44 is considered to be empty.

In step S64, if the data to be transmitted to the receiving end is stored in the retransmission buffer 44, the AM RLC entity does not perform the inquiry procedure. That is, the AM RLC entity sets the P field to "0", where the P field exists in the header of the AMD PDU to be transmitted to the receiving end [S66].

If the data to be transmitted to the receiving end is not stored in the retransmission buffer 44, the AM RLC entity executes the inquiry procedure. That is, the AM RLC entity sets the P field to "1", where the P field exists in the header of the AMD PDU to be transmitted to the receiving end [S65]. If the P field receives an AMD PDU set to "1", the receiving end considers the transmitting end to request a transmission status report, and transmits the status report of at least one RLC PDU received from the transmitting end to the transmitting end.

In the specific embodiment shown in Fig. 6, although the status of the retransmission buffer is checked after the status of the transmission buffer is checked, the check sequence can be changed. That is, you can check the status of the transmission buffer after checking the retransmission buffer. In addition, the status of the transmission buffer and the status of the retransmission buffer can be checked at the same time.

FIG. 7 is a block diagram illustrating the specific embodiment of FIG. 6 from another perspective. In Figure 7, the horizontal axis is the time axis, and the vertical axis represents the amount of data stored in the transmission buffer and the retransmission buffer. Although the transmission buffer is empty at the time point "A", since the data to be transmitted to the receiving end is stored in the retransmission buffer, the inquiry procedure is not triggered. At time point "B", the data to be transmitted to the receiving end will not be retained in the transmission buffer and retransmission buffer. At this time, the AM RLC layer executes the inquiry procedure.

At time point "C", there is no data to be transmitted to the receiving end in the transmission buffer, but at least one RLC PDU is stored in the retransmission buffer. However, if the confirmation of at least one RLC PDU stored in the retransmission buffer is not received from the receiving end, it is considered that there is no data to be transmitted to the receiving end in the retransmission buffer. Correspondingly, the RLC AM entity even executes the interrogation procedure at the time point "C". Although the retransmission buffer is empty at the time point "D", since the data to be transmitted to the receiving end is stored in the transmission buffer, the RLC AM entity does not perform the inquiry procedure.

According to other specific embodiments of the present invention, in addition to the status of the transmission buffer and the status of the retransmission buffer, it is considered that the RLC AM entity also considers the sequence number of the RLC PDU to perform an inquiry procedure. That is, if the data to be sent to the receiving end is not reserved in the sending buffer and the re-sending buffer, in this state, the inquiry procedure can be executed for each of the following situations: 1. When the sending is stored in the re-sending buffer In the case of AMD PDU, the AMD PDU has the highest sequence number among the AMD PDUs to be retransmitted; 2. When transmitting the AMD PDU stored in the retransmission buffer, the AMD PDU is among the AMD PDUs that meet the following conditions The case with the highest sequence number: The status report of the AMD PDUs indicates that the receiving end has not successfully received the AMD PDUs; 3. When transmitting the AMD PDU stored in the retransmission buffer, the AMD PDU is to be transmitted again The AMD PDU is the latest situation; 4. When transmitting the AMD PDU stored in the retransmission buffer, the AMD PDU is the latest situation among the AMD PDUs that have received its NACK from the receiver; 5. When it is from When AMD PDU is transmitted in the transmission buffer, the AMD PDU is the latest situation; 6. When AMD PDU is transmitted from the transmission buffer PDU, the data to be transmitted to the receiving end is no longer retained in the transmission buffer and the transmission buffer; 7. When AMD PDU is transmitted from the transmission buffer, the data to be transmitted to the receiving end and the data to be transmitted again The AMD PDU is not reserved in the transmission buffer; 8. When the AMD PDU is transmitted from the transmission buffer, the data to be transmitted to the receiving end and the AMD PDU waiting to be transmitted again are not reserved in the transmission buffer Circumstances; 9. When AMD PDUs are transmitted from the transmission buffer, the data to be transmitted to the receiving end is no longer retained in the transmission buffer, and at the same time, the AMD PDUs that receive its NACK from the receiving end are not retained again The situation in the transmission buffer; 10. When AMD PDU is transmitted from the retransmission buffer, the AMD PDU has the highest sequence number among the AMD PDUs to be transmitted again, and the data to be transmitted to the receiving end is not retained in the transmission buffer The situation within; 11. When AMD PDU is transmitted from the retransmission buffer, the AMD PDU has the highest sequence number among the AMD PDUs that have received NACK from the receiving end, and the data to be transmitted to the receiving end is not reserved in the transmission buffer The situation within the area; and 12. When AMD PDU is transmitted from the retransmission buffer, the AMD PDU is the latest generation among the AMD PDUs to be transmitted again, and the data to be transmitted to the receiving end is not retained in the transmission buffer The situation within.

Figure 8 is a block diagram illustrating another specific embodiment of the present invention. In the specific embodiment in Figure 8, when the total amount of data included in the AMD PDU sent to the receiving end reaches the threshold, the AM RLC actually executes the inquiry procedure, and the threshold is preset.

Referring to Figure 8, assume that PDU 1 to PDU 5 are transmitted to the receiving end in a predetermined order. When PDU 5 is transmitted, the total amount of data transmitted to the receiving end reaches or exceeds a threshold. At this time, the AM RLC entity performs the inquiry procedure. That is, the AM RLC entity requests the receiving end to transmit the status report by setting the P field included in the header of the PDU 5 to "1".

If the interrogation procedure is executed once, the total amount of data used to trigger the interrogation procedure will be calculated again from the beginning. That is, in Figure 8, after the inquiry procedure is executed through PDU 5, since the total amount of data when transmitting PDU 6 to PDU 13 exceeds the threshold, the P field included in the header of PDU 13 is again Set to "1".

The specific embodiment shown in Fig. 8 can be achieved by using a parameter of BYTE_SENT. That is, BYTE_SENT is initially set to 0. As long as the AMD PDU is transmitted, the RLC AM entity increases the data size value included in the AM PDU to BYTE_SENT. When BYTE_SENT exceeds the threshold, the RLC AM entity sets the P field included in the header of the transmitted AM PDU to "1" to perform the inquiry procedure. If the inquiry procedure is executed, the RLC AM entity resets BYTE_SENT to "0" to repeat the same procedure.

If the size of the data included in the AMD PDU sent to the receiving end is added to BYTE_SENT, various methods can be considered regarding the value of the size of the data. As mentioned above, the AMD PDU includes a header part and a data field part, wherein the header part includes a fixed part and an extended part. Correspondingly, the total size of the AMD PDU, the size of the data field part, or the size of other parts of the header except the fixed part can be the part added to the value BYTE_SENT.

For example, when calculating the total size of the data, only the size of the data included in the data field part of the AMD PDU is considered, and the data field is aligned with each byte. Therefore, a counter can be incremented according to each byte in the data field included in each AMD PDU, and when the count value of the AMD PDU sent to the receiving end exceeds a predetermined threshold, an inquiry can be executed program.

The above-mentioned specific embodiments can be achieved by combining the structural elements and features of the present invention in a predetermined type. Unless otherwise specified, each of these structural elements or features can be selectively considered. Each of these structural elements or features can be implemented without being combined with other structural elements or features. In addition, some structural elements and/or features can be combined with each other to form specific embodiments of the present invention. The sequence of operations described in the specific embodiments of the present invention can be changed. Certain structural elements or features of a specific embodiment may be included in another specific embodiment, or may be replaced by corresponding structural elements or features of another specific embodiment. In addition, it is obvious that certain claims that refer to specific claims can be combined with claims that additionally refer to other claims other than those specific claims to form the specific embodiment, or by following the filing of this application Make corrections and add new request items.

The specific embodiments according to the present invention can be implemented in various ways, for example, hardware, firmware, software, or a combination thereof. If the specific embodiment according to the present invention is implemented by hardware, then the specific embodiment of the present invention can be implemented in the following ways: one or more application-specific integrated circuits (ASIC), digital signal processor (DSP), Digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, etc.

If the specific embodiment according to the present invention is implemented by firmware or software, then according to the specific embodiment of the present invention, the method of transmitting and receiving data in a wireless communication system can be implemented by one type of module, program, or function. The module, program, or function works or operates as described above. The software code can be stored in a memory unit, which can then be driven by the processor. The memory unit can be located inside or outside the processor to transmit data to or receive data from the processor through various well-known methods.

It will be obvious to those familiar with the art that the present invention can be embodied in other specific ways without departing from the spirit and essential characteristics of the present invention. Therefore, all aspects of the above-mentioned specific embodiments are considered to be illustrative rather than restrictive. The scope of the present invention can be determined by a reasonable interpretation of the scope of the attached patent application, and all changes belonging to the equivalent scope of the present invention are included in the scope of the invention.

<b><u style="single">Industrial application</u></b>

The present invention can be used in wireless communication systems, such as mobile communication systems or wireless Internet systems.

<p>41Transmit buffer</p><p>42Split/cascade module</p><p>43RLC header add module</p><p>44Retransmit buffer</p><p>45RLC control module</p><p>46Routing Module</p><p>47Receive buffer/HARQ reordering module</p><p>48RLC header removal module</p><p>49SDU reassembly module</p>

The accompanying drawings are included to provide a further understanding of the present invention, which are incorporated into this application and constitute a part of it. The drawings illustrate specific embodiments of the present invention and are used together with this description to explain the present invention The principle.

Figure 1 is a block diagram illustrating the network structure of E-UMTS (Evolved Global Mobile Telecommunications System); Figure 2 is a diagram illustrating E-UTRAN (Evolved Global Terrestrial Radio Access Network); Figure 3A Figures and 3B are block diagrams illustrating the structure of a radio interface protocol between a user equipment (UE) and E-UTRAN. Figure 3A is a schematic diagram of a control plane protocol, and Figure 3B is a user equipment A schematic diagram of a planar protocol; Figure 4 is a block diagram illustrating an example of the functional blocks of the RLC AM entity; Figure 5 is a block diagram illustrating a basic structure of an AMD PDU; Figure 6 is a block diagram illustrating the basis of the present invention A flowchart of a specific embodiment of the program; Fig. 7 is a block diagram illustrating the specific embodiment of Fig. 6 in another aspect; and Fig. 8 is a block diagram illustrating another specific embodiment of the present invention picture.

Method for executing inquiry program in wireless communication system