USOO7245636B1
`
`(12)
`
`United States Patent
`Hans et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7.245,636 B1
`Jul. 17, 2007
`
`(54) METHOD FOR OPERATING AMOBILE
`RADIOTELEPHONE NETWORK
`
`(75) Inventors: Martin Hans, Hildesheim (DE); Mark
`Beckmann, Hameln (DE)
`(73) Assignee: Robert Bosch GmbH. Stuttgart (DE)
`
`(*) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 1028 days.
`(21) Appl. No.:
`10/111511
`(22) PCT Filed:
`Sep. 19, 2000
`(86). PCT No.:
`PCT/DEOO/O3247
`
`S 371 (c)(1),
`(2), (4) Date: Sep. 17, 2002
`(87) PCT Pub. No.: WO01/30042
`PCT Pub. Date: Apr. 26, 2001
`Foreign Application Priority Data
`(30)
`Oct. 21, 1999 (DE) ................................ 199 50 653
`
`(51) Int. Cl.
`(2006.01)
`H04O 7/22
`(2006.01)
`H04L 29/06
`(52) U.S. Cl. ...................... 370/474; 370/338: 370/352;
`455/.445
`(58) Field of Classification Search ........ 370/312–328,
`370/338-349,390-394, 469-474; 455/412–426;
`709)206, 223
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`
`7, 1996 Gardner
`5,533,029 A
`5,553,314 A * 9/1996 Grube et al. ................ 455,514
`5,818,871 A * 10/1998 Blakeney et al. ........... 375,220
`5,936,966 A
`8/1999 Ogawa et al.
`
`
`
`6,205,140 B1* 3/2001 Putzolu et al. .............. 370,389
`
`(Continued)
`FOREIGN PATENT DOCUMENTS
`
`DE
`
`19847 679
`
`5, 1990
`
`(Continued)
`OTHER PUBLICATIONS
`14 Compressing TCP/IP Headers for Low Speed Serial
`
`(Continued)
`Primary Examiner Man U. Phan
`(74) Attorney, Agent, or Firm—Kenyon & Kenyon LLP
`(57)
`ABSTRACT
`
`A method of operating a mobile wireless network is
`described to ensure proper function of protocol entities
`during the transmission of data units between two wireless
`stations of the mobile wireless network. In this case, user
`data is assembled by a first convergence protocol layer of the
`first wireless station into at least one first data unit, particu
`larly a packet data unit, before transmission to a second
`convergence protocol layer of a second wireless station,
`particularly on the same protocol level, with the user data
`being Supplied to the first convergence protocol layer by at
`least one user in a network layer. At least one protocol entity
`of the first convergence protocol layer is configured as a
`function of a configuration request received by the second
`wireless station, in order to form the at least one first data
`unit from the data received from the at least one user and to
`transmit it through a carrier to a link control layer.
`
`20 Claims, 4 Drawing Sheets
`
`
`Ex.1008 / Page 1 of 14Ex.1008 / Page 1 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 7,245,636 B1
`Page 2
`
`U.S. PATENT DOCUMENTS
`370/401
`6400,722 B1* 6, 2002 Chuah et all
`llal C al. . . . . . . . . . . . . . . .
`370,338
`6,404,754 B1* 6/2002 Lim ...........
`6.421,374 B2 *
`7/2002 Blakeney et al. ........... 375/220
`6,483,822 B1 * 1 1/2002 Lioy et al. ........
`... 370,329
`6,504,836 B1* 1/2003 Li et al. .....
`... 370,349
`6,658,235 B1 : 12, 2003 Tolmunen et al.
`455/67.13
`6,717,928 B1 * 4/2004 Kalliokulu et al. ........ 370,335
`6,848,008 B1* 1/2005 Sevanto et al. ...... ... 709/249
`2005/0050429 A1* 3/2005 Proctor, Jr. ................. 714/758
`
`
`
`FOREIGN PATENT DOCUMENTS
`
`DE
`
`19944 334
`
`12/2000
`
`WO
`WO
`WO
`
`WO 96 2.1984
`WO 97 48.212
`WO 99/22557
`
`T 1996
`12/1997
`5, 1999
`
`OTHER PUBLICATIONS
`“Radio Interface Protocol Architecture', 3 GPP TS 25.301.
`RFC 2507 “IP Header Compression”.
`ications Svstem (UMTS);
`ETSI. Uni
`1 Mobile Tel
`, Universal Mobile Telecommunications System (
`);
`Packet Data Convergence Protocol (PDCP) Specification 1999, pp.
`1-17, (3GPP TS 25.323 version 3.3.0 Release 1999).
`* cited by examiner
`
`
`Ex.1008 / Page 2 of 14Ex.1008 / Page 2 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`U.S. Patent
`
`Jul. 17, 2007
`
`Sheet 1 of 4
`
`US 7.245,636 B1
`
`Wireless Station /
`Base Station
`
`15
`
`Wireless Station
`
`/
`
`30
`Mobile Wireless
`Fi 9. 1 Network
`
`80
`
`Radio
`Resource
`Control
`
`
`
`
`
`
`
`
`
`
`
`Network
`Layer
`Convergence
`Protocol
`
`Control
`Layer
`
`MAC Layer
`
`Layer
`
`
`
`
`
`
`
`Radio
`Resource
`Control
`
`Layer
`
`MAC Layer
`
`Physical
`Layer
`
`
`
`
`
`
`
`15
`Wireless Station
`
`FQ. 2
`9.
`
`Wireless Station /
`Base Station
`6
`
`
`Ex.1008 / Page 3 of 14Ex.1008 / Page 3 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`U.S. Patent
`
`Jul. 17, 2007
`
`Sheet 2 of 4
`
`US 7.245,636 B1
`
`-- - - - - - - - - - -
`Layer 22
`
`-
`
`Il- --
`Access Point
`a1
`101
`
`Compression
`Algorithm
`-
`
`Access Point
`102
`
`
`
`convergence
`
`Protocol.
`Layer
`
`351 N.
`PDCP
`Protocol
`Entity
`
`
`
`
`
`Carrier
`
`Compression
`Algorithm
`
`10
`
`--4---------
`
`-
`
`-- - - - - - - - - - - - - - -
`Fig. 3
`
`
`Ex.1008 / Page 4 of 14Ex.1008 / Page 4 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`U.S. Patent
`
`Jul. 17, 2007
`
`Sheet 3 of 4
`
`US 7.245,636 B1
`
`Wireless Station
`
`Wireless Station /
`Base Station
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`16
`
`Communication
`
`Configuration
`Request
`
`Fig. 4
`
`Confirmation
`Signal
`55
`
`Wireless Station
`
`
`
`
`
`15
`
`16
`
`1 Configuration
`
`Reillest
`
`56
`Confirmation
`Sional
`
`42
`
`Configuration
`Recuest
`
`57
`
`Confirmation
`Signal
`
`
`
`
`
`
`
`
`
`
`
`t
`
`Wireless Station /
`Base Station
`
`Fig. 5
`
`
`
`t
`
`"UE Capability
`
`
`
`"PDCP Capability"
`Information
`Element
`Information
`Element
`
`60
`
`-65 it."
`62
`Information
`Element
`
`61
`Sub-information
`Element
`
`1.
`
`1
`
`/
`
`N
`N
`N
`
`Fig. 6
`
`115
`111
`Sub-information
`Sub-information
`Element
`Element
`Sub-information 112 113 11, Sub-information
`Element
`Element
`
`
`Ex.1008 / Page 5 of 14Ex.1008 / Page 5 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`U.S. Patent
`
`Jul. 17, 2007
`
`Sheet 4 of 4
`
`US 7.245,636 B1
`
`Other
`Information
`Element
`
`f PDCP Info
`Information
`Element
`
`/
`Sub-information/
`Element
`/
`
`Other
`information
`Element
`N
`N
`N
`
`70 Carrier
`Configuration
`Message
`
`Fi 9. 7
`
`Sub-information
`Element
`
`
`
`118
`116 / 117
`Sub-information
`Sub-information
`Element
`Element
`
`12O
`Sub-information
`Element
`
`75 Acknowledgement
`- Message
`
`
`
`Confirmation
`
`T. D
`
`Fig. 8
`
`
`Ex.1008 / Page 6 of 14Ex.1008 / Page 6 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 7,245,636 B1
`
`1.
`METHOD FOR OPERATING AMOBILE
`RADIOTELEPHONE NETWORK
`
`FIELD OF THE INVENTION
`
`The present invention relates to a method for operating a
`mobile wireless network.
`
`BACKGROUND INFORMATION
`
`A method for operating a mobile wireless network is
`described in German Published Patent Application No. 199
`44 334 in which data is assembled into at least one unit,
`particularly a packet data unit, by a first convergence pro
`tocol layer before transmission to a second convergence
`protocol layer, particularly on the same protocol level, with
`the data being Supplied to the first convergence protocol
`layer by a user in a network layer.
`
`10
`
`15
`
`SUMMARY OF THE INVENTION
`
`2
`fies to the first wireless station, in a specified or selectable
`manner, those settings for the configuration of the at least
`one protocol entity which are also implementable in the first
`wireless station.
`The communication may be transmitted to the second
`wireless station together with a message about the capabili
`ties and the output range of the first wireless station. In this
`manner, an additional information element for the transmis
`sion of the communication may be eliminated, and therefore
`transmission bandwidth may be saved.
`The configuration request, in the case in which a carrier
`is established, reconfigured, or cleared using a carrier con
`figuration message, may be inserted into the carrier configu
`ration message. In this manner, an additional information
`element for the transmission of the configuration request
`may be eliminated, and therefore transmission bandwidth
`may be saved.
`The confirmation signal may be inserted into a message
`issued by the first wireless station to acknowledge the
`establishment or the reconfiguration of the carrier. In this
`manner, an additional information element for the transmis
`sion of the confirmation signal may be eliminated, and
`therefore transmission bandwidth may be saved.
`
`25
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`In an example method according to the present invention
`at least one protocol entity of the first convergence protocol
`layer may be configured as a function of a configuration
`request received from a second wireless station in order to
`form at least one first data unit from the data received from
`the at least one user and may transmit it to a link control
`layer through a carrier. In this manner, protocol entities may
`be generated in the first wireless station whose settings and
`function may be identical to the settings and function of
`corresponding protocol entities of the second wireless sta
`tion, so that proper functioning of the protocol entities may
`be ensured during the transmission of the data units between
`the two wireless stations.
`The example method may be refined and improved.
`Using the configuration request, at least one selection for
`alternative settings for the protocol entity, which may be
`Supported by the second wireless station, may be predeter
`mined. In this manner, the first wireless station may select
`the most favorable setting for a first wireless device from the
`alternative settings as a function of its own capabilities or its
`own output range and/or as a function of a user preset.
`A confirmation signal may be transmitted from the first
`wireless station to the second wireless station in which the
`setting selected and performed by the first wireless station is
`communicated to the second wireless station. In this manner,
`the second wireless station may configure its at least one
`protocol entity as a function of the setting performed for the
`first wireless station, in order to ensure proper functioning of
`the protocol entities during the transmission of the data units
`between the two wireless stations.
`During the configuration, a protocol entity ID may be
`specified, through which the protocol entity is referenceable.
`In this manner, the protocol entity may be accessed rapidly
`and directly for later reconfigurations and to release the
`protocol entity.
`The protocol entity ID may be specified so that it corre
`sponds to the ID of the carrier assigned to it. In this manner,
`the transmission of an additional information element for
`identifying the protocol entity may be eliminated, and there
`fore transmission bandwidth may be saved.
`A communication may be transmitted from the first wire
`less station to the second wireless station, before receipt of
`the configuration request, indicating which settings of the at
`least one protocol entity are supported by the first wireless
`station. In this manner, it may be ensured that the second
`wireless station, using the configuration request, only speci
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`FIG. 1 shows a mobile wireless network having two
`wireless stations.
`FIG. 2 shows a protocol layer sequence for the two
`wireless stations.
`FIG.3 shows a detail from the protocol layer sequence of
`a first of the two wireless stations.
`FIG. 4 shows a first variation over time of a signaling
`exchange between the two wireless stations.
`FIG. 5 shows a second variation over time of a signaling
`exchange between the two wireless stations.
`FIG. 6 shows a message element for communicating the
`capabilities or the output range of the first wireless station.
`FIG. 7 shows a carrier configuration message.
`FIG. 8 shows an acknowledgment message.
`
`DETAILED DESCRIPTION
`
`In FIG. 1, 30 identifies a mobile wireless network in
`which a first wireless station 15 and a second wireless station
`16 are located. Second wireless station 16 is connected in
`this case to a network unit 80, which offers services for
`subscribers in mobile wireless network 30 and operates
`mobile wireless network 30. First wireless station 15 is, in
`this example, a subscriber of mobile wireless network 30,
`for example in the form of a mobile telecommunication
`terminal or a mobile station, particularly in the form of a
`mobile telephone. In the following, first wireless station 15
`is to be implemented as a mobile station. Second wireless
`station 16 is, in this example, a base station of mobile
`wireless network 30. However, it may not be relevant for the
`present invention whether first wireless station 15 and/or
`second wireless station 16 is a subscriber or a base station of
`the mobile wireless network. In this case, mobile wireless
`network 30 may have further base stations and subscribers,
`which are not, however, illustrated in FIG. 1.
`Mobile wireless network 30 may, for example, be oper
`ated according to a GSM standard (Global System for
`Mobile Communications) or according to a UMTS standard
`(Universal Mobile Telecommunications System) or the like.
`The present invention relates to a packet data convergence
`protocol for mobile wireless networks. The present inven
`
`Ex.1008 / Page 7 of 14Ex.1008 / Page 7 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`15
`
`3
`tion Suggests functionalities within a convergence protocol
`layer 1, 2 as shown in FIG. 2, which may be used in, for
`example, a mobile wireless system according to the UMTS
`standard (Universal Mobile Telecommunications System) or
`also in a mobile wireless system according to the GSM
`standard. In the following, it may be assumed for exemplary
`purposes that mobile wireless network 30 is operated
`according to the UMTS standard.
`The convergence protocol used according to the UMTS
`standard is referred to in this case as PDCP (Packet Data
`Convergence Protocol).
`The functionalities of the UMTS mobile wireless system
`may be divided into layers, as may also be the case in the
`GSM mobile wireless system shown in FIG. 2. Various
`protocols may be specified within the layers which may
`make various services available to each of the higher layers
`and which may make use of the services offered by lower
`lying layers. Each protocol exists in this case at least two
`times within the mobile wireless system, namely in at least
`two units, with the units each lying in the same layer. In this
`case, mobile station 15 represents a first of the two units.
`Base station 16 represents a second of the two units. The
`layer hierarchy described is classified into a user level and
`a control level in this case. The user level may also be
`referred to as a user plane and the control level may also be
`referred to as a control plane. Protocols in which user data
`is transported are assigned to the user level in this case.
`Protocols in which control data is transported and partially
`generated are assigned to the control level. The layer or
`protocol hierarchy of the user level may be relevant for this
`present invention since the convergence protocol layer lies
`in the user level and provides services for user data trans
`port. User data which is generated by applications and
`packets and is to be transmitted in a packet-oriented manner
`is initially transferred from the appropriate application to a
`transport layer protocol in a transport layer. The TCP (Trans
`mission Control Protocol) and the UDP (User Datagram
`Protocol) may be conventional in this regard. However,
`other transport layer protocols or a transparent transport
`layer may also be possible, through which the user data to
`be transmitted is relayed transparently without using a
`transport layer protocol. Transport layer protocols may be
`used for the purpose of securing the packet data for transport
`through mobile wireless network 30, which is used in this
`case as a packet data network, and for attaching the desired
`routing information to it. The transport layer may use
`services of a network protocol in a network layer lying
`underneath the transport layer. The network layer is illus
`trated in FIG. 2 and is identified using the reference number
`5 for mobile station 15 and using the reference number 6 for
`base station 16. The network protocols are, as described,
`referred to as PDP (Packet Data Protocol). The transport
`layer uses the services of the PDPs in order to transmit the
`user data. Example PDPs of network layer 5, 6 may include
`IP (Internet Protocol) and the X.25 protocol. Both the
`network and the transport protocols may attach control data
`to the user data, for example in the form of a TCP/IP header.
`The UMTS-specific protocols may lie underneath network
`layer 5, 6. Data about the data link used by the PDP is stored
`using each PDP in mobile wireless network 30 and in a
`terminal of the mobile wireless network which communi
`cates with mobile wireless network 30, for example in
`mobile station 15. This data may, for example, contain
`parameters about quality of service QOS and is referred to
`as PDP context. It may be possible to operate a PDP
`65
`simultaneously using different contexts, with the contexts
`only differing in the parameters for quality of service QOS.
`
`40
`
`45
`
`50
`
`55
`
`60
`
`US 7,245,636 B1
`
`10
`
`25
`
`30
`
`35
`
`4
`Therefore, in a terminal, an IP protocol having an IP address
`may be operated once using a first parameter for quality of
`service QOS and once using a second parameter for quality
`of service QOS. PDP contexts may, however, also be based
`on different network protocols. Thus, for example, three
`different network protocols may run in one terminal: two IP
`protocols having different IP addresses and one X.25 pro
`tocol.
`Each of these PDP contexts is illustrated as an indepen
`dent block in network layer 5, 6 above convergence protocol
`layer 1, 2 and is indicated in FIG. 3 for mobile station 15
`using reference numbers 21 and 22. In this case, PDP
`contexts 21, 22 represent users of convergence protocol
`layer 1, 2 shown in FIG. 3 lying underneath network layer
`5, 6. In FIG. 2, the convergence protocol layer for mobile
`station 15 is indicated using reference number 1 and the
`convergence protocol layer for base station 16 is indicated
`using reference number 2.
`The PDCP, whose task is to prepare the data to be
`transmitted between mobile station 15 and base station 16
`for efficient UMTS transmission, tailors the user data which
`comes from a PDP context for transmission via an air
`interface, in that it optionally compresses the user data
`and/or the control data or protocol control information added
`to the user data and combines or multiplexes possible packet
`data streams from different PDP contexts 21, 22, which
`require the same transmission quality, into one packet data
`Stream.
`In the layer model of the UMTS mobile wireless system,
`an RLC link control layer (Radio Link Control) is located
`underneath convergence protocol layer 1, 2 provided for
`forming the PDCP, which is indicated for mobile station 15
`using reference number 10 and for base station 16 using
`reference number 11 in FIG. 2 and which optionally corrects
`transmission errors of the air interface, in that it requests any
`faulty packets to be resent on the receiver end and resends
`them on the transmitter end. Furthermore, RLC link control
`layer 10, 11 optionally ensures that the sequence of the data
`packets is maintained during transmission and segments the
`data packets into RLC-PDUs (RLC Packet Data Units),
`whose length is tailored to the transmission channels used.
`A data carrier, which may also be referred to as a radio
`bearer or RB, and which provides RLC link control layer 10,
`11 lying underneath convergence protocol layer 1, 2, is then
`used for the transmission of any of the multiplexed packet
`data streams from various PDP contexts 21, 22.
`Convergence protocol layer 1, 2 has PDCP protocol
`entities 35 as shown in FIG. 3, each of which may contain
`multiple compression algorithms 50, 51. Multiple PDP con
`texts 21, 22 may be connected to one PDCP protocol entity
`35; however, one PDP context 21, 22 may only be connected
`to one PDCP protocol entity 35. Each PDCP protocol entity
`35 uses one carrier 45, which may also be referred to as a
`radio bearer. A radio bearer is the link between a PDCP
`protocol entity 35 and an entity of underlying RLC link
`control layer 10, 11, via which the data is relayed from
`convergence protocol layer 1, 2 to RLC link control layer 10,
`11. Conventional compression algorithms, such as those
`described in the publication RFC 1144 “Compressing TCP/
`IP Headers for Low Speed Serial Links” for TCP/IP proto
`cols (TCP=Transmission Control Protocol; IP-Internet Pro
`tocol) and in the publication RFC 2507 “IP Header
`Compression” for UDP/IP protocols (UDP=User Datagram
`Protocol), are based on the establishment and use of code
`books, in which codes are stored in the form of tables, with
`which the user data and/or protocol control information to be
`transmitted is coded and/or compressed in corresponding
`
`Ex.1008 / Page 8 of 14Ex.1008 / Page 8 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 7,245,636 B1
`
`5
`
`10
`
`15
`
`25
`
`30
`
`35
`
`5
`PDCP protocol entity 35 of the transmitting wireless station
`and to which reference is made in the user data and/or
`protocol control information compressed in this manner. The
`codebooks used must also be available in the decompressor
`of the receiving wireless station in order to allow decoding.
`In order to ensure proper functioning of PDCP protocol
`entities 35, compression algorithms 50, 51, their compres
`sion parameters, such as the number of codes to be stored in
`the compressor and decompressor in corresponding code
`books, and the multiplexing information of both conver
`gence protocol layers 1, 2 in mobile station 15 and in base
`station 16 may need to be identical. In this case, the
`multiplexing information indicates which PDP contexts 21,
`22 supply their packet data streams to corresponding PDCP
`protocol entity 35 for multiplexing. Compression algorithms
`50, 51, the compression parameters, and the multiplexing
`information represent PDCP protocol entity parameters,
`which may also include further parameters, such as infor
`mation about carrier 45 to be used by corresponding PDCP
`protocol entity 35. Before setup of a new PDCP protocol
`entity 35, a handshake procedure of both wireless stations
`15, 16 about the PDCP protocol entity parameters to be
`configured is performed. This handshake procedure is per
`formed in the control level by an RRC (Radio Resource
`Control), with radio resource control RRC being identified
`in FIG. 2 for mobile station 15 using reference number 95
`and for base station 16 using reference number 96.
`RLC link control layer 10, 11 uses the services of the
`underlying MAC layer (Medium Access Control) in order to
`transmit the RLC-PDUs. The MAC layer is indicated in FIG.
`2 for mobile station 15 by reference number 85 and for base
`station 16 by reference number 86 and ensures the access to
`the actual transmission medium, selects suitable transport
`formats, and multiplexes the various RLC-PDUs onto suit
`able transport channels, which are mapped onto the assigned
`physical channels in the underlying physical layer, which is
`indicated in FIG. 2 for mobile station 15 by reference
`number 90 and for base station 16 by reference number 91.
`The layer hierarchy or protocol hierarchy is described in the
`publication “Radio Interface Protocol Architecture', 3 GPP
`40
`TS 25.301. Some of the layers described, i.e., physical layer
`90,91, MAC layer 85, 86, RLC link control layer 10, 11, and
`convergence protocol layer 1, 2, also have a direct link to
`radio resource control RRC. This link is used to transmit
`status information to radio resource control RRC 95, 96 and
`to allow radio resource control RRC 95, 96 to configure the
`other protocols.
`Data to be transmitted between mobile station 15 and base
`station 16 runs from top to bottom through the layer
`sequence described. Data received runs from bottom to top
`through the layer sequence described.
`A protocol for controlling radio resource control RRC 95,
`96 is described in the publication “RRC Protocol Specifi
`cation, 3 GPP TSG RAN WG2, TS 25.331 v1.4.2 and is
`referred to in the following as RRC protocol. The objects of
`this RRC protocol may include, among other things, the
`configuration of the individual layers, negotiation of param
`eters for the configuration of the layers with the peer RRC
`layer, and establishment and release of connections between
`mobile station 15 and mobile wireless network 30 and/or,
`acting as mobile wireless network 30 in this example
`embodiment, to base station 16. The peer RRC layer repre
`sents, in this case, a layer of radio resource control RRC 95,
`96 on the same protocol layer level as the layer of mobile
`station 15 and/or base station 16 to be configured. The
`parameters for configuring the individual layers are
`exchanged in messages between the peer RRC layers of
`
`50
`
`45
`
`55
`
`60
`
`65
`
`6
`mobile station 15 and base station 16 in regard to the
`respective layer to be configured.
`The signaling described in the publication “RRC Protocol
`Specification’ cited may not include the negotiation of the
`PDCP protocol entity parameters, i.e., neither the negotia
`tion of compression algorithms 51, 52 and their compression
`algorithms for PDCP protocol entities 35, for example, nor
`the configuration of the multiplexing of the packet data
`streams of multiple PDP contexts 21, 22 in convergence
`protocol layer 1, 2.
`In FIG. 3, a detail from the layer sequence for mobile
`station 15 is illustrated as an example.
`In FIG. 3, network layer 5, convergence protocol layer 1,
`and link control layer 10 of mobile station 15 are illustrated.
`In this case, as shown in FIG. 3, each PDP context 21, 22
`uses the services of convergence protocol layer 1 at a
`respective access point 101, 102 assigned to it, which may
`also be referred to as a network layer service access point
`(NSAP). Each of these access points 101, 102 is assigned an
`identifier, for example an NSAPI (Network Layer Service
`Access Point Identifier), which uniquely identifies assigned
`PDP context 21, 22. Currently, for GSM a maximum of 16
`NSAPs are simultaneously provided in a mobile station 15.
`For UMTS, the number of PDP contexts which may simul
`taneously exist in a mobile station has not yet been specified.
`The links of link control layer 10 are used by convergence
`protocol layer 1 via service access points, which are also
`referred to as SAP (service access point). An identifier RB
`identity (radio bearer identity) is assigned to each of the
`individual connections to the SAPs in order to identify the
`individual connections between convergence protocol layer
`1 and link control layer 10. In this case, each service access
`point offers a specific quality of service or transmission QOS
`and, in the GSM mobile wireless system, a maximum of four
`different service access points, and therefore four different
`links in link control layer 10 having different quality of
`transmission QOS, are provided. In the UMTS mobile
`wireless system, for example, three different service access
`points, each having different links in link control layer 10
`with different qualities of transmission QOS, may be pro
`vided, without being restricted to this example. In order to
`allow convergence protocol layer 1 to be able to relay data
`packets arriving or received at one of the service access
`points to the correct receiver and/or to the correct PDP
`context after decompression of the user data and/or the
`protocol control information, the data packets may have an
`identifier of the receiving PDP context, i.e., the receiving
`user of convergence protocol layer 1, attached by the trans
`mitter. The NSAPI may be used as an identifier for this
`purpose, which is, for example, attached to each data packet
`on the transmitter end as a 4-bit value.
`The links to the service access points described are each
`implemented by a carrier which is, as described, also
`referred to as a radio bearer. A radio bearer is, as described,
`the link between a PDCP protocol entity 35 and an entity of
`underlying RLC link control layer 10, 11, via which the data
`from convergence protocol layer 1, 2 is relayed to RLC link
`control layer 10, 11. In FIG. 3, carrier 45 is illustrated acting
`as the service access points, which, acting as the PDCP
`protocol entities located in convergence protocol layer 1,
`connects PDCP protocol entity 35 to an entity of RLC link
`control layer 10, not illustrated in FIG. 3.
`PDCP protocol entity 35 of convergence protocol layer 1
`described for exemplary purposes includes, in this case, as
`shown in FIG. 3, a data compression algorithm 51 which
`compresses the user data received from network layer 5. A
`data decompression algorithm, not shown in FIG. 3, is
`
`Ex.1008 / Page 9 of 14Ex.1008 / Page 9 of 14
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 7,245,636 B1
`
`10
`
`15
`
`7
`associated with data compression algorithm 51. The data
`decompression algorithm decompresses user data received
`from link control layer 10 and therefore ultimately from base
`station 16. At the same time, it reverses a data compression
`in accordance with assigned data compression algorithm 51.
`PDCP protocol entity 35 of convergence protocol layer 1
`further includes a protocol control information compression
`algorithm 50, which is also referred to in the following as
`first compression algorithm 50 and which compresses the
`protocol control information received from network layer 5
`with the user data and/or generated in convergence protocol
`layer 1 for the user data received. A protocol control
`information decompression algorithm, not shown in FIG. 3,
`which decompresses the protocol control information
`received from link control layer 10 and thus reverses a
`compression according to assigned protocol control infor
`mation compression algorithm 50, is associated in a corre
`sponding way with protocol control information compres
`sion algorithm 50.
`A first PDP context 21 is connected, via a first access point
`101 assigned to it, to protocol control information compres
`sion algorithm 50 and an associated protocol control infor
`mation decompression algorithm. In the following, the com
`pression and decompression algorithms associated with one
`another are viewed as a unit to simplify the description and
`are referenced by the corresponding compression algorithm
`as a Substitute. Thus, protocol control information compres
`sion algorithm 50 is connected via data compression algo
`rithm 51, which is also referred to in the following as second
`compression algorithm 51, to carrier 45.
`A second PDP context 22 is directly connected, via an
`access point 102 assigned to it, to data compression algo
`rithm 51, which is connected to carrier 45, as described. The
`remaining PDP contexts of network layer 5 are not shown in
`FIG. 3 for reasons of clarity, nor are further PDCP protocol
`entities of convergence protocol layer 1 and further carriers.
`The present invention may include procedures which
`allow the negotiation of PDCP protocol entity parameters
`and the establishment of PDCP protocol entities between
`two devices of mobile wireless network 30, in this example
`between mobile station 15 and base station 16, which
`cooperate with network unit 80, for example a radio network
`controller (RNC), and may therefore be understood as acting
`as a network entity.
`In this case, a procedure in which base station 16 receives
`a communication 60, shown in FIG. 4, from mobile station
`15 about the settings supported by mobile station 15 of
`PDCP protocol entity 35 to be configured of mobile station
`15 is at the beginning of the negotiations. In this example,
`the configuring of PDCP protocol entity 35 illustrated in
`FIG. 3 is described as an example. Multiple PDCP protocol
`entities of mobile station 15 may, of course, be configured
`simultaneously in a corresponding manner.
`Directly before the initial setup of PDCP protocol entity
`35, base station 16, shown in FIG. 4, sends a first configu
`ration request 40 to mobile station 15, in which the initial
`setup of PDCP protocol entity 35 is initiated. The PDCP
`protocol entity parameters which base station 16 has
`selected taking into consideration the settings Supported by
`mobile station 15 of PDCP protocol entity 35 to be config
`ured are contained in this first configuration request 40. First
`configuration request 40 may also be referred to as the PDCP
`Establishment Request.
`Mobile station 15 may now establish PDCP protocol
`entity 35 using the PDCP protocol entity parameters
`received in first configuration request 40 from base station
`16. After this establishment, mobile station 15 acknowledges
`
`8
`the establishment and therefore signals to