WO2008066347A1 - Hierarchical header format and data transmission method in communication system - Google Patents

Hierarchical header format and data transmission method in communication system Download PDF

Info

Publication number
WO2008066347A1
WO2008066347A1 PCT/KR2007/006140 KR2007006140W WO2008066347A1 WO 2008066347 A1 WO2008066347 A1 WO 2008066347A1 KR 2007006140 W KR2007006140 W KR 2007006140W WO 2008066347 A1 WO2008066347 A1 WO 2008066347A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
information
data packet
fragmentation block
service
Prior art date
Application number
PCT/KR2007/006140
Other languages
French (fr)
Inventor
Geon-Min Yeo
Kang-Hee Kim
Byung-Han Ryu
Original Assignee
Electronics And Telecommunications Research Institute
Samsung Electronics.Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020070097549A external-priority patent/KR100896507B1/en
Application filed by Electronics And Telecommunications Research Institute, Samsung Electronics.Co., Ltd. filed Critical Electronics And Telecommunications Research Institute
Publication of WO2008066347A1 publication Critical patent/WO2008066347A1/en
Priority to US12/474,922 priority Critical patent/US20090232161A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1887Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/16Implementing security features at a particular protocol layer
    • H04L63/162Implementing security features at a particular protocol layer at the data link layer

