[go: up one dir, main page]

WO2002001774A2 - Procede de multiplexage d'une pluralite de paquets de donnees de plusieurs trains de donnees dans le protocole pdcp d'un systeme de radiocommunication umts - Google Patents

Procede de multiplexage d'une pluralite de paquets de donnees de plusieurs trains de donnees dans le protocole pdcp d'un systeme de radiocommunication umts Download PDF

Info

Publication number
WO2002001774A2
WO2002001774A2 PCT/DE2001/002327 DE0102327W WO0201774A2 WO 2002001774 A2 WO2002001774 A2 WO 2002001774A2 DE 0102327 W DE0102327 W DE 0102327W WO 0201774 A2 WO0201774 A2 WO 0201774A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
unit
pdcp
protocol
radio
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.)
Ceased
Application number
PCT/DE2001/002327
Other languages
German (de)
English (en)
Other versions
WO2002001774A3 (fr
Inventor
Mark Beckmann
Martin Hans
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.)
Siemens AG
Siemens Corp
Original Assignee
Siemens AG
Siemens Corp
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
Application filed by Siemens AG, Siemens Corp filed Critical Siemens AG
Publication of WO2002001774A2 publication Critical patent/WO2002001774A2/fr
Publication of WO2002001774A3 publication Critical patent/WO2002001774A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/06Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/16Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1682Allocation of channels according to the instantaneous demands of the users, e.g. concentrated multiplexers, statistical multiplexers
    • H04J3/1688Allocation of channels according to the instantaneous demands of the users, e.g. concentrated multiplexers, statistical multiplexers the demands of the users being taken into account after redundancy removal, e.g. by predictive coding, by variable sampling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/24Time-division multiplex systems in which the allocation is indicated by an address the different channels being transmitted sequentially
    • H04J3/247ATM or packet multiplexing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22Parsing or analysis of headers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02Data link layer protocols

