EP1252787B1 - Procede pour faire fonctionner un reseau de telephonie mobile - Google Patents

Procede pour faire fonctionner un reseau de telephonie mobile Download PDF

Info

Publication number
EP1252787B1
EP1252787B1 EP00991121A EP00991121A EP1252787B1 EP 1252787 B1 EP1252787 B1 EP 1252787B1 EP 00991121 A EP00991121 A EP 00991121A EP 00991121 A EP00991121 A EP 00991121A EP 1252787 B1 EP1252787 B1 EP 1252787B1
Authority
EP
European Patent Office
Prior art keywords
packet data
unit
mobile station
network unit
pdcp
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Lifetime
Application number
EP00991121A
Other languages
German (de)
English (en)
Other versions
EP1252787A1 (fr
Inventor
Martin Hans
Mark Beckmann
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Robert Bosch GmbH
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=7627697&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP1252787(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP1252787A1 publication Critical patent/EP1252787A1/fr
Application granted granted Critical
Publication of EP1252787B1 publication Critical patent/EP1252787B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller

Definitions

  • the invention relates to a method for operating a Mobile network according to the preamble of the main claim.
  • ETSI Universal Mobile Telecommunications System
  • UMTS Universal Mobile Telecommunications System
  • MAC protocol specification 3G TS 25.323 version 3.0.0 release 1999
  • ETSI is well known at a connection change from a connection between a terminal and a first SRNC connection-specific data such as the number of the next expected Exchange data packets between the first SRNC and the second SRNC.
  • the second SNRC sends to the terminal the number of the next from the terminal expected data packet.
  • the inventive method with the features of Main claim has the advantage that before the Link change the transmission of the packet data units from the first base station to the mobile station from the first one parent network unit is stopped that with the transfer-specific information from the first parent network unit a first identifier of next from the mobile station in the first one parent network unit expected packet data unit is transmitted to the second parent network unit and that of the second parent network unit a first connection exchange packet data unit to the Mobile station is transmitted, which is the first identifier includes.
  • a first identifier of next from the mobile station in the first one parent network unit expected packet data unit is transmitted to the second parent network unit and that of the second parent network unit a first connection exchange packet data unit to the Mobile station is transmitted, which is the first identifier includes.
  • first Link exchange packet data unit ensures that the Mobile station after the connection change the transmission with that of the second parent network entity expected packet data unit continues, so that no during the connection change from the mobile station to the first or the second parent network unit sent Packet data units, for example due to a faulty reception or faulty evaluation get lost. Rather, a gapless and through the if necessary, change the connection Reconfiguration or reset operations not impaired reception of the mobile station sent packet data units in the second superior network unit guaranteed.
  • Another advantage is that the first Identifier by using a as Link exchange packet data unit trained Packet data unit is sent so that it efficiently over the existing data channels without additional signaling and without the construction and dismantling of new data channels or the Reconfiguration of existing data channels to the mobile station can be transferred.
  • the mobile station Sending packet data units after receiving the first Identifier is stopped. In this way, the Mobile station informed about the connection change and prevented from receiving more packet data units send by the second parent Network unit may not have expected become.
  • Another advantage is that the second Link exchange packet data unit from the mobile station after reconfiguring or resetting the mobile station the second higher-level network entity is transmitted.
  • Another advantage is that of the second parent network unit packet data units ignored be after the connection change and before the reception the second connection exchange packet data unit of the Mobile station to be received. This way will prevents packet data units that the mobile station had sent before the connection change, but the only after the change of connection in the second parent network unit were received to one erroneous detection in the second parent Network unit lead because, for example, a Reconfigure or reset the second parent network unit through the connection switch was caused.
  • a by the at Change of connection possibly to be carried out Reconfiguration or reset operations not impaired reception of the mobile station sent packet data units in the second superior network unit guaranteed.
  • Another advantage results from the fact that the shipping of packet data units from the mobile station Reconfigure or reset the mobile station with the packet data unit referenced by the first indicator is continued, these and the following Packet data units to the second parent Network unit to be transmitted. This way will ensured that the mobile station continued the continuation of Data transfer after the connection change with the new one Connection to the second higher-level network unit performs matched packet data units, so that this Packet data units in the second parent Network unit can also be detected.
  • Another advantage results from the fact that the second higher-level network unit before receiving the transmission-specific information is initialized. In this way it is prevented that the transfer-specific information from the second parent network unit due to lack of Initialization can not be understood.
  • first identifier in the first connection exchange packet data unit and / or the second identifier in the second Connection change packet data unit as sequence number transmitted as the next expected packet data unit becomes. In this way, only marginally bandwidth for the transfer of the individual Claim changeover packet data units, especially if the sequence number is only 8 bits claimed.
  • FIG. 1 shows a block diagram of a Mobile network
  • Figure 2 is a block diagram for a connection between a mobile station and a first parent Network unit via a first base station in front of a Connection change
  • Figure 3 is a block diagram of a Connection between the mobile station and a second parent network unit via a second base station after a connection change
  • Figure 4 is an example of a Timing of the connection change according to the prior art
  • FIG. 5 shows an example of a timing of the Connection change according to the invention.
  • the invention deals with a method for operating a Mobile network 1 according to Figure 1, wherein during a Established connection a connection change between two Base stations 25, 30 takes place, which is also called “relocation” referred to as.
  • the mobile network 1 can for example according to the GSM standard (Global System for Mobile Communications) or according to the UMTS standard (Universal Mobile Telecommunications System) be constructed.
  • the method refers here specifically for the transmission of transmission-specific Information of the established connection, for example in shape of internal log information of a Convergence protocol layer 130, 135, between two parent network units 50, 55 of the cellular trained mobile network 1.
  • the cellular mobile network 1 consists of various Units 10, 20, 25, 30, 35, 50, 55, 60, physically connected to each other. 10 marks one Mobile station of the mobile network 1, for example as mobile telecommunication terminal may be formed.
  • the Mobile telecommunication terminal 10 is via a first Air interface 90 with a first base station 25 of the Mobile network 1 connected.
  • the first base station 25 is over a first landline connection 81 with a first parent Network unit 50 connected.
  • a second base station 30 is via a second landline connection 82 with a second parent network unit 55 connected.
  • a third Base station 20 is via a third landline 80 with the first higher-level network unit 50 connected.
  • a fourth base station 35 is via a fourth fixed network connection 83 connected to the second parent network unit 55.
  • the first parent network unit 50 is over a fifth Landline connection 85 with a highest network unit 60 connected.
  • the second higher-level network unit 55 is over a sixth fixed network connection 86 with the highest Network unit 60 connected.
  • the first higher-level network unit 50 via a seventh Landline connection with the second parent Network unit 55 may be connected, as dashed lines in Figure 1 is shown.
  • the first parent network unit 50, the second higher-level network unit 55 and optionally Other higher-level network units form according to the UMTS standard so-called "Radio Network Subsystems" (RNS).
  • RNS Radio Network Subsystems
  • the highest network unit forms according to the UMTS standard one so-called "GPRS Support Node” (General Packet Radio System Support Node) (GSN).
  • cellular mobile network 1 In the cellular mobile network 1 are for data transmission between the mobile telecommunication terminal 10 and the remaining units involved in the established connection of the Mobile network 1 logical connections made. There are different types of logical connections between the mobile telecommunication terminal 10 and the various participating units of the mobile network 1 simultaneously. These logical connections come from one hierarchical model in which each hierarchical layer one Protocol corresponds to that in both the mobile Telecommunication terminal 10 and in the entspechenden Unit of the mobile network 1 is present and that the corresponding logical connection realized.
  • FIG. 2 are exemplary the logical connections between the mobile station 10 and the first parent Network unit 50 and between the mobile station 10 and the first base station 25 shown.
  • the lowest hierarchical Layer in this hierarchical model is through a first physical layer 110 in the mobile telecommunication terminal 10 and a second physical layer 115 in the first Base station 25 formed, which is one of the first air interface 90 corresponding physical connection between the mobile Telecommunication terminal 10 and the first base station 25 of Mobile network 1 realize.
  • one Backup layer which according to the UMTS standard as well "Data Link Layer” is called, and in several Sublayers is divided and different logical Connections between the mobile telecommunication terminal 10 and according to the UMTS standard as "Radio Network Controler" (RNC) designated first parent network entity 50 realized.
  • RNC Radio Network Controler
  • Such a sublayer is according to the UMTS standard the radio connection control layer, also called “Radio Link Control” layer (RLC) is called and in the first RLC protocol 120 in the mobile telecommunication terminal 10 and a second RLC protocol 125 in the first parent Network unit 50 a first logical RLC connection 101 as realize one of the mentioned logical connections.
  • RLC Radio Link Control
  • a other sublayer is the packet data convergence protocol layer, which according to the UMTS standard also as "Packet Data Convergence Protocol” layer (PDCP) is called and in the first PDCP protocol 130 in the mobile Telecommunication terminal 10 and a second PDCP protocol 135 in the first parent network unit 55 a first realize logical PDCP connection 102.
  • PDCP Packet Data Convergence Protocol
  • FIG. 2 are adjacent layers in the hierarchical model interconnected, with parent layers providing the services the corresponding adjacent subordinate layers in Claim.
  • the second physical layer 115 is as in FIG Figure 1 indicated on the first fixed network connection with the first parent network unit 50 and there with the second RLC protocol 125 connected.
  • UMTS Radio Interface Protocol Architecture is the corresponding one UMTS protocol architecture of so-called layers 2 and 3 including the packet data convergence protocol layer belongs.
  • the packet data convergence protocol layer is and their location within this Architecture known.
  • the PDCP protocol 130, 135 is from the Publication "Technical Specification 25.323, Packet Data Convergence Protocol ", as far as it is specified, known.
  • One task of the PDCP protocol 130, 135 is compression of packet data control information provided by the logs the one above the packet data convergence protocol layer Transport and network layer also in the Packet data protocol layer before it is transmitted Data units or packet data units assembled Payload also one above the packet data convergence protocol layer added to expiring application were and before the transfer over the first Air interface 90 need to be compressed to one to enable efficient transmission.
  • the cellular mobile network offers the possibility of Data transmission from the mobile telecommunication terminal 10 to a unit of the mobile network 1, even if the user of the mobile telecommunication terminal 10 that of the first Base station 25 spanned radio cell leaves. This will be between the mobile telecommunication terminal 10 and the Mobile network 1, a method for transferring the built Connection for data transmission from the first base station 25 to the second base station 30, provided that User of the mobile telecommunication terminal 10 moves in the radio cell spanned by the second base station 30. This connection change is as described as well "handover" between the base stations.
  • connection change it may now be that the second Base station 30 to which the connection is to be transferred, connected to another parent network entity as the previous first base station 25.
  • the second Base station 30 in contrast to the first base station 25 with the second higher-level network unit 55 is connected. It therefore takes place simultaneously with or after the handover from a first base station to a second one also the Handover between the first parent Network unit 50 and the second parent Network Unit 55. This handover becomes "relocation" between the network entities.
  • the RLC protocol and the PDCP protocol in both the mobile telecommunication terminal 10 and in the first parent network entity 50 exist.
  • the PDCP protocols 130, 135 are according to the UMTS standard as described on the one hand in the mobile Telecommunication terminal 10 and the other in the first higher-level network unit 50 and in more higher-level network units, which are designed as RNC.
  • the connection change is the existing data connection between the mobile Telecommunication terminal 10 and the mobile network 1 so routed over the second base station 30 and the second Parent network unit 55 runs.
  • the invention now proceeds from the concrete and exemplary Scenario that the mobile telecommunication terminal 10 with Units of the mobile radio network 1, like the first base station 25, the first parent network unit 50 and the highest one Network unit 60 about the necessary physical and logical Connections, in particular those of the first PDCP protocol 130 and realized by the second PDCP protocol 135 first logical PDCP connection 102 between the mobile Telecommunication terminal 10 and the first parent Network unit 50, is connected and a data transfer, ie an exchange of packet data units over these connections takes place.
  • the first PDCP protocol defines 130 and the second PDCP protocol 135 because of their functionality transfer-specific information for compression and manipulating the payload data and the packet data control information needed. For a correct function the above two PDCP protocols 130, 135, must be part of this transmission-specific information in the two PDCP protocols 130, 135 synchronized or even be equal.
  • the new physical connection corresponds to a second Air interface 91 according to Figure 1 and Figure 3.
  • Figure 3 is the connection of the mobile telecommunication terminal 10 with the second parent network unit 55 via the second Base station 30 shown, wherein like reference numerals are the same Identify elements as in Figure 2.
  • This is the second Base station 30 according to Figure 3 via the second fixed network connection 82 with the second higher-level network unit 55 or their RLC protocol connected here as third RLC protocol 126.
  • the second parent network unit 55 is like the first parent Network unit 50 constructed and points in a corresponding manner in addition to the third RLC protocol 126, the third PDCP protocol 136 on.
  • the second base station 30 is in the mobile network 1 as described with the first parent Network unit 50 different second parent Network unit 55 connected.
  • the logical ones become Connections between the mobile telecommunication terminal 10 and the second parent network unit 55 rebuilt. It is between the first RLC protocol 120 and the third RLC protocol 126, a second logical RLC connection 103 built up. Between the first PDCP protocol 130 and the third PDCP protocol 136 becomes a second logical PDCP connection 104 built. Thus, the first logical PDCP connection 103 through the second logical PDCP connection 104 replaced. This must be in the second parent network unit 55, the third PDCP protocol 136 after the connection change to be recreated once.
  • the parent Network device that is connected to the mobile network changed, then in the original, first parent network unit 50 which is responsible for generating the second RLC protocol unit 125 provided second RLC protocol unit 2200 and that for the generation of the second PDCP protocol 135 provided second PDCP protocol unit 2100 deleted and in the new, second parent Network unit 55 becomes a third RLC protocol unit 3200 and a third PDCP protocol unit 3100 and so on configured to subsequently transfer data between the third RLC protocol unit 3200 and that for generation of the first RLC protocol 120 provided first RLC protocol unit 1200 or between the third PDCP protocol unit 3100 and that for the generation of the first PDCP protocol 130 provided first PDCP protocol unit 1100, that is between the third RLC protocol 126 and the first RLC protocol 120 and between the third PDCP protocol 136 and the first PDCP protocol 130 according to Figures 4 and 5 possible is.
  • the appropriate PDCP protocol unit 1100, 2100, 3100 of each transmitter each from a higher protocol layer for data transmission received packet data unit by means of a so-called PDCP transmission sequence number numbered and saved.
  • the Packet data unit if necessary. Compressed and to the RLC protocol layer for transfer.
  • the corresponding PDCP protocol unit 1100, 2100, 3100 of the Each receiver is each of the local RLC protocol layer received packet data unit also below Counting a PDCP receive sequence number counted. Because the RLC protocol layer a lossless transfer of Guaranteed packet data units in the right order, The PDCP send sequence number and the PDCP receive sequence number are the same each transmitted data packet.
  • the mobile station 10 and the respective parent Network unit 50, 55 each as both transmitter and as As a rule, they can usually include PDCP protocol units 1100, 2100, 3100 both to send and for receiving packet data units.
  • PDCP transmission sequence numbers and PDCP receive sequence numbers both in the Uplink, i. in the transmission path from the mobile station 10 to the corresponding higher-level network unit 50, 55 as also in the downlink, i. in the transmission line of the corresponding parent network unit 50, 55 to Mobile station 10.
  • the mobile station 10 thus counts the sent Packet data units with the so-called PDCP uplink transmission sequence number and the received packet data units with the PDCP downlink receive sequence number.
  • the corresponding higher-level network unit 50, 55 then counts the sent Packet data units with the so-called PDCP downlink transmission sequence number and the received packet data units with the PDCP uplink receive sequence number.
  • the second parent network unit 55 sends the PDCP uplink receive sequence number the next and the expected second higher-level network unit 55 to be received Data packets to the mobile station 10.
  • the mobile station 10 turn sends the PDCP downlink receive sequence number to the next of the mobile station 10 expected and to be received Packet data unit to the second higher-level network unit 55.
  • the individuals responsible for sending know each other PDCP protocol units 1100, 2100, 3100 in the mobile station 10 and in the corresponding higher-level network entity 50, 55, which packet data units before the connection change from the respective receiving PDCP protocol unit 1100, 2100, 3100 in the mobile station 10 and in the corresponding one parent network unit 50, 55 were received correctly and from which packet data unit to the payload transfer the connection change must be resumed.
  • Conceivable here is the transmission of these transmission-specific Information other than the PDCP protocol 130, 135, 136, for example by the radio resource control protocol RRC, the also the message about the occurrence of a Link change receives and processes, or by the PDCP protocol 130, 135, 136 itself. Also for transmission The transmission channels used by the packet data units are not established.
  • Packet Data Convergence (PDCP) protocol 3GPP, Technical Specification 25.323
  • PDCP PDUs Packet data units
  • These packet data units thus received may then possibly from the second parent PDCP protocol unit 3100 Network unit 55 is not properly handled, e.g. decompressed since, during or after the first connection change 500 the type of data manipulation in the PDCP protocol unit 3100 of the second superordinate network unit 55 with respect to PDCP protocol unit 2100 of the first parent Network unit 50 may have changed by a first Reset 540 of the PDCP protocol unit 3100 of the second parent network unit 55 immediately after the first Link change 500, with the first reset 540 eg in resetting the compression algorithms at the Initialization of the PDCP protocol unit 3100 of the second parent network unit 55 may exist.
  • Packet data units may then be available from the PDCP protocol unit 1100 of the mobile station 10 is not correct treated, e.g. decompressed, since after the second Link change 600 the type of data manipulation in the PDCP protocol unit 1100 of the mobile station 10 have changed may be triggered by a second reset 640 of the PDCP protocol unit 1100 of the mobile station 10 directly after the second connection change 600, wherein the second reset operation 640, for example, in resetting the compression algorithms in the PDCP protocol unit 1100 of the mobile station 10 may exist.
  • PDCP-PDU PDCP packet data unit
  • PDCP-SNPDU PDCP sequence number packet data unit
  • the PDCP-SNPDU proposed here also contains the information element known from the prior art and used in the packet data units used for the data transmission of the payload data " PDU type ", which contains in the PDCP-SNPDU a value specific to the PDCP-SNPDU, comprising 3 bits, for example 001. Furthermore, the PDCP-SNPDU contains an information element R, which comprises 5 bits, and with which the length of the PDCP-SNPDU is extended to a value divisible by 8. This information element can assume any values, it can be used in particular for further, irrelevant for this invention, signaling.
  • the table shows the proposed PDCP SNPDU format by way of example with an 8-bit PDCP sequence number, a 3-bit PDU type information element and a 5-bit information element R: PDCP SNPDU bit 8th 7 6 5 4 3 2 1 Oct 1 PDU type R Oct 2 PDCP sequence number
  • the PDCP-SNPDU according to the table comprises two octets, the each consist of 8 bits.
  • the method according to the invention now includes that in FIG. 5 following steps are shown:
  • connection change always from the network, especially from of the highest network unit 60 is started always the network with the first step.
  • the normal one Data exchange of packet data units between the mobile station 10 and the first parent network unit 50 is present a third connection change 700 in Figure 5 by the Reference numeral 701 marked.
  • the PDCP protocol unit 2100 in the first parent Network unit 50 stops the data transfer over the past used transmission channels to the mobile station 10.
  • the PDCP protocol unit 2100 in the first parent Network Unit 50 transmits the information in the publication "Packet Data Convergence (PDCP) Protocol " transmission-specific information 730 to the PDCP protocol unit 3100 of the second parent network unit 55.
  • These include the PDCP uplink receive sequence number as next in the first parent network unit 50 expected packet data unit and the memory contents with the PDCP downlink transmission sequence numbers to be sent to Mobile station 10 stored packet data units.
  • the PDCP protocol unit 3100 of the second parent Network unit 55 sends the PDCP uplink receive sequence number the next expected packet data unit via the RLC protocol unit 3200 of the second parent network unit 55 according to the transmitting step 740 and the RLC protocol unit 1200 of the mobile station 10 according to the Transmission step 741 to the PDCP protocol unit 1100 of Mobile station 10 according to the transmission step 742, by For example, a PDCP SNPDU is generated according to the table that there information element corresponding to the to be sent PDCP uplink receive sequence number sets and the PDCP SNPDU to the same RLC protocol unit 3200 of the second parent Network unit 55 and thus to the same logical channel, namely the second logical RLC connection 103 for error-free Transmission in the correct order in the transfer step 741 via the second air interface 91 passes, the second logical RLC connection 103 also for the data transmission used the remaining, payload data containing packet data units becomes.
  • the PDCP protocol unit 3100 in the second parent Network unit 55 initially ignores all of the mobile station 10 received packet data units that are not PDCP SNPDUs.
  • the PDCP protocol unit 1100 of the mobile station 10 stops, after passing the PDCP SNPDU from the second parent Network unit 55 after the transmission step 742 received has, first the user data transfer to the second parent Network Unit 55.
  • the PDCP protocol unit 1100 of the mobile station 10 now assumes for the case that at their institution a connection change Negotiated changes 720 in question, e.g. one Reset the internal protocol information, agreed these changes were 720 ago.
  • the PDCP protocol unit 1100 sends the Mobile station 10, the PDCP downlink receive sequence number of next expected packet data unit to the PDCP protocol unit 3100 of the second parent network unit 55, by generating a PDCP-SNPDU according to the table, the Information element corresponding to the PDCP downlink receive sequence number sets, and the PDCP SNPDU according to the Transfer step 745 to the same RLC protocol unit 1200 the mobile station 10 and thus to the same second logical RLC connection 103 for error-free transmission in the correct one Passing order over the second air interface 91, the also for the data transmission of the user data transporting Packet data units is used.
  • the RLC protocol unit 1200 the mobile station 10 thus transmits the PDCP-SNPDU the RLC protocol unit 3200 of the second parent Network unit 55 according to the transmission step 746.
  • the RLC protocol unit 3200 of the second parent network unit 55 then transmits the PDCP-SNPDU to the PDCP protocol unit 3100 of the second superordinate network unit 55 according to the Transmission step 747.
  • the PDCP protocol unit 1100 of the mobile station 10 takes in addition, the user data transfer to the second parent Network unit 55 back on, with this Nutzsteintransfer started with the packet data unit and then accordingly continued by the received PDCP uplink receive sequence number was referenced and by a corresponding from the PDCP protocol unit 1100 of Mobile station 10 assigned PDCP uplink transmission sequence number can be identified.
  • the transmission shown as an example the first packet data unit after the 720 changes in the PDCP protocol unit 1100 of mobile station 10 takes place according to the transmission step 750, first from the PDCP protocol unit 1100 of the mobile station 10 to the RLC protocol unit 1200 of the mobile station 10 and from there according to the Transfer step 755 to the RLC protocol unit 3200 of FIG second higher-level network unit 55 and from there according to the Transmission step 758 to PDCP protocol unit 3100 of FIG second superordinate network unit 55.
  • the PDCP protocol unit 3100 of the second parent Network unit 55 picks up the PDCP SNPDU from the Mobile station 10 has received after transmission step 747, the Nutzsteintransfer on again, with this Nutz stylisttransfer started with the packet data unit and then accordingly continued by the received PDCP downlink receive sequence number was referenced and by a corresponding in the PDCP protocol unit 3100 of the second Parent network unit 55 assigned PDCP downlink transmission sequence number can be identified.
  • the PDCP protocol unit 3100 of the second parent Network unit 55 then sends the first packet data unit this payload transfer via the RLC protocol unit 3200 of second higher-level network unit 55 according to the Transmission step 760 and the RLC protocol unit 1200 of Mobile station 10 according to the transfer step 765 to the PDCP protocol unit 1100 of the mobile station 10 according to the Transfer step 768 by sending the packet data unit to the same RLC protocol unit 3200 of the second parent Network unit 55 and thus to the same logical channel, namely the second logical RLC connection 103 for error-free Transmission in the correct order in the transfer step 741 via the second air interface 91 passes.
  • the others Packet data units of the payload transfer are in corresponding manner between the mobile station 10 and the second higher-level network unit 55 transferred.
  • steps 1-5 are shown by way of example.
  • a first message 705 from an RRC protocol unit 2000 of FIG first higher-level network entity 50 to the PDCP protocol entity 2100 of the first parent network unit 50 is an example of the initiation of the third Change of connection 700 and thus the occasion of the Transmission of the transmission-specific information 730 to PDCP protocol unit 3100 of the second parent Network unit 55.
  • a second message 708 from an RRC protocol unit 3000 of the second parent network unit 55 to the PDCP protocol unit 3100 of the second parent Network unit 55 is also an example of initiation the third change of connection 700 and thus the cause an initialization 710 of the PDCP protocol unit 3100 of second parent network unit 55, after which then the transmission-specific information 730 are received can.
  • the proposed data format for this purpose from the corresponding PDCP protocol unit 1100, 3100 generated PDCP-SNPDU is very bandwidth-efficient, since only a few unused Information must be transferred, namely 5 bits, and no more than the required information, namely 8 bits for the corresponding sequence number and 3 bits for the corresponding PDU types are present in the PDCP-SNPDU.

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é pour faire fonctionner un réseau de téléphonie mobile (1), qui permet l'échange sans erreur d'unités de données en paquets lors d'un changement de liaison (700) entre une station mobile (10) et des unités de réseau (50, 55) hiérarchiquement supérieures. Pour la transmission des unités de données en paquets, tant dans la station mobile (10) que dans une première unité de réseau (50) hiérarchiquement supérieure à la première station de base (25) sont déposées des informations spécifiques à la transmission qui décrivent l'état du moment de la transmission. Lors du changement de liaison (700) de la station mobile (10), de la première station de base (25) à une seconde station de base (30), avec une seconde unité de réseau (55) hiérarchiquement supérieure, les informations spécifiques de la transmission déposées dans la première unité de réseau (50) hiérarchiquement supérieure sont transmises à la seconde unité de réseau (55) hiérarchiquement supérieure pour que la transmission, après le changement de liaison, continue sensiblement directement à partir de son état du moment.

Claims (12)

  1. Procédé de gestion d'un réseau de téléphonie mobile selon lequel on transmet entre une station mobile (10) et une première station de base (25), des données utiles composées en unités de paquets de données avant leur transmission, selon lequel
    des informations spécifiques à la transmission, qui décrivent l'état actuel de la transmission, sont enregistrées à la fois dans la station mobile (10) et aussi dans une première unité de réseau (50) subordonnée à la première station de base (25) pour la transmission des unités de paquets de données, et
    lors d'un changement de liaison de la station mobile (10) passant de la première station de base (25) à une seconde station de base (30) ayant une seconde unité de réseau (55) subordonnée, les informations spécifiques à la transmission contenues dans la première unité de réseau subordonnée (50) sont transmises à la seconde unité de réseau subordonnée (55) pour poursuivre la transmission après le changement de liaison, essentiellement directement à partir de son état actuel,
    caractérisé en ce qu'
    avant le changement de liaison, la première unité de réseau (50) subordonnée retient la transmission des unités de paquets de données de la première station de base (25) vers la station mobile (10),
    la première unité de réseau subordonnée (50) transmet avec les informations spécifiques à la transmission, un premier identificateur de l'unité de paquets de données attendu comme paquet suivant est transmis par la station mobile (10) de la première unité de réseau subordonnée (50) à la seconde unité de réseau subordonnée (55), et
    la seconde unité de réseau subordonnée (55) transmet une première unité de paquets de données de changement de liaison à la station mobile (10), cette unité contenant le premier identificateur.
  2. Procédé selon la revendication 1,
    caractérisé en ce que
    la station mobile (10) retient l'envoi des unités de paquets de données après la réception du premier identificateur.
  3. Procédé selon la revendication 1 ou 2,
    caractérisé en ce qu'
    après la réception du premier identificateur la station mobile (10) transmet une seconde unité de paquets de données de changement de liaison à la seconde unité de réseau (55) subordonnée, qui contient un second identificateur correspondant à l'unité de paquets de données suivant, et attendu par la seconde unité de réseau subordonnée (55) à la station mobile (10).
  4. Procédé selon la revendication 3,
    caractérisé en ce que
    la seconde unité de paquets de données de changement de liaison est transmise par la station mobile (10) après reconfiguration ou remise à l'état de la station mobile (10) à la seconde unité de réseau subordonnée (55).
  5. Procédé selon la revendication 3 ou 4,
    caractérisé en ce que
    l'envoi d'unités de paquets de données par la seconde unité de réseau subordonnée (55) à la station mobile (10) après réception du second indicateur se poursuit par l'unité de paquets de données référencée par le second indicateur.
  6. Procédé selon les revendications 3, 4 ou 5,
    caractérisé en ce que
    la seconde unité de réseau subordonnée (55) ignore les unités de paquets de données reçus après le changement de liaison et avant la réception de la seconde unité de paquets de données de changement de liaison par la station mobile (10).
  7. Procédé selon l'une des revendications 2 à 6,
    caractérisé en ce qu'
    après la réception du premier indicateur, l'émission des unités de paquets de données par la station mobile (10) se poursuit par l'unité de paquets de données référencée par le premier indicateur,
    cette unité et les unités de paquets de données suivantes étant transmises à la seconde unité de réseau subordonnée (55).
  8. Procédé selon l'une des revendications 7,
    caractérisé en ce qu'
    après reconfiguration ou remise à l'état de la station mobile (10) on poursuit l'envoi des unités de paquets de données par la station mobile (10), avec l'unité de paquets de données référencée par le premier indicateur,
    cette unité et les unités de paquets de données suivantes étant transmises à la seconde unité de réseau subordonnée (55).
  9. Procédé selon l'une des revendications précédentes,
    caractérisé en ce que
    la seconde unité de réseau subordonnée (55) est initialisée avant la réception des informations spécifiques à la transmission.
  10. Procédé selon l'une des revendications précédentes,
    caractérisé en ce que
    le premier identificateur est transmis dans la première unité de paquets de données de changement de liaison et/ou le second identificateur est transmis dans la seconde unité de paquets de données de changement de liaison, chaque fois comme numéro de succession de l'unité de paquets de données suivante attendue.
  11. Procédé selon la revendication 10,
    caractérisé en ce que
    le numéro de suite est transmis dans un format prédéterminé notamment sous la forme d'une valeur à 8 bits.
  12. Procédé selon la revendication 10 ou 11,
    caractérisé en ce que
    le numéro de suite est transmis dans une unité de paquets de données de changement de liaison avec un élément d'information caractérisant en tant que telle l'unité de paquets de données de changement de liaison.
EP00991121A 2000-01-17 2000-12-23 Procede pour faire fonctionner un reseau de telephonie mobile Expired - Lifetime EP1252787B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10001608A DE10001608A1 (de) 2000-01-17 2000-01-17 Verfahren zum Betreiben eines Mobilfunknetzes
DE10001608 2000-01-17
PCT/DE2000/004652 WO2001058196A1 (fr) 2000-01-17 2000-12-23 Procede pour faire fonctionner un reseau de telephonie mobile

Publications (2)

Publication Number Publication Date
EP1252787A1 EP1252787A1 (fr) 2002-10-30
EP1252787B1 true EP1252787B1 (fr) 2005-05-11

Family

ID=7627697

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00991121A Expired - Lifetime EP1252787B1 (fr) 2000-01-17 2000-12-23 Procede pour faire fonctionner un reseau de telephonie mobile

Country Status (5)

Country Link
US (1) US7283511B2 (fr)
EP (1) EP1252787B1 (fr)
JP (1) JP3909241B2 (fr)
DE (2) DE10001608A1 (fr)
WO (1) WO2001058196A1 (fr)

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6360100B1 (en) 1998-09-22 2002-03-19 Qualcomm Incorporated Method for robust handoff in wireless communication system
KR100595583B1 (ko) * 2001-07-09 2006-07-03 엘지전자 주식회사 이동통신시스템에서 핸드오버에 따른 패킷 데이터 전송 방법
RU2273104C2 (ru) * 2001-10-05 2006-03-27 Нокиа Корпорейшн Переключение адресов и корреляция сообщений между сетевыми узлами
AU2002343696A1 (en) * 2002-01-08 2003-07-30 Motorola, Inc. Packet data serving node initiated updates for a mobile communication system
US7668541B2 (en) 2003-01-31 2010-02-23 Qualcomm Incorporated Enhanced techniques for using core based nodes for state transfer
US6862446B2 (en) * 2003-01-31 2005-03-01 Flarion Technologies, Inc. Methods and apparatus for the utilization of core based nodes for state transfer
US7656835B2 (en) * 2005-05-18 2010-02-02 Nokia Corporation Method for informing changed communications capabilities
US8982835B2 (en) 2005-09-19 2015-03-17 Qualcomm Incorporated Provision of a move indication to a resource requester
US8983468B2 (en) 2005-12-22 2015-03-17 Qualcomm Incorporated Communications methods and apparatus using physical attachment point identifiers
US8509799B2 (en) 2005-09-19 2013-08-13 Qualcomm Incorporated Provision of QoS treatment based upon multiple requests
US9066344B2 (en) 2005-09-19 2015-06-23 Qualcomm Incorporated State synchronization of access routers
US9078084B2 (en) 2005-12-22 2015-07-07 Qualcomm Incorporated Method and apparatus for end node assisted neighbor discovery
US8982778B2 (en) 2005-09-19 2015-03-17 Qualcomm Incorporated Packet routing in a wireless communications environment
US9736752B2 (en) 2005-12-22 2017-08-15 Qualcomm Incorporated Communications methods and apparatus using physical attachment point identifiers which support dual communications links
KR100866225B1 (ko) * 2005-10-05 2008-10-30 삼성전자주식회사 고속 순방향 패킷 접속 시스템을 위한 셀 선택 방법 및 장치
US9083355B2 (en) 2006-02-24 2015-07-14 Qualcomm Incorporated Method and apparatus for end node assisted neighbor discovery
KR101265643B1 (ko) * 2006-08-22 2013-05-22 엘지전자 주식회사 무선 통신 시스템에서의 핸드오버 수행 및 그 제어 방법
GB0616682D0 (en) 2006-08-22 2006-10-04 Nec Corp Mobile telecommunications
WO2008041823A2 (fr) * 2006-10-02 2008-04-10 Lg Electronics Inc. Méthode de transmission et réception d'un message de radiomessagerie dans un système de communication sans fil
EP2084928B1 (fr) * 2006-10-30 2017-08-23 LG Electronics Inc. Procédé permettant d'effectuer un accès direct dans un système de communication sans fil
WO2008054119A2 (fr) * 2006-10-30 2008-05-08 Lg Electronics Inc. Procédé de transmission d'un message par canal d'accès aléatoire
KR100938754B1 (ko) 2006-10-30 2010-01-26 엘지전자 주식회사 비연속 수신을 이용한 데이터 수신 및 전송 방법
US9155008B2 (en) 2007-03-26 2015-10-06 Qualcomm Incorporated Apparatus and method of performing a handoff in a communication network
US8543089B2 (en) * 2007-04-30 2013-09-24 Lg Electronics Inc. Method for performing an authentication of entities during establishment of wireless call connection
KR101455999B1 (ko) 2007-04-30 2014-11-03 엘지전자 주식회사 무선 통신 시스템에서의 데이터 블록 생성 방법
KR20080097338A (ko) * 2007-05-01 2008-11-05 엘지전자 주식회사 불연속 데이터 송수신 방법
KR100917205B1 (ko) * 2007-05-02 2009-09-15 엘지전자 주식회사 무선 통신 시스템에서의 데이터 블록 구성 방법
US8830818B2 (en) 2007-06-07 2014-09-09 Qualcomm Incorporated Forward handover under radio link failure
CN101589566B (zh) * 2007-06-18 2013-06-12 Lg电子株式会社 在无线通信系统中执行上行链路同步的方法
ES2652668T3 (es) 2007-06-18 2018-02-05 Lg Electronics Inc. Procedimiento y equipamiento de usuario para realizar una sincronización de enlace ascendente en un sistema de comunicación inalámbrica
US9094173B2 (en) 2007-06-25 2015-07-28 Qualcomm Incorporated Recovery from handoff error due to false detection of handoff completion signal at access terminal
KR101387537B1 (ko) * 2007-09-20 2014-04-21 엘지전자 주식회사 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법
US8422466B2 (en) * 2007-11-26 2013-04-16 Nokia Corporation Multiple network connections
TW200931918A (en) * 2007-12-07 2009-07-16 Interdigital Patent Holdings Method and apparatus for supporting configuration and control of the RLC and PDCP sub-layers
US8615241B2 (en) 2010-04-09 2013-12-24 Qualcomm Incorporated Methods and apparatus for facilitating robust forward handover in long term evolution (LTE) communication systems

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI105993B (fi) 1997-08-20 2000-10-31 Nokia Mobile Phones Ltd Menetelmä ja järjestelmä radiotiedonsiirtoverkon hallitsemiseksi ja radioverkko-ohjain
US6230013B1 (en) * 1997-11-26 2001-05-08 Telefonaktiebolaget Lm Ericsson (Publ) Diversity handling moveover for CDMA mobile telecommunications
FI108772B (fi) * 1998-03-31 2002-03-15 Nokia Corp Matkaviestimen yhteyksien hallintamenetelmä
JP3442654B2 (ja) 1998-04-28 2003-09-02 三菱電機株式会社 移動体通信網制御装置
JP2999470B1 (ja) 1999-02-04 2000-01-17 株式会社ワイ・アール・ピー移動通信基盤技術研究所 フロ―制御方法、フロ―制御機能を有する交換網および端末装置
GB2356770A (en) * 1999-11-23 2001-05-30 Ericsson Telefon Ab L M SRNS relocation in a UMTS network
US6590905B1 (en) * 1999-12-22 2003-07-08 Nokia Mobile Phones Ltd. Changing XID/PDCP parameters during connection

Also Published As

Publication number Publication date
DE10001608A1 (de) 2001-07-19
US20030119488A1 (en) 2003-06-26
JP2003522493A (ja) 2003-07-22
US7283511B2 (en) 2007-10-16
WO2001058196A1 (fr) 2001-08-09
EP1252787A1 (fr) 2002-10-30
JP3909241B2 (ja) 2007-04-25
DE50010315D1 (de) 2005-06-16

Similar Documents

Publication Publication Date Title
EP1252787B1 (fr) Procede pour faire fonctionner un reseau de telephonie mobile
EP1273147B1 (fr) Procede d'utilisation d'un reseau de telephonie mobile
EP1226692B1 (fr) Procede pour faire fonctionner un reseau de telephonie mobile
DE602004006679T2 (de) Verfahren und Vorrichtung zur Konfiguration von Protokollen für einen Multimedia Broadcast/Multicast Dienst
DE60218431T2 (de) Transfer von ip-daten in einem kommunikationssystem unter verwendung mehrerer logischer verbindungen für komprimierte felder auf der grundlage verschiedener kontexte
DE69828572T2 (de) Verfahren und vorrichtung zur umlenkung einer verbindung in einer verbindung in einem fernmeldenetz mit einer vielzahl von netzelementen
EP1282997B1 (fr) Procede de transfert de tunnel entre des noeuds d'un systeme gprs
DE60102809T2 (de) Datenpaketnummerierung bei der paketvermittelten datenübertragung
DE602004010851T2 (de) Verfahren und einrichtungen zur duplikatpaketidentifikation während eines handover
DE19605223A1 (de) Verfahren zum Betreiben einer Breitband-Verbindung zwischen einem Mobilfunk-Endgerät und einer netzseitigen Mobilfunkeinrichtung sowie Mobilfunk-Endgerät, netzseitige Mobilfunkeinrichtung und Mobilfunksystem
DE19752697A1 (de) Drahtloses lokales Netzwerk mit Controller und wenigstens einem als Controller einsetzbaren Terminal
EP1238487B1 (fr) Procede d'exploitation d'un reseau de telephonie mobile
EP1457085B1 (fr) Procédé de transmission de données par paquets au cours du changement de cellule radio
EP1049294B1 (fr) Réseau avec plusieurs grappes de réseau pour radiocommunication de paquets
DE10017062B4 (de) Verfahren zum Betreiben eines Mobilfunknetzes
EP1085716B1 (fr) Transmission sans fil de données utilisant une couche protocolaire de compression
DE10352771A1 (de) Verfahren und Netzelement zur Verteilung und Lenkung von Datenpaketen während eines Wechsels einer mobilen Sende-/Empfangsstation von einer ersten Funkzelle in eine zweite Funkzelle innerhalb eines mobilen Kommunikationsnetzes
DE10031494A1 (de) Verfahren zum Multiplexen einer Vielzahl von Datenpaketen mehrerer Datenströme innerhalb des PDCP-Protokolls eines UMTS-Funkkommunikationsystems
DE10038182A1 (de) Verfahren zum Umlegen eines Tunnels zwischen Knoten eines GPRS-Systems
EP1876849A1 (fr) Commutation et reconfiguration simultanée des liaisons radios dans un système de télécommunications mobiles
DE102006018483A1 (de) Verfahren zum Software-Download von Endgeräten über die DECT-Luftschnittstelle

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020819

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

17Q First examination report despatched

Effective date: 20030227

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB IT

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REF Corresponds to:

Ref document number: 50010315

Country of ref document: DE

Date of ref document: 20050616

Kind code of ref document: P

GBT Gb: translation of ep patent filed (gb section 77(6)(a)/1977)

Effective date: 20050908

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

ET Fr: translation filed
26 Opposition filed

Opponent name: SAGEM COMMUNICATION S.A.

Effective date: 20060208

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: SHARP CORPORATION

PLAY Examination report in opposition despatched + time limit

Free format text: ORIGINAL CODE: EPIDOSNORE2

PLAH Information related to despatch of examination report in opposition + time limit modified

Free format text: ORIGINAL CODE: EPIDOSCORE2

PLBC Reply to examination report in opposition received

Free format text: ORIGINAL CODE: EPIDOSNORE3

PLAY Examination report in opposition despatched + time limit

Free format text: ORIGINAL CODE: EPIDOSNORE2

PLAY Examination report in opposition despatched + time limit

Free format text: ORIGINAL CODE: EPIDOSNORE2

PLAP Information related to despatch of examination report in opposition + time limit deleted

Free format text: ORIGINAL CODE: EPIDOSDORE2

PLCK Communication despatched that opposition was rejected

Free format text: ORIGINAL CODE: EPIDOSNREJ1

PLBN Opposition rejected

Free format text: ORIGINAL CODE: 0009273

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: OPPOSITION REJECTED

27O Opposition rejected

Effective date: 20100516

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20191210

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20191219

Year of fee payment: 20

Ref country code: IT

Payment date: 20191230

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20191220

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 50010315

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20201222

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20201222