Definitions

  • the present invention relates to a hierarchical header format and a data transmission method in a communication system.
  • ACR automatic repeat request
  • the ARQ method is a method in which, when a receiver fails to receive predetermined data from a transmitter or fails to decode the data, the failure is notified to the transmitter so that the transmitter may transmit the data again.
  • the transmitter divides a service data unit (SDU) of a medium access control (MAC) protocol into ARQ blocks and transmits the same to the receiver.
  • the receiver notifies the transmitter of the receiving status of the respective ARQ blocks.
  • the transmitter and the receiver must identify the transmitted blocks because it is possible to know which blocks the receiver has received and whether the receiver will request an ARQ for a predetermined block when they have identified the blocks.
  • a block sequence number for identifying the transmitted blocks is applied to the respective blocks.
  • the ARQ method transmits data in a fixed manner according to a predetermined transmission amount, radio resources may be wasted when there is not a large amount of transmitted data.
  • the present invention has been made in an effort to provide a header format for efficiently using radio resources and processing data at a high data rate in the case of transmitting data between layers in a communication system.
  • a method for transmitting data between layers in a communication system includes: determining a transmission method for a service packet according to quality of service (QoS) of the service packet; determining a transmission amount of the service packet according to the transmission method; fragmentizing and concatenating the service packet according to the transmission amount and generating at least one fragmentation block; generating a data packet including the at least one fragmentation block and information on the at least one fragmentation block; inserting information on the number of fragmentation blocks into the data packet; and transmitting the data packet.
  • QoS quality of service
  • the determining of a transmission method for a service packet includes selecting one of a transparent mode, an acknowledged mode, and an unacknowledged mode depending on the QoS requested by the service packet.
  • a method for generating a data packet includes: fragmentizing and concatenating a service packet of an upper layer according to a transmission amount of a service packet, and generating at least one fragmentation block; inserting at least one fragmentation block information field corresponding to the at least one fragmentation block into the data packet; inserting the at least one fragmentation block into the data packet; and inserting information on the data packet into the data packet.
  • a method for generating a transmission block includes: determining a transmission method for a service packet according to a quality of service (QoS) of the service packet; fragmentizing and concatenating the service packet according to a transmission amount of the service packet, and generating a fragmentation block; generating a data packet including the fragmentation block and information on the fragmentation block; generating a control packet for controlling data transmission according to the transmission method; generating the transmission block including the at least one data packet and the control packet; and inserting information on the transmission block into the transmission block.
  • QoS quality of service
  • FIG. 1 is a block diagram for a communication system according to an exemplary embodiment of the present invention.
  • FIG. 2 is a flowchart for a data transmission method by an ARQ controller according to an exemplary embodiment of the present invention.
  • FIG. 3 is a configuration of a TB of a MAC layer and a header field of the TB according to an exemplary embodiment of the present invention.
  • FIG. 4 and FIG. 5 show a first type and a second type of RLC PDU of a pay load field of a TB according to an exemplary embodiment of the present invention.
  • FIG. 6 shows an RLC information field of an RLC PDU of a TB according to an exemplary embodiment of the present invention.
  • FIG. 7 and FIG. 8 show a first type and a second type of FB information field of an
  • FIG. 9 shows a configuration of an RLC control PDU according to an exemplary embodiment of the present invention. Mode for the Invention
  • FIG. 1 is a block diagram for a communication system 100 according to an exemplary embodiment of the present invention.
  • the communication system 100 includes a terminal information storage unit 110, a packet controller 115, and a scheduler/control protocol data unit (PDU) collector 117, and the terminal information storage unit 110 includes a buffer 111 and an ARQ controller 113.
  • PDU scheduler/control protocol data unit
  • the buffer 111 of the terminal information storage unit 110 receives an SDU from an upper layer and temporarily stores the SDU.
  • the ARQ controller 113 includes functions of a general radio link control (RLC) layer including a retransmission function for providing great data accuracy. Also, the ARQ controller 113 determines a data transmission mode based on the QoS of an SDU 200 stored in the buffer 111.
  • the data transmission mode includes a transparent mode, an acknowledged mode, and an unacknowledged mode.
  • the transparent mode is generated when the ARQ controller 113 provides no overhead to the FB that is transmitted by an upper layer when generating an RLC PDU. Hence, the transparent mode is appropriate for services that have great requirements on the real-time transmission.
  • the acknowledged mode is generated when the ARQ controller 113 adds a PDU header including a sequence number (SN) to the payload of the PDU when generating the PDU, and a receiver responds to the PDU transmitted by a transmitter. The response is provided so that the receiver may request the transmitter to retransmit the PDU that is not received by the receiver. Since the acknowledged mode guarantees data transmission without an error, the acknowledged mode is appropriate for the services that have a low requirement for the real-time transmission and have a great requirement for the data accuracy.
  • SN sequence number
  • the unacknowledged mode allows the receiver to know which PDU is lost during transmission since the ARQ controller 113 of the transmitter adds a PDU header including a sequence number to each PDU and transmits the PDU. Therefore, the unacknowledged mode is appropriate for the service that has requirements for the realtime transmission and the packet sequence.
  • the packet controller 115 collects various RLC control PDUs through the scheduler/ control PDU collector 117 according to the data transmission mode determined by the ARQ controller 113, and transmits the collected RLC control PDUs to a MAC layer 120 and the ARQ controller 113 by considering the resource allocation condition and using scheduler-based allocation, piggybagging, or indication bit insertion.
  • the MAC layer 120 receives an RLC data PDU from the ARQ controller 113, receives an RLC control PDU from the packet controller 115, multiplexes them to configure a transport block (TB) 300 that is appropriate for the radio channel, and transmits the transport block to the physical layer 130.
  • TB transport block
  • the TB 300 is configured to provide the hybrid ARQ (HARQ) and multi-input multi-output (MIMO) of the physical layer.
  • HARQ hybrid ARQ
  • MIMO multi-input multi-output
  • FIG. 2 is a flowchart for a data transmission method by an ARQ controller according to an exemplary embodiment of the present invention.
  • the ARQ controller determines the data transmission mode according to the QoS of the SDU stored in the buffer (Sl 10), and determines the transmission amount of the service packets according to the determined data transmission mode (S 120).
  • the ARQ controller 113 fragmentizes and concatenates the SDU depending on the data transmission amount determined by a scheduler according to the data transmission method, and generates a fragmentation block (FB) (S 130).
  • FB fragmentation block
  • the ARQ controller 113 generates a PDU including the generated FB and information on the FB (S 140), and adds radio link control information including a PDU retransmission method and the number of fragmentation blocks included in the PDU to the generated PDU to thus generate an RLC data PDU.
  • the ARQ controller 113 transmits the generated RLC data PDU to the MAC layer
  • FIG. 3 is a configuration of a TB of a MAC layer and a header field of the TB according to an exemplary embodiment of the present invention.
  • the TB 300 that is transmitted from the MAC layer 120 to the physical layer 130 includes a MAC header field and a pay load field, and the pay load field includes at least one RLC PDU 320.
  • each RLC PDU 320 is an RLC control PDU or an RLC data PDU.
  • the MAC header field 310 includes one number field 311 and at least one size field
  • the number field 311 indicates the number of RLC PDUs 320 included by the TB 300
  • the at least one size field 313 indicates the size of the at least one RLC PDU 320 included by the TB 300.
  • the TB 300 may not have the MAC header field 310.
  • FIG. 4 and FIG. 5 show a first type and a second type of RLC PDU of a payload field of a TB according to an exemplary embodiment of the present invention.
  • the first type of RLC PDU 320 includes an RLC header field and an RLC payload field
  • the RLC header field includes an RLC information field 321 and an FB information field 323
  • the RLC payload field includes at least one FB 325.
  • the FB information field 323 includes information on each of the FBs 325 included by the RLC payload field.
  • the second type of RLC PDU 320 includes an RLC information field 321, at least one FB information field 323, and at least one FB 325 corresponding to at least one FB information field 323.
  • the FB information field 323 of the second type of RLC PDU field 320 includes information on the FB 325 provided next to the FB information field 323.
  • FIG. 6 shows an RLC information field of an RLC PDU of a TB according to an exemplary embodiment of the present invention.
  • the RLC information field 321 includes a type field 321a, a link identifier field 321b, and a sequence number field 321c, and further includes a piggybagging indicator field 321d, an end of buffer (EOB) indicator field 321e, and an FB number field 321f.
  • the type field 321a displays the type of RLC PDU, and includes information for processing to the packet controller, the ARQ, or other layers. Also, the type field 321a displays whether the RLC PDU 320 is a data PDU or a control PDU.
  • the link identifier field 321b identifies the link to which the RLC PDU 320 belongs in the case of requesting to retransmit the RLC PDU 320, and is an identifier of the corresponding link for operating the ARQ.
  • the sequence number field 321c indicates a sequence number that is allocated for the
  • the piggybagging indicator field 32 Id indicates that a control PDU is included in the
  • the EOB indicator field 32 Ie notifies that the buffer has no more SDU to be transmitted to the lower layer from the upper layer.
  • the FB number field 321f indicates the entire number of FBs included in the RLC
  • the information of the RLC information field 321 can limit the number of bits in consideration of byte-based operation in the realized structure of a high data rate system.
  • the type field 321a is configured to have 3 bits
  • the link identifier field 321b is configured to have 4 bits
  • the piggybagging indicator field 321d is configured to have 1 bit
  • the sequence number field 321c is configured to have 11 bits
  • the EOB indicator field 32 Ie is configured to have 1 bit
  • FIG. 7 and FIG. 8 show a first type and a second type of FB information fields of an
  • the first type of FB information field 323 includes a fragmentation control (FC) field 323a, a starting pointer (SP) field 323b, and an ending pointer (EP) field 323c, and further includes an extension indicator (E) field 323d.
  • FC fragmentation control
  • SP starting pointer
  • EP ending pointer
  • E extension indicator
  • the FC field 323a includes fragmentation information on the SDU of a first part, a middle part, and a last part included in the FB, and other control information.
  • the SP field 323b indicates starting pointer information on the FB included in the
  • RLC PDU 320 indicates the ending pointer of the FB included in the RLC PDU 320.
  • the E field 323d is an indicator for notifying an existence of an additional FB when the RLC PDU 320 has the additional FB.
  • 2 FB information field 323 includes a length field 323e and further includes an E field 323d.
  • the length field 323c indicates the length of the FB, that is, the length of the SDU
  • the E field 323d is an indicator of existence of an additional FB when the RLC PDU 320 has an additional FB.
  • FIG. 9 shows a configuration of an RLC control PDU according to an exemplary embodiment of the present invention.
  • the RLC control PDU 320 includes an RLC information field
  • the RLC information field 327 includes a type field 327a and a message identifier field 327b, and may further include a link identifier field 327c.
  • the type field 327a indicates the type of the RLC control PDU 320, and includes information on processing for the packet controller, the ARQ controller, or other layers.
  • the type field 327a can indicate whether the RLC PDU 320 is an RLC data PDU or an RLC control PDU.
  • the message identifier field 327b includes a transmitting object and a receiving object of the RLC control PDU 320.
  • the link identifier field 327c is an identifier for identifying the link to which the
  • RLC PDU 320 belongs in the case of requesting the receiver to retransmit the RLC PDU 320, and is an identifier of the corresponding link for operating the ARQ.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