Definitions

  • the invention is concerned with the problem, in a radio communication system which can be formed in particular according to the UMTS standard, the exchange of data streams, between the subscriber equipment, in particular mobile ⁇ radios, and radio network units, in particular to improve radio control units.
  • This multiplexing of a large number of data packets of several data streams within the PDCP protocol of a UMTS radio communication system according to one of the two or at the same time according to both solution variants makes the data exchange between its subscriber devices and radio control units more efficient.
  • the invention further relates to a UMTS radio communication system in which the exchange of data streams between its subscriber devices, in particular mobile radio devices, and network units, in particular radio control units, is carried out according to at least one of the multiplex methods according to the invention.
  • Figure 1 is a schematic representation zes the configuration of a radio communication system ⁇ , preferably mobile networks, which is constructed in particular according to the UMTS standard, and operates in accordance with the PDCP protocol (Packet Data Convergence Protocol),
  • PDCP Packet Data Convergence Protocol
  • Figure 2 shows a schematic representation of the protocol layers between a subscriber device, in particular one
  • Radio station a base station and a radio control unit (radio network controller) of the radio communication system according to Figure 1, and
  • FIG. 3 shows a schematic representation of two multiplexing methods according to the invention for a multiplicity of data packets of a plurality of data streams, as are carried out individually or together in the respective subscriber device and the respective radio control unit.
  • data is generated in packets (e.g. web browsing) and transmitted in a packet-oriented manner.
  • packet data generated by one or more applications are manipulated in different, successively run protocols for transmission in packet-oriented networks.
  • TCP Transmission Control Protocol
  • IP Internet Pro tocol
  • the packet data is the TCP protocol control data (TCP header) vorange ⁇ provides, among other things, information on the source application from which the data originated, (Source Port), the target application for which the data are intended, (Destina - tion port) and data for troubleshooting and detection ent ⁇ hold.
  • TCP header is described in (RFC 793, Transmission Control Protocol (TCP), IETF September 1981, http://www.ietf.org/rfc.html (p.14)). It is at least 10 bits (5 octets) long and, together with the packet data, forms the TCP packet.
  • the TCP packet is then transferred to the IP protocol in the transmitter, which precedes the TCP packet IP control data (IP header), which includes information about the sender (source IP address) and receiver unit (destination IP address), the required transmission quality and the previously used protocol (in this example TCP).
  • IP header IP control data
  • the IP header is described in (RFC 791, Internet Protocol (IP), IETF September 1981, http://www.ietf.org/rfc.html (p.10)). It is at least 160 bit (5 octets) long and forms the IP packet together with the TCP packet.
  • the IP packet composed in this way consisting of packet data, TCP header and IP header, may become the one in the destination via several system units
  • the IP protocol then first removes the IP header from the IP packet and transfers the TCP packet thus obtained to the TCP protocol. This removes the TCP header and transfers the packet data thus received to the application identified by the destination port in the TCP header.
  • Packet data are generated in the sender, which are first transferred to the RTP protocol in the sender.
  • RTP then precedes the data with the RTP header and forms the RTP packet with the actual data.
  • This is then preceded by the UDP header of the UDP protocol and the UDP packet thus obtained is transmitted by the IP protocol as well as a TCP packet. All control data are then removed again in the receiver in order to receive the packet data and to transfer them to the application using the RTP protocol.
  • the IP protocol is a very common network layer protocol used in packet data networks, but other protocols can also be used (for example, X.25 (RFC, X.25, IETF).
  • the general term used in UMTS is the so-called Packet data protocol (PDP), the address used to route the packet data, in the example above the IP address, is called PDP address in particular.
  • PDP Packet data protocol
  • the data transmission system in which the packet data is to be transmitted consists wholly or partly of a mobile radio system, in particular UMTS radio communication system, it is advantageous to use the pairs generated as described above.
  • ket schemes eg. IP packets
  • IP packets of the various UMTS proto ⁇ kollen for efficient transmission by the mobile radio system ⁇ prepare.
  • the packet data of a PDP are first the PDCP protocol (3G TS 25.323, Packet Data Convergence Protocol (PDCP), 3GPP March 2000, http: //www.3gpp.org/ftp/Specs/March_00/25_series/25323-310.zip ) to hand over.
  • This protocol is prior to data transmission from the RRC protocol (3G TS 25.331, Radio Resource Control (RRC), 3GPP March 2000, http: //www.3gpp.org/ftp/Specs/March_00/25_series/25331-
  • Packet data is expediently such that it can be transmitted efficiently via the UMTS air interface of the respective subscriber device and / or the respective radio control unit of the UMTS radio communication system.
  • compression of the packet control data (header compression) for data reduction and numbering of the data packets for data loss and multiplication detection may be carried out.
  • header compression For this purpose, compression of the packet control data (header compression) for data reduction and numbering of the data packets for data loss and multiplication detection may be carried out.
  • header compression for data reduction and numbering of the data packets for data loss and multiplication detection may be carried out.
  • the packet control data header compression
  • the RLC protocol has in particular the task of dividing the PDCP packets, which can have a size between 0 and 1502 octets, into packets, the size of which is preferably adapted to the transmission via the air interface. This can result in a segmentation of the packages or a combination of several packages into a larger package. Depending on the configuration of the RLC protocol, RLC may or may not put an RLC header in front of the resulting RL C packets. RLC then uses the services of the MAC layer (3G TS 25.321, Medium Access Control (MAC), 3GPP March 2000 http://www.3gpp.org/ftp/ S pecs / March_00 / 25_series / 25321-
  • MAC Medium Access Control
  • the protocol architecture of the UMTS air interface of the respective subscriber device and / or the respective Funkkon ⁇ troll unit of the UMTS radio communication system is in particular ⁇ sondere in 3G TS 25.301, UMTS Protocol Architecture, 3GPP March 2000 http: //www.3gpp.org/ftp / Specs / March_00 / 25_series / 25301-340.zip.
  • Basically is called access points, the service ⁇ where the UMTS air interface specifically provides the layers above the packet data protocols (PDPs), their service is available, as radio bearer.
  • PDPs packet data protocols
  • Radio Bearer is therefore, in particular, a carrier service for transmitting data over the air interface of the UMTS radio communication system. It is possible to use several radio bearers in one UE, ie subscriber device, for example when two applications want to transmit their data with different service qualities and for this purpose set up two different radio bearers.
  • the structure and configuration of the radio bearer, as well as the configuration of all protocols involved and the negotiation of the configuration parameters of the air interface is preferably carried out by a higher-level protocol such as RRC (3G TS 25.331, Radio Resource Control (RRC), 3GPP March 2000, http: //www.3gpp.org/ftp/Specs/March_00/25_series/25331-320.zip) controlled.
  • RRC Radio Resource Control
  • 3GPP March 2000 http: //www.3gpp.org/ftp/Specs/March_00/25_series/25331-320.zip
  • the functionality of the PDCP layer of UMTS is of particular interest, which is described in detail below.
  • a PDCP protocol instance is thus initiated and configured.
  • the possible tasks of such a PDCP instance are, for example:
  • the UMTS standard only specifies a possible algorithm for TCP / IP header compression according to RFC 2507 (RFC 2507, IP Header Compression, IETF February 1999, http://www.ietf.org/rfc.html), but it is described in In the future, there will probably be several other compression methods in PDCP (eg also for RTP / UDP / IP header compression). Compression methods for control data reduction work in particular roughly according to the following principle:
  • PDCP transmitters and receivers create an identical database of stored control data headers or parts thereof at the time of data transmission.
  • This database is start the data transmission (ie immediately after the radio beamer and thus the PDCP instance has been set up) empty and is filled with time.
  • the transmitter PDCP receives a data packet ⁇ (for example. IP packet) from a higher layer, the associated data compression unit compares their data packet ⁇ (for example. IP packet) from a higher layer.
  • Control data header (or parts thereof) with the control data headers stored in the database. If it finds a broad match, it replaces all or part of the control data header with one or more references to the database.
  • the decompression algorithm in the receiver of the respective subscriber device and / or the respective network unit, e.g. radio network controller can then use this link to search for the relevant information in its database and use it to restore the original control data header. Find the tax
  • the processing unit in the transmitter does not match, it sends a fill header, i.e. an unchanged control data header. Sender and receiver enter this in their database for later use.
  • the information is expediently sent along with the data, of what type the control data are. In the principle described here, this would be e.g. the information "fill header” or "reference to database”. In PDCP, this information is especially called packet identifier (PID).
  • PID packet identifier
  • the PDCP protocol may replace the control data header with the corresponding data from the database and signal the PDCP protocol which A rt this data.
  • the PDCP protocol is then responsible for sending this information (ie the PID) to the receiver PDCP protocol so that it can signal the type of control data received to the respective decompression unit.
  • Dekompressoinshim can take this information from the transmitted data.
  • PDCP packet data units PDU () are the packet units that are transferred in the respective transmitter from PDCP to RLC and assigned in the respective one RLC recipients are handed over to PDCP).
  • a first, advantageous PDCP PDU format contains only the data generated by the respective data compression unit (PDCP-No-Header-PDU). These are entered in the "Data" field (see Table 4 from 3G TS 25.323, Packet Data Convergence Protocol (PDCP), 3GPP March 2000, http: //www.3gpp. Org / ftp / Specs / March_00 / 25_series / 25323- 310.zip). This is shown schematically:
  • Another advantageous PDCP PDU format also contains information about the PID and a field which differentiates the format of this PDU from other PDU formats (see table 5 from 3G TS 25.323, Packet Data Convergence Protocol (PDCP), 3GPP March 2000, http://www.3gpp.org/ftp/Specs/March 00/25 series / 25323-310.zip, which is shown schematically below).
  • PDCP Packet Data Convergence Protocol
  • the RRC protocol negotiates, among other things, whether or not the PDCP instance belonging to this radio bearer adds its own control data to the data field. If not, then PDCP can only send the PDCP format shown in Table 4. If PDCP adds its own control data header to the data, it can advantageously use several alternative PDU formats, each of which can be distinguished in the receiver by the "PDU type" field (always the first 3 bits).
  • the task of the transmitter PDCP protocol to select a suitable data compression method for each data packet from a PDP and to signal the data compression method used to the receiver. This is particularly the case if the PDCP instances have been configured to use the PDU formats with a PDCP control data header.
  • the data compression method used is then advantageously also signaled in the PID field as follows: The PID values that the first of the data compression methods use are assigned to the first PID values. The PID values that the second data compression method uses are continuously assigned to further PID values. The PID value zero is always for signaling an uncompressed packet uses what can also be regarded as a compression, namely as zero compression.
  • Examples are the data compression procedure according to RFC 2507, IP Header Compression ⁇ sion, IETF February 1999, http://www.ietf.org/rfc.html with the above-mentioned PIDs and another data compression procedure (Method A) with the PIDs AI, A2 and awarded A3 for a PDCP in ⁇ substance, then the PID field in this PDCP instance is as follows (coded according to table 1 of 3G TS 25.323, Packet Data Convergence Protocol (PDCP), 3GPP March 2000 http: //www.3gpp .org / ftp / Specs / March_00 / 25_series / 25323-
  • Table 1 Example of the PID value allocation table
  • the PDCP receiver instance can now determine both the data compression method used and the type of coding within a data compression method.
  • Another function of the PDCP protocol can be the numbering of PDCP PDUs if this has been configured by the RRC protocol.
  • the number then associated with each PDCP PDU is generally not sent with the PDCP PDU via the air interface, but is used for packet loss or packet duplication detection in the case of a so-called SRNS (serving radio network subsystem).
  • SRNS serving radio network subsystem
  • receiving unit may advises preferably a subscriber unit, in particular Mobilfunkge ⁇ , o r an RNC controller (Radio Network Controller) ver ⁇ turns his.
  • Mobilfunkge ⁇ a subscriber unit
  • RNC controller Radio Network Controller
  • the multiplexing is done in two different ways, depending on what have been configured for koll PDCP PDU formats for the PDCP proto ⁇ :
  • the existing PID field is used for the signaling necessary for multiplexing:
  • Each radio bearer using the PDCP protocol instance is assigned at least one PID value.
  • Such radio projectors for which data compression methods have been configured in PDCP and which require PID signaling by PDCP are already assigned PID values according to methods known in the art.
  • Radio bearers that do not use compression methods or that have been configured for data compression methods that do not require PID signaling are now always assigned PID values (exactly one per radio bearer) according to the invention.
  • the PDCP protocol is configured such that it precedes each data packet with a control data header that contains the PID field, the information for demultiplexing is thus advantageously contained in each PDCP PDU.
  • the receiving PDCP instance reads out the PID field and uses it to d erem to determine the right recipient of the data (the correct PDP).
  • This method has the particular advantage that the PDCP protocol instance can clearly assign the data even in compressed form or packets of different PDP types to a radio beamer, although it cannot read the PDP address because it is either compressed or the PDCP Protocol has no knowledge of the PDP type.
  • a further advantage is in particular that the PID field available in the prior art is used to transport the multiplex information and that additional values from the value range of the PID field are only assigned to those radio bearers that do not exist according to the prior art Use PID.
  • the PDP address will be used to distribute the packets to different radio stations Bearer used.
  • PDCP Since there is no field in the PDCP PDU for data generated by the PDCP protocol, or radio bearers who use the same compression method cannot be clearly identified by the PID field, PDCP preferably relies on the signaling in the PDP's own control data. th. It will be so in the PDCP entity at the transmitter to ⁇ packet data no control data added so that the receiver of the packet data, the PDP address read out and is used for routing to the appropriate radio bearer.
  • the type of PDP (eg IP) is known to the PDCP protocol instance. Since this is not signaled, only radio bearers from the same PDP can be multiplexed in this method using a PDCP protocol. Furthermore, if header compression is used, all radio bearers expediently use the same compression method, since a distinction between radio bearers can only be made after decompression.
  • radio bearers that are to be multiplexed together have a different PDP address.
  • one PDP ie one PDP address
  • QoS quality of service used
  • multiplexed radio bearers use the same RLC unit, they also use the same QoS.
  • radio bearers with the same PDP address are not multiplexed onto the same RLC unit in order to be able to clearly classify their data streams later and assign them to the radio bearers.
  • This method has the particular advantage that it allows the multiplexing of (theoretically) any number of radio bearers onto a data stream without further signaling via the air interface.
  • the PID field is present in the PDCP PDU, then it is preferably used for multiplexing for such radio bearers, co co M h 1 P 1
  • P- rt s PP PJ ⁇ 3 CL ⁇ tr cn ⁇ l vP OP ⁇ s; ⁇ P tr p- N rt ⁇ ! p- P hd P rt cn ⁇ - ⁇ OP ) O ro ⁇ cn ⁇ 13 ⁇ rt P> ro rt P p: P- ⁇ PP ro P ⁇ P »rt ü rt rt P- ro 3 PP P- P- P - P - P C ⁇ ⁇ l ⁇ 1 P- ⁇ iQ tr P vQ iQ P ) co cn ⁇ ⁇ 1 P ⁇ P- hd P
  • the data link ⁇ provides layer, in this case the PDCP protocol 130 in front ⁇ some manner that may in particular be made between the following packet types: Filling header, Compressed TCP, Compressed TCP nondelta, Com ⁇ pressed non TCP, Context state, Uncompressed TCP / IP, Com ⁇ pressed TCP / IP
  • SAP Service Access Point
  • the data packets of its data stream DS300 are first subjected to a specifically assigned data compression process in the subsequent data compression unit CA400.
  • a specific identification is carried out in a subsequent identification unit KE400 for this compressed data stream DS400 *. Only then is the data stream DS400 * individualized in this way fed to a downstream multiplexer unit MUP1.
  • the compressed and labeled data stream of the radio bearer RB300 together with the data packets of other data streams from other radio bearers such as RB310, RB320, RB330 are multiplexed and transmitted to the RLC unit RLC600.
  • the compression unit CA410 is immediately followed by the identification unit KE410. Only then is this marked data stream DS410 * also supplied to the multiplexer unit MUP1.
  • the marking unit CA410 is therefore arranged between the compression unit CA400 and the multiplexer unit MUP1. If the packet reaches PDCP via the fourth Radio Bearer RB330, the PID field is set to 9, for example. This individualizing identification is expediently carried out with the aid of the specially assigned identification unit KE330. Only then is this individualized data stream DS330 * fed to the common multiplexer unit MUP1.
  • Data packets can be clearly assigned to the data streams (DS340, DS350, DS360) originally fed into the transmission unit.
  • the individualized identification of the respective data stream in front of the multiplexer unit can already be predefined by its PDP field.
  • a subscriber device in particular a mobile radio device (MP), or an RNC controller (radio network controller) can preferably be used as the transmitting unit.
  • a subscriber device in particular a mobile radio device (MP), or an RNC controller (radio network controller) can likewise preferably be used as the receiving unit.
  • a radio control unit in particular an RLC unit (radio link control), is preferably selected as the network unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne le multiplexage d'une pluralité de paquets de données de plusieurs trains de données (DS300, DS310, DS320, DS330) sur une unité RLC associée (commande liaison radio) (RLC600) dans le protocole PDCP (protocole de convergence de données en paquets) d'un système de radiocommunication UMTS. Les différents trains de données sont transmis, avant leur multiplexage, avec différentes procédures de compression de données. Entre chaque unité de compression de données (CA400, CA410) et l'unité de multiplexage (MUP1), on procède au moins à une caractérisation individuelle du train de données (DS400*, DS410*, DS330) parvenant à chaque fois dans l'unité de multiplexage (MUP1).
PCT/DE2001/002327 2000-06-28 2001-06-25 Procede de multiplexage d'une pluralite de paquets de donnees de plusieurs trains de donnees dans le protocole pdcp d'un systeme de radiocommunication umts Ceased WO2002001774A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE2000131494 DE10031494A1 (de) 2000-06-28 2000-06-28 Verfahren zum Multiplexen einer Vielzahl von Datenpaketen mehrerer Datenströme innerhalb des PDCP-Protokolls eines UMTS-Funkkommunikationsystems
DE10031494.5 2000-06-28

Publications (2)

Publication Number Publication Date
WO2002001774A2 true WO2002001774A2 (fr) 2002-01-03
WO2002001774A3 WO2002001774A3 (fr) 2002-05-02

Family

ID=7647093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2001/002327 Ceased WO2002001774A2 (fr) 2000-06-28 2001-06-25 Procede de multiplexage d'une pluralite de paquets de donnees de plusieurs trains de donnees dans le protocole pdcp d'un systeme de radiocommunication umts

Country Status (2)

Country Link
DE (1) DE10031494A1 (fr)
WO (1) WO2002001774A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002030043A3 (fr) * 2000-10-03 2003-09-18 Ericsson Telefon Ab L M Identification de contexte a l'aide d'une cle de compression d'en-tete sur la couche de liaison
CN100583805C (zh) * 2001-08-22 2010-01-20 西门子公司 在使用共同混合自动请求重发过程的情况下数据包的传输方法和装置
EP2405705A4 (fr) * 2009-03-04 2013-07-10 China Academy Of Telecomm Tech Procédé, système et appareil permettant d'indiquer un format d'unité
CN111475331A (zh) * 2020-03-24 2020-07-31 平安银行股份有限公司 数据校验方法、装置、计算机设备和存储介质

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU7287900A (en) * 1999-09-17 2001-04-24 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for multiplexing packet data flows

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002030043A3 (fr) * 2000-10-03 2003-09-18 Ericsson Telefon Ab L M Identification de contexte a l'aide d'une cle de compression d'en-tete sur la couche de liaison
US6967964B1 (en) 2000-10-03 2005-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Context identification using header compression key at link layer
CN100583805C (zh) * 2001-08-22 2010-01-20 西门子公司 在使用共同混合自动请求重发过程的情况下数据包的传输方法和装置
EP2405705A4 (fr) * 2009-03-04 2013-07-10 China Academy Of Telecomm Tech Procédé, système et appareil permettant d'indiquer un format d'unité
CN111475331A (zh) * 2020-03-24 2020-07-31 平安银行股份有限公司 数据校验方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
DE10031494A1 (de) 2002-01-10
WO2002001774A3 (fr) 2002-05-02

Similar Documents

Publication Publication Date Title
DE60218431T2 (de) Transfer von ip-daten in einem kommunikationssystem unter verwendung mehrerer logischer verbindungen für komprimierte felder auf der grundlage verschiedener kontexte
DE60106457T2 (de) Zuteilung von datenübertragungsbetriebsmitteln bei der paketvermittelten datenübertragung
DE60316094T2 (de) Verfahren, Vorrichtung und System für die Komprimierung von verlängerten Kopffeldern
DE60130479T2 (de) Definieren einer kontextkennung bei der kopffeldkomprimierung
EP1273147B1 (fr) Procede d'utilisation d'un reseau de telephonie mobile
DE19950653B4 (de) Verfahren zum Betreiben eines Mobilfunknetzes
DE60131890T2 (de) Dynamische Delta-Kopierung für Kabelmodemkopffeldunterdrückung
DE19723659B4 (de) Datenkommunikationssystem und Verfahren zur Chiffrierung zu übertragender Daten
DE60200285T2 (de) Verlustfreie SRNS Relocation Prozedur in einem Funkkommunikationssystem
DE69833111T2 (de) Bestimmung von trägerdiensten in einem funkzugriffsnetz
EP1252787B1 (fr) Procede pour faire fonctionner un reseau de telephonie mobile
DE20023164U1 (de) Vorrichtung zum Austauschen von Daten variabler Länge entsprechend einem Funkverbindungsprotokoll in einem mobilen Kommunikationssystem
DE69932184T2 (de) Verfahren und vorrichtung zur reduzierung der verarbeitungszeit von daten in kommunikationsnetzwerken
DE60202352T2 (de) System und verfahren zur verarbeitung falscher daten in einem paketvermittelten kommunikationssystem, wobei die pakete unterteilt und in teilen verarbeiten werden
EP1994677A1 (fr) Procédé de transmission de l'identifiant d'un message à diffusion sélective, procédé de transmission d'un message à diffusion sélective, dispositif d'émission d'un message à diffusion sélective, dispositif de réception d'un message à diffusion sélective e
DE69905623T2 (de) Paketdatenübertragung im mobilfunksystem der dritten generation
WO2002001774A2 (fr) Procede de multiplexage d'une pluralite de paquets de donnees de plusieurs trains de donnees dans le protocole pdcp d'un systeme de radiocommunication umts
EP1049294B1 (fr) Réseau avec plusieurs grappes de réseau pour radiocommunication de paquets
WO2002067489A1 (fr) Procede de transmission de donnees
EP1505845A1 (fr) Procédé et dispositif pour déterminer au moins un paramètre de transmission dans un système de transmission
EP1301000A1 (fr) Allocation des canaux des données de contrôle dans des systèmes de communication sans fil
EP1376940B1 (fr) Procédé pour la transmission de données
DE10124996A1 (de) Mobilfunksystem, Basisstation-Demodulator für das Mobilfunksystem, und Verfahren zum Terminieren einer Vielzahl von ATM-Leitungen in dem Basisstation-Demodulator
DE69931132T2 (de) Funkstrecke mit dynamischer Anpassung
DE19944334C1 (de) Verfahren zum Betreiben eines Mobilfunknetzes

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): CA CN IN JP KR US

AL Designated countries for regional patents

Kind code of ref document: A2

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP