WO2008004724A1 - Procédé efficace de réinitialisation am rlc - Google Patents

Procédé efficace de réinitialisation am rlc Download PDF

Info

Publication number
WO2008004724A1
WO2008004724A1 PCT/KR2006/004378 KR2006004378W WO2008004724A1 WO 2008004724 A1 WO2008004724 A1 WO 2008004724A1 KR 2006004378 W KR2006004378 W KR 2006004378W WO 2008004724 A1 WO2008004724 A1 WO 2008004724A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
establishment
control
rlc
reset
Prior art date
Application number
PCT/KR2006/004378
Other languages
English (en)
Inventor
Sung-Duck Chun
Young-Dae Lee
Myung-Cheul Jung
Sung-Jun Park
Original Assignee
Lg Electronics Inc.
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 KR1020060063133A external-priority patent/KR100905965B1/ko
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Priority to CN2006800552354A priority Critical patent/CN101479965B/zh
Priority to US12/307,239 priority patent/US8681712B2/en
Publication of WO2008004724A1 publication Critical patent/WO2008004724A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management

Definitions

  • the present invention relates to an operation method of an AM RLC in a UMTS
  • the present invention relates to an improved AM RLC re- establishment method, whereby when the RLC entity is re-established, the AM RLC reduces the (number of amount of) data or control messages to be deleted, to thus minimize discontinuous communications and can increase data transmission and reception rates.
  • Figure 1 shows an exemplary network architecture for UMTS (Universal Mobile
  • the UMTS system is generally comprised of mobile terminals (user equipment: UE), a UTRAN (UMTS Terrestrial Radio Access Network), and a core network (CN).
  • the UTRAN has one or more radio network subsystems (RNS), with each RNS having a radio network controller (RNC) and one or more base stations (Node Bs). For each Node B, one or more cells exist.
  • RNS radio network subsystems
  • Node Bs base stations
  • FIG. 2 shows an exemplary radio protocol architecture used in UMTS. These radio protocol layers exist in the UE and UTRAN in pairs, and handles data transmissions over the radio interface. With respect to each radio protocol layer, the PHY layer (Layer 1) serves the purpose of transmitting data over the radio interface by using various radio transmission techniques. The PHY layer is connected with a MAC layer (a higher level layer) via transport channels in order to support reliable data transmissions, and the transport channel can be divided into dedicated transport channels and common transport channels according to whether or not the channels are shared.
  • MAC layer a higher level layer
  • the MAC layer performs mapping of various logical channels to various transport channels, and also performs logical channel multiplexing for mapping multiple logical channels to a single transport channel.
  • the MAC layer is connected with the RLC layer (a higher level layer) via logical channels, and the logical channels are divided into control channels for transmitting control plane information and traffic channels for transmitting user plane information, according to the type of data being transmitted.
  • the MAC layer can be further divided into a MAC-b sub-layer, a MAC-d sub-layer, a MACc/sh sub-layer, a MAC-hs sub-layer, and a MAC-e sub-layer according to the types of transport channels being managed.
  • the MAC-b sub-layer handles the management of a BCH (Broadcast Channel), which is a transport channel for handling the broadcast of system information.
  • the MAC-c/sh sub-layer manages common transport channels such as a FACH (Forward Access Channel), a DSCH (Downlink Shared Channel), and the like that are shared by various mobile terminals.
  • the MAC-d sub-layer handles the management of a DCH (Dedicated Channel) that is a dedicated transport channel for a particular mobile terminal.
  • the MAC-hs sub-layer manages a HS-DSCH (High Speed Downlink Shared Channel), which is a transport channel for high speed downlink data transmission.
  • the MAC-e sub-layer manages a E-DCH (Enhanced Dedicated Channel), which is a transport channel for high speed uplink data transmission.
  • the RLC layer guarantees the quality of service (QoS) of each radio bearer (RB) and handles the transmission of data thereof.
  • QoS quality of service
  • the RLC layer has one or two independent RLC entities for each RB, and provides three types of RLC modes, namely, TM (Transparent Mode), UM (Unacknowledged Mode), and AM (Acknowledged Mode) in order to support various QoS.
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the RLC layer performs the function of adjusting the size of data to be appropriate for a lower level layer to transmit data over the radio interface. To do so, a function of segmentation and concatenation of data received from a higher level layer is performed.
  • the PDCP layer is located at a higher level from the RLC layer, and employs IP
  • the PDCP layer performs the function of header compression, which allows transmission of only necessary information in the header portion of the data, to thus increase the transmission efficiency of the radio interface.
  • header compression is the basic function, the PDCP layer only exists in the PS domain, and in order to provide effective header compression with respect to each PS service, one PDCP entity exists for each RB.
  • a BMC Broadcast/Multicast Control
  • the RRC Radio Resource Control
  • the RRC Radio Resource Control
  • the RB refers to a logical path that is provided by Layer 1 and Layer 2 of the radio protocol for data transfer between the mobile terminal and the UTRAN.
  • the setup of an RB refers to the process of stipulating the characteristics of a protocol layer and a channel required for providing a specific service, and setting the respective detailed parameters and operation methods.
  • the RLC layer that is related to the present invention will be considered in more detail.
  • a basic function of the RLC layer is to guarantee the QoS of each RB and to transmit data thereof.
  • the RB service is a service that the Layer 2 of the radio protocol provides to a higher level, the entire Layer 2 effects the QoS, and in particular, the effect of the RLC layer is significant.
  • the RLC layer has independent RLC entities for each RB, and provides three types of RLC modes (TM, UM, AM) for supporting various QoS. These three modes of the RLC layer have differences in their operation methods because the QoS that they respectively support are different, and their detailed functions also have differences. As such, the RLC layer should be considered in more detail with respect to their operation modes.
  • the TM RLC is a mode in which no overhead is attached to the RLC SDU received from a higher level when forming (constituting) a RLC PDU.
  • the name TM RLC refers to the fact that the RLC passes the SDUs in a transparent manner, and the following functions are performed in the user plane and the control plane.
  • the user plane because the data processing time is short, transmission of real-time circuit data, such as voice or streaming of the circuit service (CS) domain, are handled.
  • CS circuit service
  • the control plane because there is no overhead within the RLC, in case of the uplink, transmission of RRC messages from unspecified mobile terminals are handled, while for the downlink, transmission of RRC messages that are broadcast to all mobile terminals within a cell are handled.
  • RLC is called a non-transparent mode, which comprises two types of modes; unacknowledged mode (UM) that provides no response that acknowledges receipt of transmitted data (UM), and acknowledged mode (AM) that provides a response.
  • UM unacknowledged mode
  • AM acknowledged mode
  • the UM RLC transmits each PDU upon adding thereto a PDU header that includes a sequence number (SN), to thus allow the receiving side to know which PDUs were lost (or missing) during transmission.
  • SN sequence number
  • the UM RLC handles the transmission of broadcast/multicast data in the user plane or the transmission of realtime packet data, such as voice (e.g., VoIP) or streaming of the packet service (PS) domain, and in the control plane, the transmission of RRC messages that do not need a reception acknowledgement response among the RRC messages transmitted to a particular terminal or particular terminal group.
  • voice e.g., VoIP
  • PS packet service
  • the AM RLC forms a PDU by adding a PDU header that includes a SN (as done in the UM RLC), but unlike the UM RLC and the significant difference therefrom is that the receiving side provides an acknowledgement for a PDU transmitted from the transmitting side.
  • the reason why the receiving side provides acknowledgement is to request the transmitting side to re-transmit those PDUs that could not be received.
  • Such re-transmission function is one of the most significant characteristics of the AM RLC.
  • the purpose of the AM RLC is to guarantee error-free data transmissions through the retransmitting function.
  • the AM RLC in the user plane, usually handles non-real-time packet data transmissions (such as TCP/IP of the PS domain), and in the control plane, handles the transmission of RRC messages that always requires reception acknowledgement response among the RRC messages transmitted to a particular terminal within a cell.
  • the TM RLC and UM RLC are used in uni-directional communications, while AM RLC is used in bi-directional communications because there is feedback from the receiving side.
  • the AM RLC uses only a dedicated logical channel.
  • TM RLC and UM RLC a single RLC entity has one type of structure for either a transmitter or receiver, but for AM RLC, a single RLC entity has both a transmitter and a receiver.
  • the AM RLC is complicated because of its re-transmission function.
  • the AM RLC has a re-transmission buffer in addition to a transmission/reception buffer, employs a transmission/reception window for flow control, performs a polling function whereby the transmitter requests status information from the peer RLC of the receiver, employs a status report sent by a receiver to report its buffer state to a peer RLC of the transmitter, employs a status PDU to carry the status information, performs a piggyback function that inserts a status PDU into a data PDU in order to increase data transmission efficiency, and also performs many other functions.
  • a Reset PDU is employed to request the peer AM RLC entity to re-set all operations and parameters, and a Reset Ack PDU is used for responding to such Reset PDU.
  • the AM RLC requires various protocol parameters, state variables, timer, and the like.
  • the PDUs used for data transmission control in the AM RLC, such as a status report or status PDU, Reset PDU, etc. are called Control PDUs, while the PDUs used for transferring user data are called Data PDUs.
  • the PDUs used in AM RLC are divided into two types; Data PDUs and Control PDUs.
  • a Reset Procedure is one situation where a Control PDU is employed.
  • the AM RLC of the receiver and of the transmitter initialize the state variables such that a state where communication can be performed again is achieved.
  • the Reset Procedure is as follows. First, the side that determined to start the Reset Procedure, namely the AM RLC of the transmitter includes the transmission direction HFN (Hyper Frame Number) that it currently uses into the Reset PDU and transmits such to the receiver.
  • HFN Hyper Frame Number
  • the AM RLC of the receiver resets its reception direction HFN value and also initializes the sequence numbers and other various state variables. Also, the receiver AM RLC transmits a Reset Ack PDU that includes its transmission direction HFN value to the transmitter AM RLC, and upon receiving this Reset Ack PDU, the transmitter AM RLC initializes various state variables after resetting its reception direction HFN value.
  • FIG. 17 shows an exemplary structure of an RLC PDU used in an AM RLC entity.
  • an AMD PDU which is a Data PDU used when transmitting data.
  • the AMD PDU is used when the AM RLC entity is to transmit user data or to transmit piggybacked status information and a polling bit.
  • the user data portion comprises 8 bit integer multiples
  • the AMD PDU header comprises a sequence number having a size of 2 octets.
  • the header portion of the AMD PDU includes a length indicator.
  • FIG. 4 shows an exemplary structure of a Status PDU.
  • the Status PDU is comprised of different types of super fields (SUFI).
  • the Status PDU may have a variable size, but is limited to the size of the largest RLC PDU of the logical channel on which the Status PDU is transmitted.
  • the SUFI serves the purpose of providing certain information, such as indicating which AMD PDUs arrived at the receiver or which AMD PDUs have not arrived.
  • the SUFI may be comprised of three parts; type, length and value.
  • FIG. 5 shows an exemplary structure of a Piggybacked Status PDU.
  • the structure of the Piggybacked Status PDU is similar to that of the AMD PDU, but the D/C field of the AMD PDU is replaced with a reserved but (R2).
  • the Piggybacked Status PDU is inserted if there is sufficient space remaining in the AMD PDU.
  • the PDU type value is always fixed to be 000 .
  • a Control PDU includes both a Status PDU and a Piggybacked Status PDU.
  • FIG. 6 shows an exemplary structure of a Reset/Reset Ack PDU.
  • the Reset PDU includes a 1 bit sequence number called an RSN.
  • the Reset Ack PDU is transmitted in response to the received Reset PDU, and the RSN of the received Reset PDU is included when transmitting.
  • the following parameters are used in the Reset/ Reset Ack PDU format.
  • D/C field indicates whether the PDU is a Control PDU or Data PDU
  • PDU Type indicates the type of Control PDU, namely, whether the PDU is a
  • Sequence Number refers to sequence number information of the AMD PDU.
  • Header extension indicates whether the next octet is a length indicator or data.
  • Length indicator indicates the location of a boundary, if such boundary exists between respectively different SDUs within the data portion of a PDU.
  • PAD indicates a padding region, but not used in the AMD PDU.
  • the receiver when a situation where a Reset procedure needs to be performed occurs, the receiver must send a Reset PDU to the transmitter.
  • the Reset procedures is performed if a Status PDU containing an erroneous sequence number is received or if a particular PDU transmission has failed a certain number of times.
  • the transmitter performs the following operations.
  • the VR(RST) is initialized by using internal parameters of the receiver each time the reset procedure is performed. This value is the maximum value of transmitting the Reset PDU for each reset procedure. Namely, if the Reset PDU transmission exceeds the MaxRST value, the reset procedure is immediately terminated and the higher level is informed that an unsolvable error has occurred.
  • the transmitter transmits the Reset PDU, a HFNI value and a RSN value are included in the transmission.
  • the transmitter sets the HFNI as the maximum HFN value that it uses.
  • the HFN is a values used in encoding (encryption) and the transmitter uses the HFN value to encode the portions of the AMD PDU excluding the SN value of thereof.
  • the receiver uses the same HFN value to decode the received AMD PDU. If the receiver and the transmitter do not have the same HFN value, communication therebetween cannot be maintained. Accordingly, in the reset procedure, the transmitter and receiver exchange their HFN values such that both the transmitter and receiver are set to have the same HFN value.
  • the transmitter and the receiver include their HFN value in the Reset PDU or the Reset Ack PDU when transmitting.
  • the RSN value is used for matching each of the Reset PDUs and the Reset Ack
  • Reset Ack PDU If a Reset Ack PDU with a RSN value set to a value other than 1 is received, such Reset Ack PDU is deems as erroneous and is thus discarded. Also, for each reset procedure that begins, the RSN value is increased by one. [41] When the Reset Ack PDU is transmitted in response to the Reset PDU, the receiver sends the largest value HFN that is used in its transmission direction by filling it into the HFNI, and also, the same RSN value as that included in the corresponding Reset
  • the receiver Upon receiving the Reset PDU, the receiver performs the following operations.
  • step 3 is performed. [45] 3. If the currently received Reset PDU is the first Reset PDU received after the
  • a Reset Ack PDU is newly formed and transmitted.
  • the HFN value of the receiver direction is set according to the value instructed from a higher level.
  • the Control PDU(s) of both transmitter and receiver are all deleted, and among the SDUs in the transmitter, those SDUs that have been completely transmitted are deleted.
  • the SDU(s) not deleted in step 4 are re-segmented again according to the set
  • step 7 is performed. [71] 6.
  • the Control PDU(s) of both the receiver and transmitter are deleted, and the
  • Control PDU(s) are deleted even if the re-establishment is for a single direction (i.e. either the transmitting direction or the receiving direction). However, this may not be desirable in certain situations.
  • the present invention has been developed in order to solve at least the above described problems of the related art that deletes all control PDUs for both directions of re-establishment.
  • the present invention provides an efficient AM RLC re-establishment mechanism (scheme) that deletes only those control PDUs related to a particular re-establishment direction.
  • Figure 1 shows an exemplary UMTS network architecture applicable to the related art and the present invention.
  • Figure 2 shows an exemplary radio protocol architecture used in UMTS.
  • FIG. 7 shows an exemplary structure of an AM RLC PDU that is a data PDU used when data is transmitted.
  • Figure 4 shows an exemplary structure of a Status PDU.
  • Figure 5 shows an exemplary structure of a Piggyback Status PDU.
  • Figure 6 shows an exemplary structure of a Reset / Reset Ack PDU.
  • Figure 7 shows an inefficient a single-sided (one direction) re-establishment procedure that occurs during a RLC Reset process.
  • Figure 8 shows an exemplary flow chart of a RLC re-establishment method in a radio communication system according to the present invention.
  • RLC re-establishment for an RLC of the UE, an RLC of the network, or both
  • a cell or coverage area
  • the UE may be able to perform high speed access (such as HSDPA and/or HSUPA) with the network, but at locations near the boundary (or edge) of the cell, such high speed access may not be available.
  • high speed access such as HSDPA and/or HSUPA
  • RLC re-establishment should be performed in order to support seamless communications.
  • control information is managed depending upon the direction in which re-establishment is performed. Namely, when a single-sided re-establishment is performed, the control information (e.g., control PDUs) related to that direction is not deleted, which is different than the related art wherein all control information is deleted regardless of the re-establishment direction.
  • control information e.g., control PDUs
  • PDU(s) are deleted even if the re-establishment is for a single direction (i.e. either the transmitting direction or the receiving direction). In most cases, such does not significantly affect the data transmission capabilities of the mobile terminal or of the network. This is because, in most instances, when re-establishment is performed for both the receiving direction and the transmitting direction, the context of the RLC can only change because the Node B has changed or because the RNC has changed, and thus it is faster to newly start processing by disregarding all control message information. Also, doing so removes the possibility of inconsistencies (i.e., non- correspondence) in the context of the transmitter and of the receiver.
  • HSDPA High Speed Downlink Packet Access
  • HSUPA High Speed Uplink Packet Access
  • AM RLC PDU(s) having a relatively large size may be used, but when located at a cell boundary, the quality of the radio environment is degraded, and thus, relatively large sized AM RLC PDU(s) cannot be used. Accordingly, when the mobile terminal moves from a center of the cell to a cell boundary, or vice versa, despite the fact that the mobile terminal remains within the same cell, there is a need to change the size of the AM RLC PDU(s) used by the mobile terminal.
  • the introduction of HSDPA and HSUPA has allowed various types of physical channels and transport channels to be used, and AM RLC PDU(s) having an optimal size for each physical channel or each transport channel can be used. As the size of the AM RLC PDU(s) changes, the RLC entity must be re-established.
  • the downlink quality and the uplink quality may be different (i.e., distinct). Namely, the degree of degradation on the downlink does not result in the same degree of degradation on the uplink.
  • the downlink quality is degraded to a level where HSDPA cannot be used, but where HSUPA may still be used occur quite frequently.
  • situations where the HSUPA quality is degraded yet the HSDPA quality remains satisfactory, or when the mobile terminal moves from a cell boundary to the cell center, as well as many other situations may occur. In such cases, re-establishment for both the transmitter direction and the receiver direction are not necessary, and only re- establishment for the corresponding direction (e.g., only for the uplink or only for the downlink) would be needed.
  • Figure 7 shows a re-establishment method while the Reset procedure is in progress.
  • step 3 Simultaneously with the procedure of step 2, the re-establishment procedure with respect to one direction is performed. At side B, the re-establishment procedure for the transmitter direction occurs, and accordingly, at side A, the re-establishment procedure for the receiver direction occurs.
  • each side exchanges HFNI values and the like and works towards normalizing communications. For example, if the HFN values used respectively for the directions of the receiver of side B and the transmitter of side A are different, data cannot be properly decoded at the receiver. Thus, the Reset procedure should be terminated as quickly as possible. However, the Reset procedure can be terminated only if a Reset Ack PDU is properly received by the transmitter. In the above process, even though re-establishment occurred in the direction that is unrelated to the Reset, because both the transmitter and the receiver deleted all Control PDUs, the procedure for normally exchanging Control PDUs is delayed.
  • the present invention provides an improved operation of an AM RLC entity for a single-sided RLC re-establishment, which increases data transmission rate and minimizes communication disruptions.
  • the transmitting side and the receiving side only deletes the Control PDU(s) related to its respective direction.
  • RLC entity only deletes those Control PDU(s) related to the transmitting direction, while the Control PDU(s) related to the receiving direction are not deleted.
  • Control PDU(s) related to the transmitting side direction refers to Control
  • the Control PDU(s) formed by the transmitting side include Control PDU(s), such as a Reset PDU or a MRW SUFl, that are to be actively sent by the transmitting side.
  • the Control PDU(s) formed by the receiving side include Control PDU(s), such as a Reset Ack PDU or a MRW Ack SUFl, that are to be actively sent by the receiving side.
  • Control PDU(s) such as a Reset Ack PDU or a MRW Ack SUFl, that are to be actively sent by the receiving side.
  • Control PDU that is waiting to be transmitted
  • the Control PDU(s) that have not been transmitted, and not deleted by the re-establishment procedure should be immediately transmitted to the peer RLC entity. Accordingly, such Control PDU(s) that remain without being deleted should be reserved for transmission.
  • the present invention proposes that with respect to Control PDUs formed before a re-establishment procedure and reserved for transmission, or Control PDUs not transmitted before the re-establishment procedure and not deleted through the re- establishment procedure, new Control PDU(s) should be formed and its transmission should be scheduled again.
  • the present invention proposes that when re-establishment occurs, the receiving side of the RLC entity does not delete all existing Control PDUs, but Control PDUs unrelated to the receiving side (direction) are not deleted. Also, other Control PDUs are all deleted.
  • the present invention proposes that when re-establishment occurs, the receiving side of the RLC entity does not delete all existing Control PDUs, but Control PDUs related to the transmitting side (direction) are not deleted. Also, the Control PDUs unrelated to the transmitting side (direction) are all deleted.
  • Control PDUs related to the receiving side may include Acknowledgement Status Report, Window SUFl, MRW Ack SUFl, and the like.
  • Control PDUs unrelated to the receiving side may include MRW SUFI, Reset PDU, Reset Ack PDU, and the like.
  • Control PDUs related to the transmitting side may include MRW SUFl and the like.
  • Control PDUs unrelated to the transmitting side may include Acknowledgement Status Report, Window SUFI, MRW Ack StTl, Reset PDU, Reset
  • FIG. 8 shows an exemplary flow chart of a RLC re-establishment method in a radio communication system according to the present invention.
  • the HFN value of the receiving direction is set according to the value instructed from a higher level.
  • Control PDUs the Control PDUs excluding the transmitting direction Control PDUs are deleted.
  • the HFN value of the receiving direction is set according to the value instructed from a higher level.
  • the HFN value of the receiving direction is set according to the value instructed from a higher level.
  • the receiving direction AMD PDUs are deleted.
  • the Acknowledgement is only in the receiving direction, the Acknowledgement
  • the MRW SUFl is merely one example, and regardless of the receiving direction, namely, Control PDUs or SUFl that were formed before re- establishment, not transmitted before re-establishment, and not deleted during re- establishment are all formed as new PDUs in step 5 and transmitted in step 6.
  • the existence of a Reset PDU means that a Reset procedure is in progress.
  • reserving transmission of a Reset PDU means that a new reset procedure is started after the re-establishment procedure.
  • the present invention proposes that for a re-establishment procedure only in the receiving direction, all Control PDUs excluding the MRW SUFl are deleted, and if there was a Reset PDU (i.e., when a Reset procedure was in progress), the Reset procedure is newly started.
  • Control PDUs excluding the MRW SUFI refers to an Acknowledgement Status Report, Window SUFl, MRW Ack SUFl, and Reset PDU, Reset Ack PDU.
  • the receiving direction operation according to the present invention is as follows:
  • the HFN value of the receiving direction is set according to the value instructed from a higher level.
  • step 4 if there was a Control PDU that was deleted, namely, if there was a Reset procedure in progress before the re-establishment procedure, a Reset PDU is formed and transmitted. Namely, a new Reset procedure is started.
  • the present invention proposes that when re-establishment occurs
  • the transmitting side of the RLC entity does not delete all existing Control PDUs, but Control PDUs unrelated to the transmitting side (direction) are not deleted. Also, other Control PDUs are all deleted.
  • the present invention proposes that when re-establishment occurs
  • the transmitting side of the RLC entity does not delete all existing Control PDUs, but Control PDUs related to the receiving side (direction) are not deleted. Also, the Control PDUs unrelated to the receiving side (direction) are all deleted.
  • Control PDUs related to the transmitting side may include MRW
  • Control PDUs unrelated to the transmitting side may include Acknowledgement Status Report, Window SUFI, MRW Ack SUFl, Reset PDU, Reset Ack PDU, and the like.
  • Control PDUs related to the receiving side may include Acknowledgement Status Report, Window SUFl, MRW Ack SUFl, and the like.
  • Control PDUs unrelated to the receiving side may include MRW SUFI,
  • Reset PDU Reset Ack PDU, and the like.
  • the present invention proposes the following operations when the transmitting side (direction) of the RLC is re-established:
  • the HFN value of the transmitting direction is set according to the value instructed from a higher level.
  • step 5 except for the Reset Ack PDU among the remaining Control PDUs, all Control PDUs are deleted. Namely, among the Control PDUs formed before the re- establishment procedure, all Control PDUs (except the Reset Ack PDU) are deleted.
  • step 4 The SDUs not deleted as a result of step 4 are re-segmented again according to the set RLC size.
  • step 5 (excluding the Control PDUs related to the receiving direction) are deleted. [175] 6. After step 5, the remaining other Control PDUs are formed as new Control PDUs and transmission is reserved. [176] 7. The SDUs not deleted as a result of step 4 are re-segmented again according to the set RLC size.
  • PDU means that a reset procedure is started after the re-establishment procedure.
  • the present invention proposes that for a re-establishment procedure only in the transmitting direction, all Control PDUs (excluding Control PDUs related to the receiving direction) are deleted, and if there was a Reset Ack PDU (i.e., when a Reset procedure was in progress), the Reset procedure is newly started.
  • Control PDUs excluding those related to the receiving direction refers to MRW SUFI, and Reset
  • the transmitting direction operation according to another embodiment of the present invention is as follows:
  • the HFN value of the receiving direction is set according to the value instructed from a higher level.
  • step 4 For re-establishment only in the transmitting direction, perform procedure from step 4.
  • step 10 For re-establishment of both the transmitter and the receiver, perform procedure from step 10.
  • Control PDUs related to the receiving direction are Control PDUs that inform about the receiving side circumstances. For example, an Acknowledgement Status Report that indicates which PDUs were properly received or not received, a Window SUFI that adjusts the window size that can be received, a MRW Ack SUFI that is a response message of the receiving side that is sent for a MRW SUFI that informs about the SDU information discarded at the transmitting side, and the like.
  • step 4 The SDUs not deleted as a result of step 4 are re-segmented again according to the set RLC size.
  • step 8 the re-segmentation of data PDUs is unrelated to the Control PDUs, thus is not affected by sequential order.
  • step 8 can be performed right after step 4.
  • the present invention provides a method wherein, if the RLC entity is re-established, all Control PDUs are not deleted regardless of whether re- establishment is only for one direction, but only those Control PDUs related to a particular direction are selectively deleted, and the Control PDUs newly formed after re-establishment are immediately transmitted. As a result, the communication disconnection time is reduced, the RLC data transmission rate is improved, etc. to thus improve user satisfaction.
  • the present disclosure provides a re-establishment method for an Acknowledged
  • Mode Radio Link Control entity the method comprising: receiving, from an upper entity, a command to perform Acknowledged Mode Radio Link Control re- establishment; and managing control protocol data units by considering a direction of the Acknowledged Mode Radio Link Control re-establishment.
  • the control protocol data units related to the direction are deleted.
  • the control protocol data units not related to the direction are not deleted.
  • the method may further comprise: scheduling the control PDUs for transmission after acknowledged mode radio link control re- establishment.
  • the upper entity is a Radio Resource Control layer.
  • the Acknowledged Mode Radio Link Control re-establishment is performed in a transmitting direction.
  • the Acknowledged Mode Radio Link Control re-establishment is performed in a receiving direction.
  • the present disclosure provides a scheme for re-establishment of a radio link control entity, the scheme comprising: deciding to perform re-establishment of a protocol entity; and processing control information by considering the direction of the re-establishment of the protocol entity.
  • the protocol entity is an Acknowledged Mode Radio Link Control entity.
  • the deciding is based upon a command received from an upper layer entity.
  • the control information is in the form of control protocol data units.
  • the Acknowledged Mode Radio Link Control re-establishment is performed in a transmitting direction.
  • the Acknowledged Mode Radio Link Control re-establishment is performed in a receiving direction.
  • the present disclosure provides a protocol stack to support re- establishment of a radio link control entity, the protocol stack comprising: a Radio Resource Control layer adapted to provide instructions to perform re-establishment of a lower layer; and a Radio Link Control layer cooperating with the Radio Resource Control layer and adapted to perform re-establishment based upon the instructions from the Radio Resource Control layer by considering a direction of the re- establishment.

Landscapes

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

Abstract

L'invention concerne un procédé de réinitilisation d'une entité de contrôle de liaison radio en mode accusé de réception, ce procédé consistant à recevoir d'une entité supérieure un ordre pour effectuer une réinitilisation de contrôle de liaison radio en mode accusé de réception, et à gérer des unités données de protocole de contrôle en tenant compte de la direction de la réinitilisation de contrôle de liaison radio en mode accusé de réception, les unités données de protocole de contrôle associées à la direction étant supprimées et les unités données de protocole de contrôle non associées à la direction n'étant pas supprimées.
PCT/KR2006/004378 2005-10-04 2006-10-25 Procédé efficace de réinitialisation am rlc WO2008004724A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2006800552354A CN101479965B (zh) 2006-07-05 2006-10-25 一种用于确认模式无线链路控制实体的重建方法及设备
US12/307,239 US8681712B2 (en) 2005-10-04 2006-10-25 Efficient AM RLC re-establishment mechanism

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020060063133A KR100905965B1 (ko) 2005-10-04 2006-07-05 무선통신 시스템에서의 ｒｌｃ 재연결 방법
KR10-2006-0063133 2006-07-05

Publications (1)

Publication Number Publication Date
WO2008004724A1 true WO2008004724A1 (fr) 2008-01-10

Family

ID=38894675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2006/004378 WO2008004724A1 (fr) 2005-10-04 2006-10-25 Procédé efficace de réinitialisation am rlc

Country Status (2)

Country Link
CN (1) CN101479965B (fr)
WO (1) WO2008004724A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010016150A1 (fr) * 2008-08-08 2010-02-11 富士通株式会社 Dispositif sans fil, procédé de communication et programme de communication
KR101518269B1 (ko) 2008-02-01 2015-05-08 삼성전자주식회사 상태보고를 전송하는 방법 및 시스템

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030147370A1 (en) * 2002-02-05 2003-08-07 Chih-Hsiang Wu Inter Node B serving HS-DSCH cell change mechanism in a high speed wireless communication system
US20030206534A1 (en) * 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20040032851A1 (en) * 2002-08-13 2004-02-19 Chih-Hsiang Wu Method for handling timers after an RLC reset or re-establishment in a wireless communications system
US20040203971A1 (en) * 2002-06-21 2004-10-14 Kuo Richard Lee-Chee Method for determining RLC entity re-establishment during SRNS relocation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030147370A1 (en) * 2002-02-05 2003-08-07 Chih-Hsiang Wu Inter Node B serving HS-DSCH cell change mechanism in a high speed wireless communication system
US20030206534A1 (en) * 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20040203971A1 (en) * 2002-06-21 2004-10-14 Kuo Richard Lee-Chee Method for determining RLC entity re-establishment during SRNS relocation
US20040032851A1 (en) * 2002-08-13 2004-02-19 Chih-Hsiang Wu Method for handling timers after an RLC reset or re-establishment in a wireless communications system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101518269B1 (ko) 2008-02-01 2015-05-08 삼성전자주식회사 상태보고를 전송하는 방법 및 시스템
WO2010016150A1 (fr) * 2008-08-08 2010-02-11 富士通株式会社 Dispositif sans fil, procédé de communication et programme de communication

Also Published As

Publication number Publication date
CN101479965A (zh) 2009-07-08
CN101479965B (zh) 2013-07-10

Similar Documents

Publication Publication Date Title
US8681712B2 (en) Efficient AM RLC re-establishment mechanism
RU2419218C2 (ru) Способ передачи управляющей информации в системе беспроводной связи и использующий его способ обновления окна передачи
WO2008004725A1 (fr) Procédé optimisé de réinitialisation de am rlc
US9532378B2 (en) Apparatus and method for moving a receive window in a radio access network
JP4906844B2 (ja) 無線移動通信システムで下位階層データブロックを生成する方法
KR101084135B1 (ko) 무선 통신 시스템의 송수신 단에서의 상태 ｐｄｕ송수신방법
US10230496B2 (en) Method and apparatus for processing control message which requests retransmitting data
KR20050118591A (ko) 무선통신 시스템에서의 무선링크제어(ｒｌｃ) 데이터처리방법
KR101084136B1 (ko) 무선 통신 시스템의 송수신 단에서 상태정보를 포함하는ｐｄｕ를 송수신하는 방법
WO2008004724A1 (fr) Procédé efficace de réinitialisation am rlc
KR20020088316A (ko) 무선통신시스템에서 서비스 데이터 단위 폐기정보 전송방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680055235.4

Country of ref document: CN

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

Ref document number: 06812220

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12307239

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06812220

Country of ref document: EP

Kind code of ref document: A1