In order to transmit data between layers in a communication system, an ARQ controller determines a transmission method of a service packet according to QoS of the service packet of an upper layer, determines a retransmission method of the service packet according to the transmission method, generates a fragmentation block by fragmentizing and concatenating the service packet according to a transmission amount of the service packet determined by the transmission method, generates a data packet including the fragmentation block and fragmentation block information, adds radio link control information including the retransmission method to the data packet to generate a radio link control data packet, and transmits the radio link control data packet to a MAC layer.

Description

Description
HIERARCHICAL HEADER FORMAT AND DATA TRANSMISSION METHOD IN COMMUNICATION SYSTEM
Technical Field
[1] The present invention relates to a hierarchical header format and a data transmission method in a communication system.
[2] This work was supported by the IT R&D program of MIC/IITA [2005-S-404- 12,
Research & Development of Radio Transmission Technology for 3G Evolution]. Background Art
[3] Communication systems require security of transmitted data. The security is more important in wireless communication systems than wired communication systems. The security is a function for preventing transmitted data from being lost or damaged. Various methods are used so as to prevent loss or damage in transmitted data in communication systems. One of the methods is the automatic repeat request (ARQ) method. The ARQ method is a method in which, when a receiver fails to receive predetermined data from a transmitter or fails to decode the data, the failure is notified to the transmitter so that the transmitter may transmit the data again.
[4] The transmitter divides a service data unit (SDU) of a medium access control (MAC) protocol into ARQ blocks and transmits the same to the receiver. The receiver notifies the transmitter of the receiving status of the respective ARQ blocks. In this instance, the transmitter and the receiver must identify the transmitted blocks because it is possible to know which blocks the receiver has received and whether the receiver will request an ARQ for a predetermined block when they have identified the blocks. In order to identify the respective blocks, a block sequence number for identifying the transmitted blocks is applied to the respective blocks.
[5] However, since the ARQ method transmits data in a fixed manner according to a predetermined transmission amount, radio resources may be wasted when there is not a large amount of transmitted data.
[6] The above information disclosed in this Background section is only for enhancement of understanding of the background of the invention and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Disclosure of Invention Technical Problem
[7] The present invention has been made in an effort to provide a header format for efficiently using radio resources and processing data at a high data rate in the case of transmitting data between layers in a communication system. Technical Solution
[8] In one aspect of the present invention, a method for transmitting data between layers in a communication system includes: determining a transmission method for a service packet according to quality of service (QoS) of the service packet; determining a transmission amount of the service packet according to the transmission method; fragmentizing and concatenating the service packet according to the transmission amount and generating at least one fragmentation block; generating a data packet including the at least one fragmentation block and information on the at least one fragmentation block; inserting information on the number of fragmentation blocks into the data packet; and transmitting the data packet.
[9] The determining of a transmission method for a service packet includes selecting one of a transparent mode, an acknowledged mode, and an unacknowledged mode depending on the QoS requested by the service packet.
[10] In another aspect of the present invention, a method for generating a data packet includes: fragmentizing and concatenating a service packet of an upper layer according to a transmission amount of a service packet, and generating at least one fragmentation block; inserting at least one fragmentation block information field corresponding to the at least one fragmentation block into the data packet; inserting the at least one fragmentation block into the data packet; and inserting information on the data packet into the data packet.
[11] In another aspect of the present invention, a method for generating a transmission block includes: determining a transmission method for a service packet according to a quality of service (QoS) of the service packet; fragmentizing and concatenating the service packet according to a transmission amount of the service packet, and generating a fragmentation block; generating a data packet including the fragmentation block and information on the fragmentation block; generating a control packet for controlling data transmission according to the transmission method; generating the transmission block including the at least one data packet and the control packet; and inserting information on the transmission block into the transmission block.
[12] According to the exemplary embodiments of the present invention, it is possible to efficiently use the radio resource and efficiently process data with a high data rate by using the hierarchical header format. Brief Description of the Drawings
[13] FIG. 1 is a block diagram for a communication system according to an exemplary embodiment of the present invention.
[14] FIG. 2 is a flowchart for a data transmission method by an ARQ controller according to an exemplary embodiment of the present invention.
[15] FIG. 3 is a configuration of a TB of a MAC layer and a header field of the TB according to an exemplary embodiment of the present invention.
[16] FIG. 4 and FIG. 5 show a first type and a second type of RLC PDU of a pay load field of a TB according to an exemplary embodiment of the present invention.
[17] FIG. 6 shows an RLC information field of an RLC PDU of a TB according to an exemplary embodiment of the present invention.
[18] FIG. 7 and FIG. 8 show a first type and a second type of FB information field of an
RLC PDU of a TB according to an exemplary embodiment of the present invention.
[19] FIG. 9 shows a configuration of an RLC control PDU according to an exemplary embodiment of the present invention. Mode for the Invention
[20] In the following detailed description, only certain exemplary embodiments of the present invention have been shown and described, simply by way of illustration. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. Accordingly, the drawings and description are to be regarded as illustrative in nature and not restrictive. Like reference numerals designate like elements throughout the specification.
[21] Throughout this specification and the claims which follow, unless explicitly described to the contrary, the word "comprising" and variations such as "comprises" will be understood to imply the inclusion of stated elements but not the exclusion of any other elements. Also, the terms "unit", "device", and "module" in the present specification represent a unit for processing a predetermined function or operation, which can be realized by hardware, software, or a combination of hardware and software.
[22] A hierarchical header format and a data transmission method in a communication system according to an exemplary embodiment of the present invention will be described.
[23] FIG. 1 is a block diagram for a communication system 100 according to an exemplary embodiment of the present invention.
[24] As shown in FIG. 1, the communication system 100 includes a terminal information storage unit 110, a packet controller 115, and a scheduler/control protocol data unit (PDU) collector 117, and the terminal information storage unit 110 includes a buffer 111 and an ARQ controller 113.
[25] The buffer 111 of the terminal information storage unit 110 receives an SDU from an upper layer and temporarily stores the SDU.
[26] The ARQ controller 113 includes functions of a general radio link control (RLC) layer including a retransmission function for providing great data accuracy. Also, the ARQ controller 113 determines a data transmission mode based on the QoS of an SDU 200 stored in the buffer 111. Here, the data transmission mode includes a transparent mode, an acknowledged mode, and an unacknowledged mode.
[27] The transparent mode is generated when the ARQ controller 113 provides no overhead to the FB that is transmitted by an upper layer when generating an RLC PDU. Hence, the transparent mode is appropriate for services that have great requirements on the real-time transmission.
[28] The acknowledged mode is generated when the ARQ controller 113 adds a PDU header including a sequence number (SN) to the payload of the PDU when generating the PDU, and a receiver responds to the PDU transmitted by a transmitter. The response is provided so that the receiver may request the transmitter to retransmit the PDU that is not received by the receiver. Since the acknowledged mode guarantees data transmission without an error, the acknowledged mode is appropriate for the services that have a low requirement for the real-time transmission and have a great requirement for the data accuracy.
[29] The unacknowledged mode allows the receiver to know which PDU is lost during transmission since the ARQ controller 113 of the transmitter adds a PDU header including a sequence number to each PDU and transmits the PDU. Therefore, the unacknowledged mode is appropriate for the service that has requirements for the realtime transmission and the packet sequence.
[30] The packet controller 115 collects various RLC control PDUs through the scheduler/ control PDU collector 117 according to the data transmission mode determined by the ARQ controller 113, and transmits the collected RLC control PDUs to a MAC layer 120 and the ARQ controller 113 by considering the resource allocation condition and using scheduler-based allocation, piggybagging, or indication bit insertion.
[31] The MAC layer 120 receives an RLC data PDU from the ARQ controller 113, receives an RLC control PDU from the packet controller 115, multiplexes them to configure a transport block (TB) 300 that is appropriate for the radio channel, and transmits the transport block to the physical layer 130.
[32] Here, the TB 300 is configured to provide the hybrid ARQ (HARQ) and multi-input multi-output (MIMO) of the physical layer.
[33] FIG. 2 is a flowchart for a data transmission method by an ARQ controller according to an exemplary embodiment of the present invention.
[34] As shown in FIG. 2, the ARQ controller (113 of FIG. 1) determines the data transmission mode according to the QoS of the SDU stored in the buffer (Sl 10), and determines the transmission amount of the service packets according to the determined data transmission mode (S 120). [35] The ARQ controller 113 fragmentizes and concatenates the SDU depending on the data transmission amount determined by a scheduler according to the data transmission method, and generates a fragmentation block (FB) (S 130).
[36] The ARQ controller 113 generates a PDU including the generated FB and information on the FB (S 140), and adds radio link control information including a PDU retransmission method and the number of fragmentation blocks included in the PDU to the generated PDU to thus generate an RLC data PDU.
[37] The ARQ controller 113 transmits the generated RLC data PDU to the MAC layer
(S150).
[38] FIG. 3 is a configuration of a TB of a MAC layer and a header field of the TB according to an exemplary embodiment of the present invention.
[39] As shown in FIG. 3, the TB 300 that is transmitted from the MAC layer 120 to the physical layer 130 includes a MAC header field and a pay load field, and the pay load field includes at least one RLC PDU 320. Here, each RLC PDU 320 is an RLC control PDU or an RLC data PDU.
[40] The MAC header field 310 includes one number field 311 and at least one size field
313, and the number field 311 indicates the number of RLC PDUs 320 included by the TB 300, and the at least one size field 313 indicates the size of the at least one RLC PDU 320 included by the TB 300.
[41 ] Here, the TB 300 may not have the MAC header field 310.
[42] FIG. 4 and FIG. 5 show a first type and a second type of RLC PDU of a payload field of a TB according to an exemplary embodiment of the present invention.
[43] As shown in FIG. 4, the first type of RLC PDU 320 includes an RLC header field and an RLC payload field, the RLC header field includes an RLC information field 321 and an FB information field 323, and the RLC payload field includes at least one FB 325. The FB information field 323 includes information on each of the FBs 325 included by the RLC payload field.
[44] As shown in FIG. 5, the second type of RLC PDU 320 includes an RLC information field 321, at least one FB information field 323, and at least one FB 325 corresponding to at least one FB information field 323. The FB information field 323 of the second type of RLC PDU field 320 includes information on the FB 325 provided next to the FB information field 323.
[45] FIG. 6 shows an RLC information field of an RLC PDU of a TB according to an exemplary embodiment of the present invention.
[46] As shown in FIG. 6, the RLC information field 321 includes a type field 321a, a link identifier field 321b, and a sequence number field 321c, and further includes a piggybagging indicator field 321d, an end of buffer (EOB) indicator field 321e, and an FB number field 321f. [47] The type field 321a displays the type of RLC PDU, and includes information for processing to the packet controller, the ARQ, or other layers. Also, the type field 321a displays whether the RLC PDU 320 is a data PDU or a control PDU.
[48] The link identifier field 321b identifies the link to which the RLC PDU 320 belongs in the case of requesting to retransmit the RLC PDU 320, and is an identifier of the corresponding link for operating the ARQ.
[49] The sequence number field 321c indicates a sequence number that is allocated for the
ARQ operation to the FB 325.
[50] The piggybagging indicator field 32 Id indicates that a control PDU is included in the
TB 325 in the piggybagging format so as to increase the data transmission efficiency according to the determination of the MAC layer.
[51] The EOB indicator field 32 Ie notifies that the buffer has no more SDU to be transmitted to the lower layer from the upper layer.
[52] The FB number field 321f indicates the entire number of FBs included in the RLC
PDU 320 when the number of FBs included in the RLC PDU 320 is plural. The information of the RLC information field 321 can limit the number of bits in consideration of byte-based operation in the realized structure of a high data rate system. For example, the type field 321a is configured to have 3 bits, the link identifier field 321b is configured to have 4 bits, the piggybagging indicator field 321d is configured to have 1 bit, the sequence number field 321c is configured to have 11 bits, the EOB indicator field 32 Ie is configured to have 1 bit, and the FB number field 32 If is configured to have 4 bits.
[53] FIG. 7 and FIG. 8 show a first type and a second type of FB information fields of an
RLC PDU of a TB according to an exemplary embodiment of the present invention.
[54] As shown in FIG. 7, the first type of FB information field 323 includes a fragmentation control (FC) field 323a, a starting pointer (SP) field 323b, and an ending pointer (EP) field 323c, and further includes an extension indicator (E) field 323d.
[55] The FC field 323a includes fragmentation information on the SDU of a first part, a middle part, and a last part included in the FB, and other control information.
[56] The SP field 323b indicates starting pointer information on the FB included in the
RLC PDU 320, and the EP field 323c indicates the ending pointer of the FB included in the RLC PDU 320.
[57] The E field 323d is an indicator for notifying an existence of an additional FB when the RLC PDU 320 has the additional FB.
[58] As shown in FIG. 8, when one FB includes an SDU that is not fragmentized, the type
2 FB information field 323 includes a length field 323e and further includes an E field 323d.
[59] Here, the length field 323c indicates the length of the FB, that is, the length of the SDU, and the E field 323d is an indicator of existence of an additional FB when the RLC PDU 320 has an additional FB.
[60] FIG. 9 shows a configuration of an RLC control PDU according to an exemplary embodiment of the present invention.
[61] As shown in FIG. 9, the RLC control PDU 320 includes an RLC information field
327 and a message field 329.
[62] The RLC information field 327 includes a type field 327a and a message identifier field 327b, and may further include a link identifier field 327c.
[63] The type field 327a indicates the type of the RLC control PDU 320, and includes information on processing for the packet controller, the ARQ controller, or other layers. Here, the type field 327a can indicate whether the RLC PDU 320 is an RLC data PDU or an RLC control PDU.
[64] The message identifier field 327b includes a transmitting object and a receiving object of the RLC control PDU 320.
[65] The link identifier field 327c is an identifier for identifying the link to which the
RLC PDU 320 belongs in the case of requesting the receiver to retransmit the RLC PDU 320, and is an identifier of the corresponding link for operating the ARQ.
[66] The above-described embodiments can be realized through a program for realizing functions corresponding to the configuration of the embodiments or a recording medium for recording the program in addition to through the above-described device and/or method, which is easily realized by a person skilled in the art.
[67] While this invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

