WO2001005121A1 - Technique for providing a secure link in a mobile communication system - Google Patents
Technique for providing a secure link in a mobile communication system Download PDFInfo
- Publication number
- WO2001005121A1 WO2001005121A1 PCT/SE2000/001461 SE0001461W WO0105121A1 WO 2001005121 A1 WO2001005121 A1 WO 2001005121A1 SE 0001461 W SE0001461 W SE 0001461W WO 0105121 A1 WO0105121 A1 WO 0105121A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- link layer
- layer protocol
- protocol entity
- transmitting
- entity
- Prior art date
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/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
-
- 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/1874—Buffer management
-
- 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
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
-
- 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
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
Definitions
- the present invention relates generally to mobile communication systems and, more particularly, to a technique for providing a secure link when transitioning from a first pair of link layer protocol entities to a second pair of link layer protocol entities in a mobile communication system.
- the system 10 includes a Core Network (CN) 12, a Radio Access Network (RAN) 14, and a plurality of Mobile Stations (MS) 16.
- the RAN 14 is divided into controller nodes 18 and Base Transceiver Station (BTS) nodes 20.
- BTS Base Transceiver Station
- the RAN 14 may be made up of several RANs, each having one or more controller nodes 18 and BTS nodes 20.
- the hierarchy of the system is such that the CN 12 is connected to several controller nodes 18, each controller node 18 is connected to several BTS nodes 20, and each BTS node 20 services one or more MS 16.
- an Automatic Repeat Request (ARQ) protocol can optionally be executed between the MS 16 and the RAN 14 to reduce the residual error rate.
- the function of the ARQ protocol is to take care of errors that are introduced as a result of the radio interface (e.g., due to interference).
- a handover may occur that results in moving the execution of the ARQ protocol between different controller nodes 18. To insure that no user data is lost during a handover, certain mechanisms must be implemented.
- GPRS General Packet Radio Service
- SGSN's Serving GPRS Support Nodes
- the protocol states of the buffers are synchronized between the MS 16 and the destination SGSN by means of handover signaling (see GSM 03.60 -
- this first mechanism is that no unnecessary retransmission of the user data is required over the radio interface, and that the ARQ protocol in the MS 16 can be unaware of the handover, which also makes the implementation less expensive.
- this first mechanism is limited to intra- system handovers, where the same ARQ protocol with the same configuration is used throughout the system. Thus, it will no longer be useful in future systems where it will be possible to use different ARQ protocol configurations within the same RAN, and where there can be different sizes of protocol data units (PDU's) associated with the different ARQ protocol configurations. In addition, it can be very complex to move an entire protocol state.
- PDU's protocol data units
- the user data is secured by having 2 levels of ARQ protocols in the system 10.
- the first ARQ protocol called a Radio Link Control (RLC) protocol
- RLC Radio Link Control
- BSC Base Station Controller
- the second ARQ protocol called a Logical Link Control (LLC) protocol, is executed between an MS 16 and the CN 12 (e.g., at an SGSN node)(see
- LLC Logical Link Control
- the RLC protocol is re-started in both the MS 16 and the BSC when a handover is performed.
- the main benefit of this second mechanism is that it can handle inter-system handovers.
- this second mechanism has major disadvantages. For instance, unnecessary radio resources are wasted due to the overhead associated with the second ARQ protocol.
- L3 PDU is on the order of 7 bytes. This can be compared to the size of a Van Jacobsen compressed Transmission Control Protocol (TCP) acknowledgment, which is under
- this third mechanism Similar to the second mechanism, the main benefit of this third mechanism is that it can handle inter-system handovers.
- this third mechanism also has major disadvantages. For instance, extra buffer space is required because the sender of the L2_ARQ protocol PDUs is required to keep all the L2 PDUs, carrying a L3 PDU, in a buffer until the whole L3 PDU has been acknowledged. Also, when a handover takes place, all L2 PDUs of an L3 PDU are retransmitted by the new L2 ARQ protocol. That is, even the L2 PDUs which were previously acknowledged are retransmitted. This is of course not optimal and a major disadvantage of this third mechanism.
- the first pair of link layer protocol entities includes a first transmitting link layer protocol entity for segmenting data and transmitting segmented data, and a first receiving link layer protocol entity for receiving segmented data from the first transmitting link layer protocol entity and acknowledging the received segmented data.
- the second pair of link layer protocol entities includes a second transmitting link layer protocol entity for segmenting data and transmitting segmented data, and a second receiving link layer protocol entity for receiving segmented data from the second transmitting link layer protocol entity and acknowledging the received segmented data.
- Both the first pair of link layer protocol entities and the second pair of link layer protocol entities are preferably automatic repeat request protocol entities.
- the transition from the first pair of link layer protocol entities to the second pair of link layer protocol entities can be due to a variety of reasons such as, for example, a handover in the mobile communication system or a protocol reconfiguration in the mobile communication system.
- the first pair of link layer protocol entities can utilize the same protocol as the second pair of link layer protocol entities, or the first pair of link layer protocol entities can utilize a different protocol than the second pair of link layer protocol entities. If the first pair of link layer protocol entities utilizes the same protocol as the second pair of link layer protocol entities, the first pair of link layer protocol entities can still be configured differently than the second pair of link layer protocol entities.
- the technique is realized by first suspending data transmissions from the first transmitting link layer protocol entity to the first receiving link layer protocol entity, and then initiating data transmissions from the second transmitting link layer protocol entity to the second receiving link layer protocol entity.
- the unacknowledged segmented data in the first transmitting link layer protocol entity is then tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- the first pair of link layer protocol entities can be controlled by at least one first control protocol entity
- the second pair of link layer protocol entities can be controlled by at least one second control protocol entity.
- the data transmissions from the first transmitting link layer protocol entity to the first receiving link layer protocol entity can then be suspended by the at least one first control protocol entity, and the data transmissions from the second transmitting link layer protocol entity to the second receiving link layer protocol entity can then be initiated by the at least one second control protocol entity.
- the at least one first control protocol entity and the at least one second control protocol entity can be the same control protocol entity.
- untransmitted unsegmented data in the first transmitting link layer protocol entity is preferably transferred from the first transmitting link layer protocol entity to the second transmitting link layer protocol entity.
- untransmitted unsegmented data in the first transmitting link layer protocol entity can be segmented and then transferred from the first transmitting link layer protocol entity to the second transmitting link layer protocol entity for tunneling.
- segmented data in the first transmitting link layer protocol entity can be assembled and transferred from the first transmitting link layer protocol entity to the second transmitting link layer protocol entity.
- a status message can be sent from the first receiving link layer protocol entity to the first transmitting link layer protocol entity prior to tunneling the unacknowledged segmented data from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- the first receiving link layer protocol entity can be notified of the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- first pair of link layer protocol entities are controlled by at least one first control protocol entity
- second pair of link layer protocol entities are controlled by at least one second control protocol entity
- a sequence number of a last unacknowledged data segment in the first transmitting link layer protocol entity can be sent from the at least one first control protocol entity to the at least one second control protocol entity to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- an indication of the number of tunneled unacknowledged segmented data can be sent from the at least one first control protocol entity to the at least one second control protocol entity to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- an indication of the amount of tunneled unacknowledged segmented data can be sent from the at least one first control protocol entity to the at least one second control protocol entity to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- a sequence number of a last unacknowledged data segment in the first transmitting link layer protocol entity can be sent from the first transmitting link layer protocol entity to the first receiving link layer protocol entity prior to tunneling the unacknowledged segmented data to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- a message indicating that the previous tunneled unacknowledged segmented data was the last tunneled unacknowledged segmented data can be sent from the first transmitting link layer protocol entity to the first receiving link layer protocol entity after the last tunneled unacknowledged segmented data to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- a message containing an indication of the amount of tunneled unacknowledged segmented data can be sent from the second transmitting link layer protocol entity to the second receiving link layer protocol entity to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- a message containing a sequence number of a last unacknowledged data segment in the first transmitting link layer protocol entity can be sent from the second transmitting link layer protocol entity to the second receiving link layer protocol entity prior to tunneling the unacknowledged segmented data to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- the sequence number is signaled to the second transmitting link layer protocol entity from the first transmitting link layer protocol entity prior to sending the message, and then signaled to the first receiving link layer protocol entity from the second receiving link layer protocol entity after sending the message.
- an indication of the number of tunneled unacknowledged segmented data can be sent from the second transmitting link layer protocol entity to the second receiving link layer protocol entity to notify the first receiving link layer protocol entity of the end of the unacknowledged segmented data tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity.
- the number of tunneled unacknowledged segmented data is signaled to the second transmitting link layer protocol entity from the first transmitting link layer protocol entity prior to sending the indication, and then signaled to the first receiving link layer protocol entity from the second receiving link layer protocol entity after sending the indication.
- the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity can be signaled to the second transmitting link layer protocol entity from the first transmitting link layer protocol entity.
- a message indicating the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity can then be sent from the second transmitting link layer protocol entity to the second receiving link layer protocol entity.
- the end of the unacknowledged segmented data to be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity can then be signaled to the first receiving link layer protocol entity from the second receiving link layer protocol entity.
- the first pair of link layer protocol entities can be terminated after all of the unacknowledged segmented data has been tunneled.
- the first pair of link layer protocol entities can be terminated after a predetermined period of time.
- unacknowledged segmented data in the first transmitting link layer protocol entity can be tunneled from the first transmitting link layer protocol entity to the first receiving link layer protocol entity through the second transmitting link layer protocol entity and the second receiving link layer protocol entity by first sending the unacknowledged segmented data from the first transmitting link layer protocol entity to the second transmitting link layer protocol entity.
- the unacknowledged segmented data is then transmitted from the second transmitting link layer protocol entity to the second receiving link layer protocol entity.
- the unacknowledged segmented data is then sent from the second receiving link layer protocol entity to the first receiving link layer protocol entity.
- the unacknowledged segmented data can be marked before it is transmitted from the second transmitting link layer protocol entity to the second receiving link layer protocol entity.
- the unacknowledged segmented data can be marked utilizing, for example, a length indicator field in an acknowledged mode data protocol data unit, or a special field in a control protocol data unit.
- the unacknowledged segmented data can be transmitted from the second transmitting link layer protocol entity to the second receiving link layer protocol entity over a dedicated communication link.
- the unacknowledged segmented data is preferably transmitted from the second transmitting link layer protocol entity to the second receiving link layer protocol entity before any higher layer data so as to insure sequence order integrity.
- tunneled unacknowledged segmented data is typically combined with acknowledged segmented data in the first receiving link layer protocol entity, and the combined segmented data is then assembled.
- the assembled combined data can then be sent directly to a higher layer protocol entity.
- the assembled combined data can be sent to a higher layer protocol entity through the second receiving link layer protocol entity.
- the assembled combined data is preferably sent to a higher layer protocol entity before the second receiving link layer protocol entity sends any data to the higher layer protocol entity so as to insure sequence order integrity.
- the second receiving link layer protocol entity can be notified that all the assembled combined data has been sent to the higher layer protocol entity so as to insure sequence order integrity.
- FIG. 1 is a schematic diagram of a typical mobile cellular system including a Core Network (CN), a Radio Access Network (RAN), and a plurality of Mobile Stations (MS).
- CN Core Network
- RAN Radio Access Network
- MS Mobile Stations
- Figure 2 is an illustration of a generic protocol stack for showing specific protocols on different hierarchical layers that are used within a cellular mobile communication system in accordance with the present invention.
- Figure 3 is a schematic diagram of a cellular mobile communication system including a CN, two different RANs, and an MS which are involved in a technique for providing a secure link between an MS and a CN during handover scenarios or L2_ARQ protocol reconfigurations in accordance with the present invention.
- Figure 4 is a flowchart showing data being transferred between two L2_ARQ protocol entities over an air interface.
- Figure 5 is a flowchart showing data being transferred between two new L2_ARQ protocol entities over an air interface just after a handover or an L2_ARQ protocol reconfiguration has taken place in accordance with the present invention.
- Figure 6 is a signaling chart for a handover scenario in accordance with the present invention.
- FIG. 7 shows the format of an L2 ARQ Acknowledged Mode Data (AMD) PDU in accordance with the present invention.
- Figure 8 shows the format of an L2 ARQ Acknowledged Mode Data (AMD) PDU in accordance with the present invention.
- FIG. 9 is a schematic diagram of an exemplary protocol entity processing device for implementing the signaling involved in a handover or a protocol reconfiguration in a mobile communication system in accordance with the present invention.
- the L3 layer is used to refer to any network protocol such as, for example, Internet Protocol (IP).
- IP Internet Protocol
- the L3 layer may also include a framing protocol such as, for example, Point-to-Point Protocol (PPP).
- PPP Point-to-Point Protocol
- the L3 layer may further include a control plane protocol such as, for example, Radio Resource
- RRC Universal Mobile Telecommunication System
- the L3 layer refers to any protocol that produces a protocol data unit
- PDU that is transferred to the layer below, which in this case is the L2_ARQ layer.
- the L2 ARQ layer is used to refer to a link layer protocol such as, for example, Radio Link Control (RLC), that potentially segments L3 PDUs into smaller
- RLC Radio Link Control
- L2_ARQ PDUs and/or concatenates several L3 PDUs into L2_ARQ PDUs and implements ARQ functionality on the basis of these L2_ARQ PDUs.
- the L2_ARQ protocol follows rules regarding the retransmission of L2 ARQ PDUs. For example, for any form of ARQ, the sending L2_ARQ has to buffer each L2_ARQ PDU until the receiving L2_ARQ positively acknowledges the receipt of same. Upon receiving the acknowledgment, the sending
- L2_ARQ is allowed to delete the acknowledged L2_ARQ PDU from its send buffer.
- the L2_ARQ protocol may have several different operational modes such as, for example, unreliable, semi-reliable, and fully reliable, for the transmission of higher layer data (i.e., L3 PDUs).
- L3 PDUs higher layer data
- the latter two modes can either be combined with in- sequence or out-of-sequence delivery operation.
- the LI layer is used to refer to the physical layer of a radio link. It can be any radio transmission technology used in today's or future mobile communication networks (e.g., GSM, UMTS, or wireless LANs).
- GSM Global System for Mobile Communications
- UMTS Universal Mobile Subscriber Identity
- wireless LANs wireless local area network
- Radio Access Network examples of such systems are the Global System for Mobile Communications (RAN). Examples of such systems are the Global System for Mobile Communications (RAN).
- GSM Global System for Mobile Communications
- GPRS General Packet Radio Service
- UMTS Universal Mobile Communications
- L2_ARQ protocol in both is the RLC protocol.
- FIG. 3 there is shown a cellular mobile communication system 100 which will be used in this detailed description to describe a technique for providing a secure link between an MS and a Core Network (CN) during handover scenarios or L2 ARQ protocol reconfigurations in accordance with the present invention.
- the system 100 comprises a CN 102, which is connected to two different
- L3 PDUs are transmitted between the MS 106 and the CN 102 through different L2 ARQ protocols depending on the currently used RAN 104.
- the technique described in this detailed description is not limited to the number of RANs 104 that are connected to the CN 102. That is, any number of RANs 104 are allowed by the technique described herein.
- RAB Bearer
- unacknowledged L2_ARQ PDUs in the old sending L2_ARQ protocol entity are tunneled through the new L2 ARQ protocol entities to the old receiving L2_ARQ protocol entity. That is, after a handover or an L2_ARQ protocol reconfiguration has occurred, the old L2 ARQ protocol entities enter into a tunneling state wherein they do not perform any ARQ functions but still communicate data via the new L2 ARQ protocol entities.
- the old L2_ARQ PDUs are tunneled via the new L2 ARQ protocol entities to the old receiving L2_ARQ protocol entity, which reassembles the old L2_ARQ PDUs into L3 PDUs and delivers them to the receiving L3 protocol entity.
- the old L2_ARQ PDUs After all the old L2_ARQ PDUs have been tunneled via the new L2 ARQ protocol entities to the old receiving
- L2_ARQ protocol entity reassembled into L3 PDUs, and then delivered to the receiving L3 protocol entity, the old L2_ARQ protocol entities are terminated.
- the above-described technique requires that a complete L3 PDU is either transmitted through the old sending L2_ARQ protocol entity or through the new sending L2_ARQ protocol entity.
- the last PDU in the old sending L2_ARQ protocol entity consists of a last segment of an old L3 PDU and possibly padding.
- the new receiving L2_ARQ protocol entity receives new L2_ARQ PDUs from the new sending L2_ARQ protocol entity and reassembles them into L2_ARQ SDUs.
- the new L2 ARQ protocol entities have to distinguish between L2_ARQ SDUs containing new L3 PDUs and L2 ARQ SDUs containing tunneled old
- L2_ARQ PDUs This can be achieved by marking the PDUs and/or the SDUs, or by other means of signaling.
- New L2_ARQ PDUs that contain tunneled old L2_ARQ PDUs are reassembled into old L2 ARQ PDUs and passed along to the old receiving L2_ARQ protocol entity.
- New L2_ARQ PDUs that contain new L3 PDUs are reassembled into L3 PDUs and delivered to the receiving L3 protocol entity.
- Figure 4 shows data being transferred between two L2_ARQ protocol entities over an air interface.
- Both the sending L2_ARQ protocol entity (i.e., L2_ARQ la) and the receiving L2_ARQ protocol entity (i.e., L2_ARQ lb) comprise an SDU data buffer 110 and a PDU data buffer 112. It shall be understood that these buffers are only logical buffers used for explaining the present invention.
- the data in the sending L2_ARQ protocol entity SDU data buffer 110a is higher layer data (i.e., L3 PDUs).
- the data in the sending L2_ARQ protocol entity PDU data buffer 112a consists of L2 ARQ PDUs.
- a PDU encapsulates either a part of an SDU or a full SDU. This is referred to as segmentation. If several SDUs are part of a PDU, then the several SDUs are referred to as being concatenated within the PDU.
- an SDU resides in the sending L2 ARQ protocol entity SDU data buffer 110a until it is segmented and potentially concatenated and transferred to the sending L2_ARQ protocol entity PDU data buffer 112a. At that point, the whole SDU is moved into the sending L2_ARQ protocol entity PDU data buffer 112a.
- the PDUs sent from the sending L2_ARQ protocol entity (i.e., L2_ARQ la) over the air interface have to be acknowledged by the receiving L2 ARQ protocol entity (i.e., L2 ARQ lb).
- the sending L2 ARQ protocol entity receives an acknowledgement for a PDU, that PDU is discarded from the sending L2_ARQ protocol entity PDU data buffer 112a.
- the sending L2_ARQ protocol entity PDU data buffer 112a may encapsulate both whole SDUs and parts of SDUs depending on what PDUs have been acknowledged by the sending
- L2_ARQ protocol entity The data in the receiving L2_ARQ protocol entity PDU data buffer 112b will reside there until a whole SDU can be assembled. At that point, the assembled SDU will be transferred to the receiving L2 ARQ protocol entity SDU data buffer 110b.
- Figure 5 shows data being transferred between two new L2_ARQ protocol entities over an air interface just after a handover or an L2_ARQ protocol reconfiguration has taken place in accordance with the present invention.
- Both the old sending L2 ARQ protocol entity i.e., L2 ARQ la
- the old receiving L2_ARQ protocol entity i.e., L2_ARQ lb
- both the new sending L2_ARQ protocol entity i.e., L2_ARQ lb
- L2_ARQ 2a and the new receiving L2_ARQ protocol entity comprise a new SDU data buffer 118 and a new PDU data buffer 120.
- the old sending L2_ARQ protocol entity determines if PDUs in the old sending L2_ARQ protocol entity PDU data buffer 116a need to be reassembled into SDUs. If so, the reassembled SDUs are transferred to the old sending L2_ARQ protocol entity SDU data buffer 114a.
- the old sending L2 ARQ protocol entity SDU data buffer 114a will then contain SDUs encapsulating L3 PDUs, which are denoted as SI in Figure 5.
- SDUs (SI) in the old sending L2_ARQ protocol entity SDU data buffer 114a are then transferred along path 115 to the new sending L2 ARQ protocol entity SDU buffer 118a.
- any PDUs remaining the old sending L2_ARQ protocol entity PDU data buffer 116a which are denoted as PI in Figure 5, are transferred along path 117 from the old sending L2_ARQ protocol entity PDU data buffer 116a to the new sending L2_ARQ protocol entity SDU data buffer 118a.
- PDUs (PI) from the old sending L2 ARQ protocol entity PDU data buffer 116a serve as SDUs in the new sending L2_ARQ protocol entity.
- new L3 PDUs are transferred directly between L3 and the new sending L2_ARQ protocol entity SDU data buffer 118a along path 119 after the handover/reconfiguration has occurred.
- the data in the new sending L2_ARQ protocol entity SDU data buffer 118a is segmented and sent to the new sending L2 ARQ protocol entity PDU data buffer 120a.
- the data in the new sending L2_ARQ protocol entity PDU data buffer 120a is sent across the air interface to the new receiving L2_ARQ protocol entity PDU data buffer 120b.
- the data in the new receiving L2_ARQ protocol entity PDU data buffer 120b is assembled and sent to the new receiving L2_ARQ protocol entity SDU data buffer 118b.
- the data in the new receiving L2 ARQ protocol entity SDU data buffer 118b is either sent to the receiving L3 protocol entity or is sent to the old receiving
- L2_ARQ protocol entity PDU data buffer 116b Any data in the old receiving L2_ARQ protocol entity PDU data buffer 116b is assembled and sent to the old receiving L2_ARQ protocol entity SDU data buffer 114b and then to the receiving L3 protocol entity.
- any data (PI) which was residing in the old sending L2_ARQ protocol entity PDU data buffer 116a and transferred along path 117 from the old sending L2_ARQ protocol entity PDU data buffer 116a to the new sending L2 ARQ protocol entity SDU data buffer 118a at the time of the handover/reconfiguration is logically tunneled through tunnel 121 from the old sending L2_ARQ protocol entity PDU data buffer 116a to the old receiving L2_ARQ protocol entity PDU data buffer 116b.
- the new sending L2 ARQ protocol entity only needs to signal the number of L2 ARQ SDUs, or the number of new L2_ARQ PDUs, that encapsulate the tunneled old L2_ARQ PDUs in order for the receiver to distinguish between L3
- L2_ARQ protocol entity will then implicitly know where to send each assembled L2_ARQ SDU without having marked the PDUs and/or the SDUs. If concatenation of several L2_ARQ SDUs within a L2_ARQ PDU is supported by the new L2 ARQ protocol entities, together with signaling the number of new L2_ARQ PDUs including tunneled old
- L2_ARQ PDUs L2_ARQ PDUs
- This rule defines that it is not possible to encapsulate a whole new L3 PDU in the last new L2_ARQ PDU including a tunneled old L2_ARQ PDU.
- One solution is to allow two separate L2_ARQ PDU types, one corresponding to the new L3 PDUs and one corresponding to the PDUs that originate from the old sending L2_ARQ protocol entity (see description of Figure 7 below).
- Another solution is to add a one bit field to the L2_ARQ SDU. This field can be set to one if the L2_ARQ SDU is actually a PDU from the old sending L2 ARQ protocol entity, and it can be cleared to zero if it is a new L3 PDU.
- the old and the new sending L2_ARQ protocol entities must be able to communicate with each other, just as the old and the new receiving L2 ARQ protocol entities must be able to communicate with each other.
- the communication links are logical links which can be divided into several physical links.
- the L2_ARQ network protocol entities could be in different nodes of the radio access network and the logical link could be established via several physical links involving several network nodes of the radio access network and/or the core network.
- both protocol entities could reside in the same node and even in the same hardware/software (e.g., in the same processing device wherein the logical link could be one or several device components (see Figure 9)).
- the old receiving L2 ARQ protocol entity In order to establish in-sequence delivery, the old receiving L2 ARQ protocol entity must signal to the new receiving L2_ARQ protocol entity that all of the old L2 ARQ PDUs are received correctly, reassembled into L3 PDUs, and delivered to the receiving L3 protocol entity. Only after that is the new receiving L2_ARQ protocol entity allowed to send SDUs to higher layers (i.e., the receiving L3 protocol entity).
- the old receiving L2 ARQ protocol entity needs to have knowledge about when the last old L2_ARQ PDU from the old sending L2 ARQ protocol entity has arrived.
- the present invention allows such information to be passed from the old sending L2_ARQ protocol entity to the old receiving
- tunneled old L2_ARQ PDUs are placed first in the new receiving L2_ARQ protocol entity SDU data buffer 118b combined with signaling of the number of PDUs or SDUs holding tunneled old L2_ARQ PDUs. Then the new receiving L2 ARQ protocol entity implicitly knows when there are no more tunneled old L2 ARQ PDUs coming because it must be able to distinguish between L2_ARQ SDUs encapsulating new L3 PDUs and L2_ARQ SDUs encapsulating tunneled old L2 ARQ PDUs.
- Another way to do this is to communicate the highest sequence number of the last old L2_ARQ PDU of the old sending L2 ARQ protocol entity to the old receiving L2_ARQ protocol entity.
- This sequence number may be transferred from the old sending L2 ARQ protocol entity to the old receiving L2 ARQ protocol entity via any appropriate signaling.
- a first solution to this would be to signal the sequence number through a control protocol entity. This implies of course that the old L2_ARQ protocol entities inform the control protocol entity about this sequence number.
- This special PDU (identified by a PDU Type field) containing the sequence number from the old sending L2_ARQ protocol entity to the old receiving L2_ARQ protocol entity.
- This special PDU could be the first message to be transmitted before any L2_ARQ PDUs are tunneled. This special PDU is sent via the tunnel as well.
- a third solution to this would be to send a special PDU (identified by a PDU
- This special PDU is sent via the tunnel as well.
- a fourth solution to this would be to send the sequence number in a special PDU (identified by a PDU Type field) containing the sequence number from the new sending L2_ARQ protocol entity to the new receiving L2_ARQ protocol entity.
- This special PDU would be the first message to be transmitted before any L2_ARQ PDUs are tunneled.
- the sequence number needs to be signaled from the old sending L2_ARQ protocol entity to the new sending L2 ARQ protocol entity and from the new receiving L2_ARQ protocol entity to the old receiving L2_ARQ protocol entity.
- the knowledge about when the last tunneled L2_ARQ PDU has been received is used on the receiving side to know when the old receiving L2_ARQ protocol entity may be terminated.
- the old receiving L2 ARQ protocol entity has to deliver all its data to the receiving L3 protocol entity and then indicate that it has finished before the new receiving L2_ARQ protocol entity may start delivering data to the receiving L3 protocol entity.
- FIG 6 there is shown a signaling chart 130 for a handover scenario in accordance with the present invention.
- the particular example shown in Figure 6 is based upon a UMTS system and involves a User Equipment Radio Resource Control protocol entity 132 (UE RRC), a first User Equipment Radio Link Control protocol entity 134 (UE RLC 1 ), a second User Equipment Radio Link Control protocol entity 136 (UE RLC2), a first Network Radio Link Control protocol entity 140 (NW RLCl), a second Network Radio Link Control protocol entity 138 (NW RLC2), a first Network Radio Resource Control protocol entity 142 (NW RRC 1 ), and a second Network Radio Resource Control protocol entity 144 (NW RRC2).
- UE RRC User Equipment Radio Resource Control protocol entity 132
- UE RLC 1 User Equipment Radio Link Control protocol entity
- UE RLC2 User Equipment Radio Link Control protocol entity 136
- NW RLCl Network Radio Link Control protocol entity 140
- NW RLC2 NW RLC2
- NW RRC 1 first Network Radio Resource Control protocol entity 142
- NW RRC 2 Network Radio Resource Control protocol entity 144
- the NW RRC1 entity 142 requests the NW RRC2 entity 144 to set up a new RLC protocol entity using a configuration request message 148 (RRC_RLC_CONFIG.req).
- the NWRRC2 entity 144 sets up the NW RLC2 entity 138 using a configuration request message 150 (CRLC_CONFIG.req).
- the NW RLC2 entity 138 has been set up, the NW
- RRC2 entity 144 confirms the creation of the NW RLC2 entity 138 with the NW RRCl entity 142 using a configuration confirmation message 152 (RRC_RLC_CONFIG.cfm).
- the NW RLCl entity 140 is then suspended by the NW RRCl entity 142 using a suspension request message 154 (CRLC_SUSPEND.req), which causes the NW RLCl entity 140 to stop transmitting data and enter into the tunneling state described above.
- the unsegmented SDUs in the NW RLC 1 entity 140 are sent to the SDU buffer of the NW RLC2 entity 138 via an SDU transfer message 156 (SDU TRANSFER).
- a cell update confirmation message 158 (CELL UPDATE CONFIRM) is then sent from the NW RRCl entity 142 to the UE RRC entity 132.
- the cell update confirmation message 158 (CELL UPDATE CONFIRM) may contain an indication of the sequence number of the last PDU in the NW RLCl entity 140.
- the UE RRC entity 132 Upon receipt of the cell update confirmation message 158 (CELL UPDATE CONFIRM), the UE RRC entity 132 sets up the UE RLC2 entity 136 using a configuration request message 160 (CRLC_CONFIG.req). In addition, the UE RLC 1 entity 134 is suspended by the UE RRC entity 132 using a suspension request message 162 (CRLC_SUSPEND.req), which causes the UE RLCl entity 134 to stop transmitting data and enter into the tunneling state described above. Next, the unsegmented SDUs in the UE RLCl entity 134 are sent to the SDU buffer of the UE RLC2 entity 136 via an SDU transfer message 164 (SDU TRANSFER).
- SDU TRANSFER SDU transfer message
- a cell update completion message 166 (CELL UPDATE COMPLETE) is then sent from the UE RRC entity 132 to the NW RRCl entity 142.
- the cell update completion message 166 (CELL UPDATE COMPLETE) may contain an indication of the sequence number of the last PDU in the UE RLCl entity 134. At this point, there is no data transfer between the UE RLC 1 entity 134 and the
- NW RLCl entity 140 That is, the UE RLC2 entity 136 and the NW RLC2 entity 138 now perform the data transfer functions. However, any data remaining in the UE RLCl entity 134 may now be tunneled through the UE RLC2 entity 136 once the UE RLCl entity 134 receives a tunneling request message 168 (CRLC_TUNNELLNG.req) from the UE RRC entity 132. Likewise, any data remaining in the NW RLC 1 entity
- the UE RLC 1 entity 134 sends a status report message 172 (STATUS) to the NW RLCl entity 140, while the NW RLCl entity 140 sends a status report message 174 (STATUS) to the UE RLCl entity 134.
- the status report message 172 may also contain an indication of the sequence number of the last PDU in the UE RLCl entity 134.
- the status report message 174 may also contain an indication of the sequence number of the last PDU in the NW RLC 1 entity 140.
- the UE RLC 1 entity 134 After all the data in the UE RLC 1 entity 134 has been tunneled and transmitted correctly, the UE RLC 1 entity 134 indicates the same to the UE RRC entity 132 using a configuration indication message 176 (CRLC_CONFIG.ind). The UE RRC entity 132 then releases the UE RLC 1 entity 134 using a configuration request message 180 (CRLC_CONFIG.req). Similarly, after all the data in the NW RLCl entity 140 has been tunneled and transmitted correctly, the NW RLCl entity 140 indicates the same to the NW RRCl entity 142 using a configuration indication message 178 (CRLC_CONFIG.ind). The NW RRCl entity 142 then releases the NW RLCl entity 140 using a configuration request message 182 (CRLC_CONFIG.req). At this point it should be noted that if in-sequence delivery is necessary, the
- the UE RLC2 entity 136 and the NW RLC2 entity 138 should be notified that all UE RLCl PDUs and all NW RLCl PDUs have been received, respectively. After that, the UE RLC2 entity 136 and the NW RLC2 entity 138 can send the UE RLC2 SDUs and the NW RLC2 SDUs to higher layers, respectively. At this point it should also be noted that the suspension request message 154
- CRLC_SUSPEND.req the suspension request message 162
- CRLC SUSPEND.req the suspension request message 162
- a protocol entity may be suspended, and then later may be resumed.
- the RLCl entities 134 and 140 do not resume, but rather enter a tunneling state.
- L2_ARQ Acknowledged Mode Data (AMD) PDU 190 wherein L2_ARQ could be, for example, a Radio Link Control (RLC) protocol entity.
- the AMD PDU 190 includes a data/control (D/C) bit 192, indicating if the PDU is an AMD PDU or a Control PDU, a sequence number (SN) field 194, a poll (P) bit 196, a header compression (H) bit 198, one or more extension (E) bits 200, zero or more length indicator fields 202, one or more data segments 204, and an optional field 206 containing padding (PAD) or a piggybacked status PDU (STATUS PDU).
- D/C data/control
- SN sequence number
- P poll
- H header compression
- E extension bits 200
- PID piggybacked status PDU
- STATUS PDU piggybacked status PDU
- the extension bits 200 and the length indicator fields 202 can be of particular interest with respect to the present invention.
- the extension bit 200a indicates whether the next field will be data or a length indicator.
- the length indicator field 202 is used when concatenation or padding takes place in the PDU. In either case, it indicates where the concatenation or padding starts. If concatenation takes place, the length indicator field 202 indicates the border between the two higher layer segments. If padding takes place, the length indicator field 202 is assigned a specific value.
- the extension bit 200b is then set to indicate that the next octet will be yet another length indicator. The length indicator field 202 will then indicate the border between data and padding.
- One of the length indicator fields 202 can also be used to indicate whether the data segments 204 contain tunneled RLC PDUs or L3 PDUs. To indicate the transport of tunneled RLC PDUs, the length indicator field 202 can be assigned a specific and reserved value.
- L2 ARQ Control PDU 220 includes a data/control (D/C) bit 222, indicating if the PDU is an AMD PDU or a Control PDU, a PDU Type field 224, specifying the type of control message, a reserved field 226, zero or more Specific Control Fields 228, depending on the type of control message, and padding (PAD) 230 to fill in the rest of the Control PDU 220.
- D/C data/control
- PDU Type field 224 specifying the type of control message
- padding (PAD) 230 to fill in the rest of the Control PDU 220.
- the Control PDU 220 can be used to transfer the sequence number of the last untransmitted segmented L2_ARQ PDU of the old sending L2_ARQ protocol entity to the old receiving L2_ARQ protocol entity.
- the control message can be defined as either a PDU of the old L2_ARQ link, which is then tunneled via the new L2 ARQ link, or a PDU of the new L2_ARQ link, in which case a sequence number is signaled between the old and new L2_ARQ protocol entities.
- a specific value for the PDU Type field 224 is defined and the Specific Control Field 228 contains the sequence number.
- each of the above-described protocol entities may have an associated processing device 210 having at least one processor (P) 212, memory (M)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP00946731A EP1195036B1 (en) | 1999-07-08 | 2000-07-07 | Technique for providing a secure link in a mobile communication system |
AU60444/00A AU6044400A (en) | 1999-07-08 | 2000-07-07 | Technique for providing a secure link in a mobile communication system |
JP2001510213A JP4536976B2 (en) | 1999-07-08 | 2000-07-07 | Technology for providing a reliable link in a mobile communication system |
DE60030442T DE60030442T2 (en) | 1999-07-08 | 2000-07-07 | METHOD FOR PROVIDING A SAFE CONNECTION IN A MOBILE COMMUNICATION SYSTEM |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/349,899 | 1999-07-08 | ||
US09/349,899 US6301479B1 (en) | 1999-07-08 | 1999-07-08 | Technique for providing a secure link in a mobile communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2001005121A1 true WO2001005121A1 (en) | 2001-01-18 |
Family
ID=23374443
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2000/001461 WO2001005121A1 (en) | 1999-07-08 | 2000-07-07 | Technique for providing a secure link in a mobile communication system |
Country Status (11)
Country | Link |
---|---|
US (1) | US6301479B1 (en) |
EP (1) | EP1195036B1 (en) |
JP (1) | JP4536976B2 (en) |
KR (1) | KR100604679B1 (en) |
CN (1) | CN1171428C (en) |
AR (1) | AR026867A1 (en) |
AT (1) | ATE338412T1 (en) |
AU (1) | AU6044400A (en) |
DE (1) | DE60030442T2 (en) |
MY (1) | MY124992A (en) |
WO (1) | WO2001005121A1 (en) |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2820598A1 (en) * | 2001-02-08 | 2002-08-09 | Cit Alcatel | METHOD FOR OPTIMIZING DATA TRANSFER IN A CELLULAR MOBILE RADIO COMMUNICATION SYSTEM |
WO2002080604A1 (en) * | 2001-03-28 | 2002-10-10 | Nokia Corporation | Method for providing parameters during a change of access, cellular communications system, user equipment and network element |
EP1253736A3 (en) * | 2001-04-26 | 2003-12-10 | NTT DoCoMo, Inc. | Data link transmission control for mobile communications |
WO2004030396A1 (en) | 2002-09-24 | 2004-04-08 | Fujitsu Limited | Packet transferring and transmitting method and mobile communication system |
EP1493288A2 (en) * | 2002-04-05 | 2005-01-05 | Interdigital Technology Corporation | System for efficient recovery of node b buffered data following serving high speed downlink shared channel cell change |
JP2005510950A (en) * | 2001-11-28 | 2005-04-21 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Retransmission method and retransmission system |
EP1868408A2 (en) | 2006-06-14 | 2007-12-19 | NEC Corporation | Mobile communications system and method for transmitting data when handover occurs |
EP1871054A1 (en) * | 2006-06-19 | 2007-12-26 | Innovative Sonic Limited | Method and apparatus for handling downlink data upon handover in a wireless communications system |
EP1940095A2 (en) * | 2002-04-05 | 2008-07-02 | Interdigital Technology Corporation | System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change |
EP1946460A1 (en) * | 2005-10-31 | 2008-07-23 | LG Electronics Inc. | Data transfer management in a radio communications network |
EP1954090A1 (en) * | 2007-02-05 | 2008-08-06 | Alcatel Lucent | A method for handover of a user terminal |
WO2008094662A2 (en) * | 2007-02-01 | 2008-08-07 | Interdigital Technology Corporation | Method and apparatus for supporting rlc re-segmentation |
EP1959601A1 (en) * | 2007-02-13 | 2008-08-20 | Matsushita Electric Industrial Co., Ltd. | Retransmission scheme to exchange control information between a gateway and a mobile node |
EP1983698A1 (en) * | 2007-04-20 | 2008-10-22 | Matsushita Electric Industrial Co., Ltd. | Improved transmission scheme of protocol data units during a procedure that comprises the reset of the protocol layer |
US7522560B2 (en) | 2001-02-09 | 2009-04-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, system and equipment for retransmission in communications systems |
EP2117269A1 (en) * | 2008-05-10 | 2009-11-11 | Research In Motion Limited | method and system for transitioning between radio access technologies (RATS) |
CN101674618A (en) * | 2002-09-24 | 2010-03-17 | 富士通株式会社 | Packet transmission/delivery method and mobile communication system |
US7706405B2 (en) | 2002-09-12 | 2010-04-27 | Interdigital Technology Corporation | System for efficient recovery of Node-B buffered data following MAC layer reset |
CN101730168A (en) * | 2002-09-24 | 2010-06-09 | 富士通株式会社 | Data packet transmitting/sending method and mobile communication system |
US7839834B2 (en) | 2004-06-18 | 2010-11-23 | Qualcomm Incorporated | Radio link protocols for a wireless communication system |
DE202012003490U1 (en) | 2012-04-04 | 2012-04-23 | Hans-Jürgen Koch | Light / acoustic screen |
US8254935B2 (en) | 2002-09-24 | 2012-08-28 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
US8374148B2 (en) | 2003-01-23 | 2013-02-12 | Samsung Electronics Co., Ltd. | Handoff method in wireless LAN, and access point and mobile station performing handoff method |
US8867449B2 (en) | 2006-01-05 | 2014-10-21 | Lg Electronics Inc. | Transmitting data in a mobile communication system |
US8971288B2 (en) | 2006-03-22 | 2015-03-03 | Lg Electronics Inc. | Method of supporting handover in a wireless communication system |
US9220093B2 (en) | 2006-06-21 | 2015-12-22 | Lg Electronics Inc. | Method of supporting data retransmission in a mobile communication system |
US9462576B2 (en) | 2006-02-07 | 2016-10-04 | Lg Electronics Inc. | Method for transmitting response information in mobile communications system |
US9516573B2 (en) | 2005-10-31 | 2016-12-06 | Lg Electronics Inc. | Data transfer management in a radio communications network |
NO339864B1 (en) * | 2002-04-05 | 2017-02-13 | Intel Corp | User equipment and handover procedures |
Families Citing this family (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19849578A1 (en) * | 1998-10-27 | 2000-01-13 | Siemens Ag | Method and cellular network for handling a packet data service |
EP1014641A1 (en) * | 1998-12-22 | 2000-06-28 | Telefonaktiebolaget Lm Ericsson | Method and system for reducing the processing time of data in communication networks |
EP1056258A1 (en) * | 1999-05-27 | 2000-11-29 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Data unit sending means and control method in wireless networks |
FI109169B (en) * | 1999-07-02 | 2002-05-31 | Nokia Corp | Providing control signaling in a telecommunications system |
GB9921706D0 (en) * | 1999-09-14 | 1999-11-17 | Nokia Telecommunications Oy | Relocation in a communication system |
US6622019B1 (en) * | 1999-11-17 | 2003-09-16 | Eci Telecom, Ltd. | Increasing channel capacity in fixed cellular networks |
DE69926514T2 (en) * | 1999-11-23 | 2006-06-08 | Lucent Technologies Inc. | A method, apparatus and data packet for displaying the length of the payload transmitted in a data packet in a cellular network |
FI109255B (en) * | 2000-04-07 | 2002-06-14 | Nokia Corp | Numbering of data packets during packet switching data transfer |
KR100519612B1 (en) * | 2000-04-07 | 2005-10-07 | 노키아 코포레이션 | Transmission of the fixed size PDUs through the transparent RLC |
US6799039B2 (en) * | 2000-04-17 | 2004-09-28 | Nortel Networks Limited | Network resource sharing during handover of a mobile station between cellular wireless networks |
US6671507B1 (en) * | 2000-06-16 | 2003-12-30 | Siemens Aktiengesellschaft | Authentication method for inter-system handover between at least two radio communications systems |
EP1198107B1 (en) * | 2000-10-07 | 2012-11-28 | LG Electronics Inc. | Method for transmitting data from an RLC layer in a radio communication system |
US6731939B1 (en) * | 2000-10-20 | 2004-05-04 | Nokia Corporation | Apparatus, and associated method, for allocating channels in a radio communication system |
DE10054473A1 (en) * | 2000-11-03 | 2002-05-08 | Siemens Ag | Method for exchanging data packets between two service providers of a radio transmission system |
GB2369961B (en) * | 2000-12-09 | 2003-04-23 | Ericsson Telefon Ab L M | Transmission control in a radio access network |
US6788944B2 (en) * | 2001-04-02 | 2004-09-07 | Asustek Computer Inc. | Length indicator for a protocol data unit in a wireless communications protocol |
US6775533B2 (en) * | 2001-07-27 | 2004-08-10 | Nokia Corporation | Apparatus, and associated method, for transferring data between a first target entity and a second target entity of a mobile radio communication system |
US7220365B2 (en) * | 2001-08-13 | 2007-05-22 | New Qu Energy Ltd. | Devices using a medium having a high heat transfer rate |
US6811720B2 (en) * | 2001-08-13 | 2004-11-02 | New Qu Energy Ltd. | Medium having a high heat transfer rate |
US20030039226A1 (en) * | 2001-08-24 | 2003-02-27 | Kwak Joseph A. | Physical layer automatic repeat request (ARQ) |
US6862082B1 (en) * | 2001-10-05 | 2005-03-01 | Cisco Technology, Inc. | System and method for handover execution in a wireless environment |
US7269448B2 (en) * | 2001-11-09 | 2007-09-11 | Electronics And Telecommunications Research Institute | Method for recognizing request for data transmission by mobile/base station RRC using network transfer device |
EP1452041B1 (en) * | 2001-12-04 | 2010-10-27 | Nokia Siemens Networks GmbH & Co. KG | Method and network device for running especially personalised communication services in a communication system |
EP1326460A1 (en) * | 2001-12-21 | 2003-07-09 | Siemens Aktiengesellschaft | Method and system of handover in a cellular packet network |
US20040054766A1 (en) * | 2002-09-16 | 2004-03-18 | Vicente John B. | Wireless resource control system |
US7376567B2 (en) * | 2004-02-16 | 2008-05-20 | Celtro Ltd | Method and system for efficiently transmitting encoded communication signals |
CN1299479C (en) * | 2004-03-10 | 2007-02-07 | 中兴通讯股份有限公司 | Slicing transmitting method of tunnel packet |
KR100989314B1 (en) * | 2004-04-09 | 2010-10-25 | 삼성전자주식회사 | display apparatus |
GB2417862B (en) * | 2004-09-01 | 2009-09-09 | Samsung Electronics Co Ltd | Adaptive ARQ system |
US7961683B2 (en) * | 2004-09-30 | 2011-06-14 | Alcatel-Lucent Usa Inc. | Active session mobility solution for point-to-point protocol |
US8316416B2 (en) | 2005-04-04 | 2012-11-20 | Research In Motion Limited | Securely using a display to exchange information |
US7656835B2 (en) * | 2005-05-18 | 2010-02-02 | Nokia Corporation | Method for informing changed communications capabilities |
KR100810207B1 (en) | 2005-07-22 | 2008-03-06 | 삼성전자주식회사 | Handover method between core network entities in packet-switched based network and therefor apparatus |
KR100723885B1 (en) * | 2005-12-08 | 2007-05-31 | 한국전자통신연구원 | Method and apparatus for seamless handover of mobile node using msctp |
KR100912784B1 (en) | 2006-01-05 | 2009-08-18 | 엘지전자 주식회사 | Data transmission method and data retransmission method |
KR101268200B1 (en) | 2006-01-05 | 2013-05-27 | 엘지전자 주식회사 | Radio resource allocating method in mobile communication system |
KR101211807B1 (en) | 2006-01-05 | 2012-12-12 | 엘지전자 주식회사 | Method for managing synchronization state for mobile terminal in mobile communication system |
ES2459371T3 (en) | 2006-01-05 | 2014-05-09 | Lg Electronics Inc. | Transmission of information in a mobile communications system |
KR101333918B1 (en) | 2006-01-05 | 2013-11-27 | 엘지전자 주식회사 | Point-to-multipoint service communication of mobile communication system |
KR101216751B1 (en) | 2006-02-07 | 2012-12-28 | 엘지전자 주식회사 | Method for avoiding collision using identifier in mobile network |
KR101358469B1 (en) | 2006-02-07 | 2014-02-06 | 엘지전자 주식회사 | Method for selection and signaling of downlink and uplink bandwidth in wireless networks |
US8670566B2 (en) | 2006-05-12 | 2014-03-11 | Blackberry Limited | System and method for exchanging encryption keys between a mobile device and a peripheral output device |
WO2007144757A2 (en) * | 2006-06-16 | 2007-12-21 | Nokia Corporation | An apparatus and method for transferring pdp context information for a terminal in the case of intersystem handover |
KR20070121505A (en) | 2006-06-21 | 2007-12-27 | 엘지전자 주식회사 | Method for reconfiguring radio link |
CN101473565B (en) | 2006-06-21 | 2012-11-07 | Lg电子株式会社 | Method of transmitting and receiving radio access information using a message separation in a wireless mobile communications system |
KR20070121513A (en) | 2006-06-21 | 2007-12-27 | 엘지전자 주식회사 | Uplink access method of mobile communication system |
KR101369135B1 (en) | 2006-06-21 | 2014-03-05 | 엘지전자 주식회사 | Mehtod for supproting quality of multimeida broadcast multicast service(mbms) in mobile communications system and terminal thereof |
KR100953151B1 (en) * | 2006-11-30 | 2010-04-19 | 이노베이티브 소닉 리미티드 | Method of enhancing continuous packet connectivity in a wireless communications system and related apparatus |
US8660085B2 (en) | 2006-12-04 | 2014-02-25 | Qualcomm Incorporated | Methods and apparatus for transferring a mobile device from a source eNB to a target eNB |
KR100957420B1 (en) * | 2006-12-15 | 2010-05-11 | 삼성전자주식회사 | Method for transmitting and receiving signal in wireless communication system and system thereof |
WO2008078381A1 (en) * | 2006-12-25 | 2008-07-03 | Fujitsu Limited | Radio communication system, radio base station, and radio communication method |
US8797995B2 (en) * | 2007-01-18 | 2014-08-05 | Cisco Technology, Inc. | Device-assisted layer 3 handoff for mobile services |
JP4896073B2 (en) * | 2007-05-15 | 2012-03-14 | イノヴァティヴ ソニック リミテッド | Method and apparatus for polling data transmission status in a wireless communication system |
FR2916598A1 (en) * | 2007-05-24 | 2008-11-28 | Thomson Licensing Sas | METHOD FOR TRANSMITTING DATA PACKETS AND CORRESPONDING RECEPTION METHOD |
FR2916591A1 (en) * | 2007-05-24 | 2008-11-28 | Thomson Licensing Sas | METHOD FOR RECEIVING DATA PACKETS AND METHOD FOR TRANSMITTING THE SAME |
WO2009103189A1 (en) * | 2008-02-21 | 2009-08-27 | Alcatel Shanghai Bell Co., Ltd. | Method, user equipment and communication system for inter-rat handover in 3g lte |
EP2656556B1 (en) * | 2010-12-21 | 2018-02-21 | Telefonaktiebolaget LM Ericsson (publ) | An improvement on ip fragmentation in gtp tunnel |
JP6140960B2 (en) * | 2012-09-25 | 2017-06-07 | 株式会社Nttドコモ | Mobile communication method |
JP6389126B2 (en) * | 2013-03-12 | 2018-09-12 | パナソニック株式会社 | Wireless communication apparatus and transmission frame control method |
WO2017151022A1 (en) * | 2016-02-29 | 2017-09-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Enhancement of relay arq in mmw network |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1998047302A2 (en) * | 1997-04-15 | 1998-10-22 | Nokia Networks Oy | Method of avoiding packet loss at a handover in a packet-based telecommunications network and handover method |
WO1999034635A2 (en) * | 1997-12-30 | 1999-07-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for improving the handing over a connection from one sgsn to another sgsn |
-
1999
- 1999-07-08 US US09/349,899 patent/US6301479B1/en not_active Expired - Lifetime
-
2000
- 2000-06-28 MY MYPI20002946 patent/MY124992A/en unknown
- 2000-07-07 AR ARP000103489A patent/AR026867A1/en active IP Right Grant
- 2000-07-07 AT AT00946731T patent/ATE338412T1/en not_active IP Right Cessation
- 2000-07-07 AU AU60444/00A patent/AU6044400A/en not_active Abandoned
- 2000-07-07 JP JP2001510213A patent/JP4536976B2/en not_active Expired - Lifetime
- 2000-07-07 KR KR1020027000077A patent/KR100604679B1/en not_active IP Right Cessation
- 2000-07-07 WO PCT/SE2000/001461 patent/WO2001005121A1/en active IP Right Grant
- 2000-07-07 DE DE60030442T patent/DE60030442T2/en not_active Expired - Lifetime
- 2000-07-07 EP EP00946731A patent/EP1195036B1/en not_active Expired - Lifetime
- 2000-07-07 CN CNB00809926XA patent/CN1171428C/en not_active Expired - Lifetime
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1998047302A2 (en) * | 1997-04-15 | 1998-10-22 | Nokia Networks Oy | Method of avoiding packet loss at a handover in a packet-based telecommunications network and handover method |
WO1999034635A2 (en) * | 1997-12-30 | 1999-07-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for improving the handing over a connection from one sgsn to another sgsn |
Cited By (75)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1231742A1 (en) * | 2001-02-08 | 2002-08-14 | Alcatel | Optimization method of transferring data in a mobile cellular radio communication system |
FR2820598A1 (en) * | 2001-02-08 | 2002-08-09 | Cit Alcatel | METHOD FOR OPTIMIZING DATA TRANSFER IN A CELLULAR MOBILE RADIO COMMUNICATION SYSTEM |
US7522560B2 (en) | 2001-02-09 | 2009-04-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, system and equipment for retransmission in communications systems |
WO2002080604A1 (en) * | 2001-03-28 | 2002-10-10 | Nokia Corporation | Method for providing parameters during a change of access, cellular communications system, user equipment and network element |
CN100442862C (en) * | 2001-04-26 | 2008-12-10 | 株式会社Ntt都科摩 | Data chain transmitting control method, mobile communication system, data chain transmitting controller, base station, mobile station and its controller |
EP1253736A3 (en) * | 2001-04-26 | 2003-12-10 | NTT DoCoMo, Inc. | Data link transmission control for mobile communications |
EP2068488A3 (en) * | 2001-04-26 | 2011-05-04 | NTT DoCoMo, Inc. | Data link transmission control methods, mobile communication systems, data link transmission control apparatus, base stations, mobile stations, mobile station control programs, and computer-readable recording media |
JP2005510950A (en) * | 2001-11-28 | 2005-04-21 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Retransmission method and retransmission system |
EP1940095A2 (en) * | 2002-04-05 | 2008-07-02 | Interdigital Technology Corporation | System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change |
NO339864B1 (en) * | 2002-04-05 | 2017-02-13 | Intel Corp | User equipment and handover procedures |
CN101702819A (en) * | 2002-04-05 | 2010-05-05 | 美商内数位科技公司 | User equipment, node b and method |
US8837431B2 (en) | 2002-04-05 | 2014-09-16 | Intel Corporation | HS-DSCH inter-node B cell change |
EP3002971A1 (en) * | 2002-04-05 | 2016-04-06 | Intel Corporation | System for efficient recovery of node b buffered data following serving high speed downlink shared channel cell change |
EP1940095A3 (en) * | 2002-04-05 | 2012-12-26 | Intel Corporation | System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change |
US8130721B2 (en) | 2002-04-05 | 2012-03-06 | Interdigital Technology Corporation | HS-DSCH inter-node B cell change |
US9220037B2 (en) | 2002-04-05 | 2015-12-22 | Intel Corporation | HS-DSCH inter-node B cell change |
US8085728B2 (en) | 2002-04-05 | 2011-12-27 | Interdigital Technology Corporation | High speed downlink shared control channel cell change |
CN101702819B (en) * | 2002-04-05 | 2014-08-27 | 英特尔公司 | User equipment, node b and method |
US9565603B2 (en) | 2002-04-05 | 2017-02-07 | Intel Corporation | HS-DSCH inter-node B cell change |
US8085729B2 (en) | 2002-04-05 | 2011-12-27 | Interdigital Technology Corporation | High speed downlink shared control channel cell change |
EP1493288A4 (en) * | 2002-04-05 | 2006-05-31 | Interdigital Tech Corp | System for efficient recovery of node b buffered data following serving high speed downlink shared channel cell change |
US8085726B2 (en) | 2002-04-05 | 2011-12-27 | Interdigital Technology Corporation | High speed downlink shared channel cell change |
EP1493288A2 (en) * | 2002-04-05 | 2005-01-05 | Interdigital Technology Corporation | System for efficient recovery of node b buffered data following serving high speed downlink shared channel cell change |
US10172048B2 (en) | 2002-09-12 | 2019-01-01 | Interdigital Technology Corporation | System for efficient recovery of node-B buffered data following MAC layer reset |
US7706405B2 (en) | 2002-09-12 | 2010-04-27 | Interdigital Technology Corporation | System for efficient recovery of Node-B buffered data following MAC layer reset |
US8693435B2 (en) | 2002-09-12 | 2014-04-08 | Interdigital Technology Corporation | System for efficient recovery of node-B buffered data following MAC layer reset |
US9319946B2 (en) | 2002-09-12 | 2016-04-19 | Interdigital Technology Corporation | System for efficient recovery of Node-B buffered data following MAC layer reset |
EP1545143A4 (en) * | 2002-09-24 | 2008-04-23 | Fujitsu Ltd | Packet transferring and transmitting method and mobile communication system |
US8254935B2 (en) | 2002-09-24 | 2012-08-28 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
EP2178327A1 (en) | 2002-09-24 | 2010-04-21 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
CN101674618A (en) * | 2002-09-24 | 2010-03-17 | 富士通株式会社 | Packet transmission/delivery method and mobile communication system |
WO2004030396A1 (en) | 2002-09-24 | 2004-04-08 | Fujitsu Limited | Packet transferring and transmitting method and mobile communication system |
CN101730168A (en) * | 2002-09-24 | 2010-06-09 | 富士通株式会社 | Data packet transmitting/sending method and mobile communication system |
EP2237608A1 (en) * | 2002-09-24 | 2010-10-06 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
EP2051553A1 (en) * | 2002-09-24 | 2009-04-22 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
EP1545143A1 (en) * | 2002-09-24 | 2005-06-22 | Fujitsu Limited | Packet transferring and transmitting method and mobile communication system |
EP2051552A1 (en) * | 2002-09-24 | 2009-04-22 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
EP2139281A3 (en) * | 2002-09-24 | 2010-04-14 | Fujitsu Limited | Packet transferring/transmitting method and mobile communication system |
US8374148B2 (en) | 2003-01-23 | 2013-02-12 | Samsung Electronics Co., Ltd. | Handoff method in wireless LAN, and access point and mobile station performing handoff method |
US7839834B2 (en) | 2004-06-18 | 2010-11-23 | Qualcomm Incorporated | Radio link protocols for a wireless communication system |
US10129795B2 (en) | 2005-10-31 | 2018-11-13 | Lg Electronics Inc. | Data transfer management in a radio communications network |
EP1946460A4 (en) * | 2005-10-31 | 2012-09-19 | Lg Electronics Inc | Data transfer management in a radio communications network |
EP1946460A1 (en) * | 2005-10-31 | 2008-07-23 | LG Electronics Inc. | Data transfer management in a radio communications network |
US9930580B2 (en) | 2005-10-31 | 2018-03-27 | Lg Electronics Inc. | Data transfer management in a radio communications network |
US9516573B2 (en) | 2005-10-31 | 2016-12-06 | Lg Electronics Inc. | Data transfer management in a radio communications network |
US9036596B2 (en) | 2006-01-05 | 2015-05-19 | Lg Electronics Inc. | Transmitting data in a mobile communication system |
US8867449B2 (en) | 2006-01-05 | 2014-10-21 | Lg Electronics Inc. | Transmitting data in a mobile communication system |
US9397791B2 (en) | 2006-01-05 | 2016-07-19 | Lg Electronics Inc. | Transmitting data in a mobile communication system |
US10045381B2 (en) | 2006-02-07 | 2018-08-07 | Lg Electronics Inc. | Method for transmitting response information in mobile communications system |
US9462576B2 (en) | 2006-02-07 | 2016-10-04 | Lg Electronics Inc. | Method for transmitting response information in mobile communications system |
US9706580B2 (en) | 2006-02-07 | 2017-07-11 | Lg Electronics Inc. | Method for transmitting response information in mobile communications system |
US8971288B2 (en) | 2006-03-22 | 2015-03-03 | Lg Electronics Inc. | Method of supporting handover in a wireless communication system |
EP1868408A3 (en) * | 2006-06-14 | 2010-01-13 | NEC Corporation | Mobile communications system and method for transmitting data when handover occurs |
EP1868408A2 (en) | 2006-06-14 | 2007-12-19 | NEC Corporation | Mobile communications system and method for transmitting data when handover occurs |
US8781470B2 (en) | 2006-06-14 | 2014-07-15 | Nec Corporation | Mobile communications system and method for transmitting data when handover occurs |
CN101094446B (en) * | 2006-06-14 | 2012-02-29 | 日本电气株式会社 | Mobile communications system and method for transmitting data when handover occurs |
EP1871054A1 (en) * | 2006-06-19 | 2007-12-26 | Innovative Sonic Limited | Method and apparatus for handling downlink data upon handover in a wireless communications system |
US9220093B2 (en) | 2006-06-21 | 2015-12-22 | Lg Electronics Inc. | Method of supporting data retransmission in a mobile communication system |
WO2008094662A3 (en) * | 2007-02-01 | 2009-02-26 | Interdigital Tech Corp | Method and apparatus for supporting rlc re-segmentation |
US7817669B2 (en) | 2007-02-01 | 2010-10-19 | Interdigital Technology Corporation | Method and apparatus for supporting RLC re-segmentation |
US10382181B2 (en) | 2007-02-01 | 2019-08-13 | Intel Corporation | Method and apparatus for supporting AMD re-segmentation |
US8897216B2 (en) | 2007-02-01 | 2014-11-25 | Intel Corporation | Method and apparatus for supporting AMD re-segmentation |
WO2008094662A2 (en) * | 2007-02-01 | 2008-08-07 | Interdigital Technology Corporation | Method and apparatus for supporting rlc re-segmentation |
US9806867B2 (en) | 2007-02-01 | 2017-10-31 | Intel Corporation | Method and apparatus for supporting AMD re-segmentation |
US9774434B2 (en) | 2007-02-01 | 2017-09-26 | Intel Corporation | Method and apparatus for supporting AMD re-segmentation |
EP1954090A1 (en) * | 2007-02-05 | 2008-08-06 | Alcatel Lucent | A method for handover of a user terminal |
EP1959601A1 (en) * | 2007-02-13 | 2008-08-20 | Matsushita Electric Industrial Co., Ltd. | Retransmission scheme to exchange control information between a gateway and a mobile node |
WO2008098738A1 (en) * | 2007-02-13 | 2008-08-21 | Panasonic Corporation | Retransmission scheme to exchange control information between a gateway and a mobile node |
EP1983698A1 (en) * | 2007-04-20 | 2008-10-22 | Matsushita Electric Industrial Co., Ltd. | Improved transmission scheme of protocol data units during a procedure that comprises the reset of the protocol layer |
WO2008128597A1 (en) * | 2007-04-20 | 2008-10-30 | Panasonic Corporation | Improved transmission scheme of protocol data units during a procedure that comprises the reset of the protocol layer |
US9554306B2 (en) | 2008-05-10 | 2017-01-24 | Blackberry Limited | Method and system for transitioning between radio access technologies (RATS) |
US8730909B2 (en) | 2008-05-10 | 2014-05-20 | Blackberry Limited | Method and system for transitioning between radio access technologies (RATS) |
EP2117269A1 (en) * | 2008-05-10 | 2009-11-11 | Research In Motion Limited | method and system for transitioning between radio access technologies (RATS) |
US9282492B2 (en) | 2008-05-10 | 2016-03-08 | Blackberry Limited | Method and system for transitioning between radio access technologies (RATS) |
DE202012003490U1 (en) | 2012-04-04 | 2012-04-23 | Hans-Jürgen Koch | Light / acoustic screen |
Also Published As
Publication number | Publication date |
---|---|
EP1195036A1 (en) | 2002-04-10 |
AU6044400A (en) | 2001-01-30 |
KR20020026519A (en) | 2002-04-10 |
AR026867A1 (en) | 2003-03-05 |
DE60030442T2 (en) | 2007-03-29 |
DE60030442D1 (en) | 2006-10-12 |
JP2003504968A (en) | 2003-02-04 |
CN1171428C (en) | 2004-10-13 |
KR100604679B1 (en) | 2006-07-26 |
EP1195036B1 (en) | 2006-08-30 |
MY124992A (en) | 2006-07-31 |
US6301479B1 (en) | 2001-10-09 |
JP4536976B2 (en) | 2010-09-01 |
ATE338412T1 (en) | 2006-09-15 |
CN1359581A (en) | 2002-07-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1195036B1 (en) | Technique for providing a secure link in a mobile communication system | |
US11805443B2 (en) | Method and apparatus for data processing in wireless communication system | |
US9860915B2 (en) | Apparatus and method for moving a receive window in a radio access network | |
JP5541469B2 (en) | Handover processing | |
EP2369795B1 (en) | Method and apparatus for performing handover using packet data convergence protocol (pdcp) reordering in mobile communication system | |
JP4376486B2 (en) | Data packet number addition method for packet-switched data transmission | |
US8681712B2 (en) | Efficient AM RLC re-establishment mechanism | |
US8588784B2 (en) | Mobile communication system, wireless base station and hand over reconnection method for use therewith including an accumulation portion for holding data | |
US8400982B2 (en) | Method for handling correctly received but header compression failed packets | |
KR20160081915A (en) | Method and apparatus for reconfiguring a bearer | |
KR100421863B1 (en) | Data Transmission method for a radio communications system, and apparatus for the same | |
WO2008004724A1 (en) | Efficient am rlc re-establishment mechanism |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2000946731 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020027000077 Country of ref document: KR Ref document number: 00809926X Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2000946731 Country of ref document: EP Ref document number: 1020027000077 Country of ref document: KR |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWG | Wipo information: grant in national office |
Ref document number: 2000946731 Country of ref document: EP |