Claims
[1] A method for transmitting data between layers in a communication system, the method comprising: determining a transmission method for a service packet according to a quality of service (QoS) of the service packet; determining a transmission amount of the service packet according to the transmission method; fragmentizing and concatenating the service packet according to the transmission amount to generate at least one fragmentation block; generating a data packet including the at least one fragmentation block and information on the at least one fragmentation block; inserting information on the number of the at least one fragmentation blocks into the data packet; and transmitting the data packet.
[2] The method of claim 1, wherein the determining of the transmission method for the service packet comprises: selecting one of a transparent mode, an acknowledged mode, and an unacknowledged mode depending on the QoS requested by the service packet.
[3] A method for generating a data packet comprising: fragmentizing and concatenating a service packet of an upper layer according to a transmission amount of a service packet, to generate at least one fragmentation block; inserting at least one fragmentation block information field each corresponding to the at least one fragmentation block into the data packet; inserting the at least one fragmentation block into the data packet; and inserting information on the data packet into the data packet.
[4] The method of claim 3, wherein the inserting of the at least one fragmentation block into the data packet comprises: inserting the at least one fragmentation block into the data packet after the at least one fragmentation block information field.
[5] The method of claim 3, wherein the inserting of the at least one fragmentation block into the data packet comprises: inserting the corresponding fragmentation block into the data packet after the at least one fragmentation block information field.
[6] The method of claim 3, wherein the inserting of the at least one fragmentation block information field each corresponding to the at least one fragmentation block into the data packet comprises: when each of the at least one fragmentation block includes a plurality of service packets, inserting fragmentation information of the plurality of service packets included in the fragmentation block into the fragmentation block information field, and inserting location information for indicating the insertion location of the fragmentation block at the data packet into the fragmentation block information field.
[7] The method of claim 3, wherein the inserting of the at least one fragmentation block information field each corresponding to the at least one fragmentation block into the data packet comprises: when each of the at least one fragmentation block includes a service packet, inserting the length of the service packet into the fragmentation block information field.
[8] The method of claim 7, further comprising: inserting information for indicating that an additional fragmentation block in addition to the fragmentation block is provided in the data packet into the fragmentation block information field.
[9] The method of claim 3, wherein the inserting of the data packet information into the data packet comprises: inserting an order for inserting at least one fragmentation block included in the data packet into the data packet into information on the data packet; inserting an identifier for identifying a corresponding link into the information on the data packet when a receiver requests to retransmit the data packet; and inserting type information for processing the data packet to another layer into the information on the data packet.
[10] The method of claim 9, further comprising: inserting the number of fragmentation blocks included in the data packet into the information on the data packet; inserting an indicator for notifying that there are no more service packets to be transmitted to the lower layer into the information on the data packet; and inserting an indicator for indicating that a control packet for controlling data transmission of the service packet is a piggybag format into the data packet information.
[11] A method for generating a transmission block, comprising: determining a transmission method for a service packet according to a quality of service (QoS) of the service packet; fragmentizing and concatenating the service packet according to a transmission amount of the service packet, to generate a fragmentation block; generating a data packet including the fragmentation block and information on the fragmentation block; generating a control packet for controlling data transmission according to the transmission method; generating the transmission block including the at least one data packet and the control packet; and inserting information on the transmission block into the transmission block. [12] The method of claim 11, wherein the generating of a control packet for controlling data transmission according to the transmission method comprises: inserting a control message for controlling data transmission of the service packet into the control packet; and inserting information on the control message into the control packet. [13] The method of claim 12, wherein the inserting of information on the control message into the control packet comprises: inserting an identifier for identifying the link to which the control packet belongs into the information on the control message; inserting an identifier for identifying the control message into information on the control message; and inserting type information for processing the control packet to another layer into the information on the control message.
PCT/KR2007/006140 2006-12-01 2007-11-30 Hierarchical header format and data transmission method in communication system WO2008066347A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/474,922 US20090232161A1 (en) 2006-12-01 2009-05-29 Hierarchical header format and data transmission method in communication system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2006-0120599 2006-12-01
KR20060120599 2006-12-01
KR10-2007-0097549 2007-09-27
KR1020070097549A KR100896507B1 (en) 2006-12-01 2007-09-27 Hierachical Header Format and Method of data transmission for Communication System

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/474,922 Continuation US20090232161A1 (en) 2006-12-01 2009-05-29 Hierarchical header format and data transmission method in communication system

Publications (1)

Publication Number Publication Date
WO2008066347A1 true WO2008066347A1 (en) 2008-06-05

Family

ID=39468081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/006140 WO2008066347A1 (en) 2006-12-01 2007-11-30 Hierarchical header format and data transmission method in communication system

Country Status (1)

Country Link
WO (1) WO2008066347A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036305A (en) * 2009-09-30 2011-04-27 华为技术有限公司 Transmitting method and receiving method of control information, devices and communication system
WO2014147140A1 (en) * 2013-03-20 2014-09-25 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Two-stage signaling for transmission of a datastream

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030061415A1 (en) * 2001-09-24 2003-03-27 Horton John D. System and method for hardware based reassembly of a fragmented packet
US6683866B1 (en) * 1999-10-29 2004-01-27 Ensemble Communications Inc. Method and apparatus for data transportation and synchronization between MAC and physical layers in a wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6683866B1 (en) * 1999-10-29 2004-01-27 Ensemble Communications Inc. Method and apparatus for data transportation and synchronization between MAC and physical layers in a wireless communication system
US20030061415A1 (en) * 2001-09-24 2003-03-27 Horton John D. System and method for hardware based reassembly of a fragmented packet
US20040221074A1 (en) * 2001-09-24 2004-11-04 Horton John D. System and method for hardware based reassembly of a fragmented packet

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036305A (en) * 2009-09-30 2011-04-27 华为技术有限公司 Transmitting method and receiving method of control information, devices and communication system
US9124411B2 (en) 2009-09-30 2015-09-01 Huawei Technologies Co., Ltd. Method for sending and receiving control information, apparatus and communication system
US9220097B2 (en) 2009-09-30 2015-12-22 Huawei Technologies Co., Ltd. Method for sending and receiving control information, apparatus and communication system
US9544894B2 (en) 2009-09-30 2017-01-10 Huawei Technologies Co., Ltd. Method for sending and receiving control information, apparatus and communication system
US9872288B2 (en) 2009-09-30 2018-01-16 Huawei Technologies Co., Ltd. Method for sending and receiving control information, apparatus and communication system
US10334583B2 (en) 2009-09-30 2019-06-25 Huawei Technologies Co., Ltd. Method for sending and receiving control information, apparatus and communication system
WO2014147140A1 (en) * 2013-03-20 2014-09-25 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Two-stage signaling for transmission of a datastream
KR101795198B1 (en) 2013-03-20 2017-11-07 프라운호퍼 게젤샤프트 쭈르 푀르데룽 데어 안겐반텐 포르슝 에. 베. Two-stage signaling for transmission of a datastream
US10057013B2 (en) 2013-03-20 2018-08-21 Fraunhofer-Gesellschaft Zur Foerderung Der Angewandten Forschung E.V. Two-stage signaling for transmission of a datastream
CN110324113A (en) * 2013-03-20 2019-10-11 弗劳恩霍夫应用研究促进协会 For handling the method and receiver that correspond to the reception signal of data flow
CN110324113B (en) * 2013-03-20 2023-04-07 弗劳恩霍夫应用研究促进协会 Method for processing a received signal corresponding to a data stream and receiver

Similar Documents

Publication Publication Date Title
US11082885B2 (en) Method and apparatus for transmitting and receiving status report comprising received status of packet data in a mobile communication system
US20220201743A1 (en) Method for scheduling in mobile communication and apparatus thereof
US10530431B2 (en) Method and apparatus in a wireless communication system
US10396942B2 (en) Method and apparatus for transmitting and receiving data in a communication system
US9100965B2 (en) Apparatus and method for multiplexing data of a layer into data transmission unit of another layer
US8270348B2 (en) Method for sending status information in mobile telecommunications system and receiver of mobile telecommunications
US9397791B2 (en) Transmitting data in a mobile communication system
EP2094049B1 (en) Method and apparatus for sending RLC PDU in a mobile communications system
US20180368166A1 (en) User equipment and method to support data preprocessing
US20090319850A1 (en) Local drop control for a transmit buffer in a repeat transmission protocol device
US7729665B2 (en) Down-link data transmission and receiving system and method of ARQ in wireless communication system
JP5215413B2 (en) Status report for retransmission protocol
AU2009209739A1 (en) Method for sending status information in mobile telecommunications system and receiver of mobile telecommunications
US20090323605A1 (en) Base station, mobile station, and communication method
US8306059B2 (en) Method of constructing and transmitting packets with MIMO configuration in a wireless communication system and related communication device
US20070249343A1 (en) Method and system of communications
CN103716141A (en) Signal transmission method and apparatus for user equipment in mobile communication system
JP2009534917A (en) Method, communication entity, and system for transmitting positive acknowledgment and negative acknowledgment in a wireless communication system
WO2008066347A1 (en) Hierarchical header format and data transmission method in communication system
US20090232161A1 (en) Hierarchical header format and data transmission method in communication system
EP2026492B1 (en) Radio apparatus, radio communication system, and radio information notification method
KR100631742B1 (en) AC frame transmission method and device
Tykhomyrov et al. Analysis and performance evaluation of the IEEE 802.16 ARQ mechanism
WO2024028277A1 (en) Infrastructure equipment, communications devices and methods

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07834418

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07834418

Country of ref document: EP

Kind code of ref document: A1