throbber
(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY(PCT)
`a
`International Bureau
`(19) World Intellectual Property
`# DryAIPOS
`Organization
`bi
`
`
`(43) International Publication Date
`29 December 2005 (29.12.2005)
`
`(51) International Patent Classification’:
`HO4L 12/56, 29/08
`
`H04Q 7/38,
`
`(21) International Application Number:
`PCT/EP2005/006361
`
`(22) InternationalFiling Date:
`
`14 June 2005 (14.06.2005)
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`(30) Priority Data:
`04014004.8
`
`English
`
`English
`
`15 June 2004 (15.06.2004)
`
`EP
`
`(71) Applicant (for all designated States except US): MAT-
`SUSHITA ELECTRIC INDUSTRIAL CO., LTD.
`[JP/JP];
`1006, Oaza Kadoma, Kadoma-shi, Osaka
`571-8501 (JP).
`
`(72) Inventors; and
`(75) Inventors/Applicants (for US only): LOHR, Joachim
`[DE/DE]; Soderstr. 90, 64287 Darmstadt (DE). SEIDEL,
`Eiko [DE/DE]; Moosbergerstr. 97 a-b, 64285 Darmstadt
`(DE). PETROVIC, Dragan [YU/DE]; Am Kaiserschlag
`15, 64295 Darmstadt (DE).
`
`(10) International Publication Number
`WO 2005/125252 Al
`
`(74) Agent: KUHL, Dietmar; Griinecker, Kinkeldey, Stock-
`mair & Schwanhdusser, Maximilianstrasse 58, 80538
`Miinchen (DE).
`
`(81) Designated States (unless otherwise indicated, for every
`kind of national protection available): AE, AG, AL, AM,
`AT, AU, AZ, BA, BB, BG, BR, BW, BY, BZ, CA, CH, CN,
`CO, CR, CU, CZ, DE, DK, DM, DZ, EC, EE, EG, ES,FI,
`GB, GD, GE, GH, GM, HR, HU,ID, IL, IN, IS, JP, KE,
`KG, KM,KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MA,
`MD, MG, MK, MN, MW, Mx, MZ, NA, NG, NI, NO, NZ,
`OM,PG,PII, PL, PT, RO, RU, SC, SD, SE, SG, SK, SL,
`SM, SY, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, VC,
`VN, YU, ZA, ZM, ZW.
`
`(84) Designated States (unless otherwise indicated, for every
`kind of regional protection available): ARIPO (BW, GH,
`GM, KE, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG, ZM,
`ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM),
`European (AT, BE, BG, CH, CY, CZ, DE, DK, EE,ES, FI,
`FR, GB, GR,HU,IE,IS, IT, LT, LU, MC, NL, PL, PT, RO,
`SE, SI, SK, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA, GN,
`GQ, GW, ML, MR, NE, SN, TD, TG).
`
`[Continued on next page]
`
`(54) Title: SCHEDULING MODE DEPENDENT DATA TRANSMISSIONS
`
`transport channel #2
`
`
`
`ai
`Sie
`ie
`te
`\ £
`1g
`LEI
`!
`
`(57) Abstract: The present invention relates to a method for transmitting data from a mobile terminal to a radio access network of
`& a mobile communication system, the mobile terminal comprising a medium access control entity and to a mobile terminal. In order
`©} to enhancedata transmission dependent on the scheduling mode, the present invention provides individual priorities depending on
`the scheduling mode which are used by the mobile terminal to schedule the transmission data or to multiplex different transmission
`data of different radio bearers onto a transport channel. Further the invention relates to a method and mobile terminal allowing a
`scheduling mode dependent scheduling of data transmissions by
`foreseeing andsetting a flag for each logical channel depending on
`the scheduling mode of the associated radio bearer.
`
`Ex.1007 / Page 1 of 59
`
`Ex.1007 / Page 1 of 59Ex.1007 / Page 1 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`
` RLC entity #2
`
`
`
`
`1201
`
`sched. mode #1: MLP = 2
`sched. mode #2: MLP =3
`
`ete
`
`1202
`
`sched. mode #1: MLP = 3
`sched. mode #2: MLP = 4
`
`
`
` RLC entity #1
`
`logical channel #2
`logical channel #1
`
`
`
`
`scheduling mode:~
`
` MACentity
`
`
`
`5/125252AIMVMIMTAMIINTUTATTATAATAA
`
`©S
`
`

`

`WO 2005/125252 Al
`
`Published:
`
`— with international search report
`
`For two-letter codes and other abbreviations, refer to the "Guid-
`ance Notes on Codes and Abbreviations” appearing at the begin-
`ning of each regularissue of the PCT Gazette.
`
`Ex.1007 / Page 2 of 59
`
`Ex.1007 / Page 2 of 59Ex.1007 / Page 2 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`SCHEDULING MODE DEPENDENT DATA TRANSMISSIONS
`
`FIELD OF THE INVENTION
`
`The presentinvention relates to a method for transmitting data from a mobile terminalto
`a radio access network of a mobile communication system,
`the mobile terminal
`comprising a medium access control entity and to a mobile terminal using individual
`priorities. Further the invention relates to a method and mobile terminal allowing a
`scheduling mode dependent scheduling of data transmissions.
`
`TECHNICAL BACKGROUND
`
`10
`
`15
`
`20
`
`25
`
`W-CDMA (Wideband Code Division Multiple Access) is a radio interface for IMT-2000
`(International Mobile Communication), which was standardized for use as the 3"
`generation wireless mobile telecommunication system. It provides a variety of services
`such as voice services and multimedia mobile communication services in a flexible and
`efficient way. The standardization bodies in Japan, Europe, USA, and other countries
`havejointly organized a project called the 3% Generation Partnership Project (3GPP) to
`produce commonradiointerface specifications for W-CDMA.
`
`The standardized European version of IMT-2000 is commonly called UMTS (Universal
`Mobile Telecommunication System). The first release of the specification of UMTS has
`been published in 1999 (Release 99).
`In the mean time several improvements to the
`standard have been standardized by the 3GPP in Release 4 and Release 5 and
`discussion on further improvements is ongoing under the scope of Release6.
`
`The dedicated channel (DCH) for downlink and uplink and the downlink shared channel
`(DSCH) have been defined in Release 99 and Release 4.
`In the following years, the
`developers recognized that for providing multimedia services - or data services in
`general - high speed asymmetric access had to be implemented. In Release 5 the high-
`speed downlink packet access (HSDPA)wasintroduced. The new high-speed downlink
`shared channel (HS-DSCH)provides downlink high-speed access to the user from the
`UMTS Radio Access Network (RAN) to the communication terminals, called user
`
`equipments in the UMTSspecifications.
`
`Ex.1007 / Page 3 of 59
`
`Ex.1007 / Page 3 of 59Ex.1007 / Page 3 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`Hybrid ARQ Schemes
`
`The most common technique for error detection of non-real time services is based on
`
`Automatic Repeat reQuest (ARQ) schemes, which are combined with Forward Error
`Correction (FEC), called Hybrid ARQ.
`If Cyclic Redundancy Check (CRC) detects an
`error, the receiver requests the transmitter to send additional bits or a new data packet.
`From different existing schemes the stop-and-wait (SAW) and selective-repeat (SR)
`continuous ARQ are most often used in mobile communication.
`
`A data unit will be encoded before transmission. Depending on the bits that are
`retransmitted three different types of ARQ maybedefined.
`
`In HARQ Type| the erroneous data packets received, also called PDUs (Packet Data
`Unit) are discarded and new copyof that PDU is retransmitted and decoded separately.
`There is no combining of earlier and later versions of that PDU. Using HARQ TypeII the
`erroneous PDU that needs to be retransmitted is not discarded, but is combined with
`
`someincremental redundancybits provided by the transmitter for subsequent decoding.
`Retransmitted PDU sometimes have higher coding rates and are combined at the
`receiver with the stored values. That meansthatonly little redundancy is added in each
`retransmission.
`
`Finally, HARQ Typelil is almost the same packet retransmission schemeas TypeIl and
`only differs in that every retransmitted PDUis self-decodable. This implies that the PDU
`is decodable without the combination with previous PDUs.
`In case some PDUs are
`heavily damaged such that almost no information is reusable self decodable packets can
`be advantageously used.
`
`. When employing chase-combining the retransmission packets carry identical symbols.In
`this case the multiple received packets are combined either by a symbol-by-symbolor by
`a bit-by-bit basis (see D. Chase: "Code combining: A maximum-likelihood decoding
`approach for combining an arbitrary number of noisy packets", IEEE Transactions on
`Communications, Col. COM-33, pages 385 to 393, May 1985). These combined values
`are stored in the soft buffers of respective HARQ processes.
`
`Packet Scheduling
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Packet scheduling may be a radio resource managementalgorithm used for allocating
`transmission opportunities and transmission formats to the users admitted to a shared
`
`Ex.1007 / Page 4 of 59
`
`Ex.1007 / Page 4 of 59Ex.1007 / Page 4 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`medium. Scheduling may be used in packet based mobile radio networks in combination
`with adaptive modulation and coding to maximize throughput/capacity by e.g. allocating
`transmission opportunities to the users in favorable channel conditions. The packet data
`service in UMTS maybe applicable for the interactive and backgroundtraffic classes,
`though it may also be used for streaming services. Traffic belonging to the interactive
`and backgroundclassesis treated as non real time (NRT)traffic and is controlled by the
`packet scheduler. The packet scheduling methodologies can be characterized by:
`
`e Scheduling period/frequency: The period over which users are scheduled
`
`aheadin time.
`
`10
`
`e Serve order: The order in which users are served, e.g. random order (round
`robin) or according to channel quality (C/I or throughput based).
`
`e Allocation method: Thecriterion for allocating resources, e.g. same data amount
`or same power/code/time resources for all queued users perallocation interval.
`
`The packet scheduler for uplink is distributed between Radio Network Controller (RNC)
`and user equipment in 3GPP UMTS R99/R4/R5. Onthe uplink, the air interface resource
`to be sharedby different users is the total received power at a Node B, and consequently
`the task of the scheduler is to allocate the power among the user equipment(s).
`In
`current UMTS R99/R4/RS5 specifications the RNC controls the maximum rate/power a
`user equipmentis allowed to transmit during uplink transmission by allocating a set of
`different transport formats (modulation scheme, coderate, etc.) to each user equipment.
`
`The establishment and reconfiguration of such a TFCS (transport format combination
`set) may be accomplished using Radio Resource Control (RRC) messaging between
`RNC and user equipment. The user equipment is allowed to autonomously choose
`amongthe allocated transport format combinations based on its ownstatus e.g. available
`powerand buffer status. In current UMTS R99/R4/R5 specifications there is no control
`on time imposed on the uplink user equipment transmissions. The scheduler may é.g.
`operate on transmission time interval basis.
`
`UMTSArchitecture
`
`The high level R99/4/5 architecture of Universal Mobile Telecommunication System
`(UMTS)
`is shown in Fig.
`1
`(see 3GPP TR 25.401: "UTRAN Overall Description",
`available from http:/Awww.3gpp.org). The network elements are functionally grouped into
`
`15
`
`20
`
`25
`
`30
`
`Ex.1007 / Page 5 of 59
`
`Ex.1007 / Page 5 of 59Ex.1007 / Page 5 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`the Core Network (CN) 101, the UMTSTerrestrial Radio Access Network (UTRAN) 102
`and the User Equipment (UE) 103. The UTRAN 102 is responsible for handling all radio-
`related functionality, while the CN 101 is
`responsible for routing calls and data
`connections to external networks. The interconnections of these network elements are
`defined by openinterfaces (lu, Uu). It should be noted that UMTS system is modular and
`it is therefore possible to have several network elementsof the sametype.
`
`Fig. 2 illustrates the current architecture of UTRAN. A number of Radio Network
`Controllers (RNCs) 201, 202 are connected to the CN 101. Each RNC 201, 202 controls
`one or several base stations (Node Bs) 203, 204, 205, 206, which in turn communicate
`with the user equipments. An RNC controlling several base stations is called Controlling
`RNC (C-RNC)for these base stations. A set of controlled base stations accompanied by
`their C-RNCis referred to as Radio Network Subsystem (RNS) 207, 208. For each
`connection between User Equipment and the UTRAN,one RNSis the Serving RNS (S-
`RNS). It maintains the so-called lu connection with the Core Network (CN) 101. When
`required, the Drift RNS 302 (D-RNS) 302 supports the Serving RNS (S-RNS) 301 by -
`providing radio resources as shownin Fig. 3. Respective RNCsare called Serving RNC
`(S-RNC) and Drift RNC (D-RNC). It is also possible and often the case that C-RNC and
`D-RNC are identical and therefore abbreviations S-RNC or RNC are used.
`
`Enhanced Uplink Dedicated Channel (E-DCH)
`
`Uplink enhancements for Dedicated Transport Channels (DTCH)are currently studied by
`the 3GPP Technical Specification Group RAN (see 3GPP TR 25.896: “Feasibility Study
`for Enhanced Uplink for UTRA FDD (Release 6)”, available at http:/Avww.3gpp.org).
`Since the use of IP-based services become more important, there is an increasing
`demand to improve the coverage and throughput of the RAN as well as to reduce the
`delay of the uplink dedicated transport channels. Streaming,interactive and background
`services could benefit from this enhanceduplink.
`
`One enhancementis the usage of adaptive modulation and coding schemes (AMC)in
`connection with Node B controlled scheduling, thus an enhancementof the Uuinterface.
`In the existing R99/R4/R5 system the uplink maximum data rate contro! resides in the
`RNC.Byrelocating the scheduler in the Node B the latency introduced due to signaling
`on the interface between RNC and Node B may be reduced and thus the scheduler may
`be able to respond faster to temporal changesin the uplink load. This may reduce the
`overall latency in communications of the user equipment with the RAN. Therefore Node
`
`15
`
`20
`
`25
`
`30
`
`Ex.1007 / Page 6 of 59
`
`Ex.1007 / Page 6 of 59Ex.1007 / Page 6 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`B controlled scheduling is capable of better controlling the uplink interference and
`smoothing the noiserise variance byallocating higher data rates quickly whenthe uplink
`load decreases and respectively by restricting the uplink data rates whenthe uplink load
`increases. The coverage andcell throughput may be improved bya better control of the
`uplink interference.
`
`is
`Another technique, which may be considered to reduce the delay on the uplink,
`introducing a shorter TT! (Transmission Time Interval) length for the E-DCH compared to
`other transport channels. A transmission time interval
`length of 2ms is currently
`investigated for use on the E-DCH, while a transmission time interval of 10ms is
`commonly used on the other channels. Hybrid ARQ, which was one of the key
`technologies in HSDPA,is also considered for the enhanced uplink dedicated channel.
`The Hybrid ARQ protocol between a Node B and a user equipment allows for rapid
`retransmissions of erroneously received data units, and may thus reduce the numberof
`RLC (Radio Link Control) retransmissions and the associated delays. This may improve
`the quality of service experienced by the end user.
`
`To support enhancements described above, a new MACsub-layeris introduced which
`will be called MAC-eu in the following (see 3GPP TSG RAN WG1, meeting #31, Tdoc
`R0O1-030284, "Scheduled and Autonomous Mode Operation for the Enhanced Uplink").
`The entities of this new sub-layer, which will be described in more detail in the following
`sections, may be located in user equipment and Node B. On user equipmentside, the
`MAC-eu performs the new task of multiplexing upper layer data (e.g. MAC-d)data into
`the new enhancedtransport channels and operating HARQ protocol transmitting entities.
`
`Further, the MAC-eu sub-layer may be terminated in the S-RNC during handoverat the
`UTRANside. Thus, the reordering buffer for the reordering functionality provided may
`also reside in the S-RNC.
`
`15
`
`20
`
`25
`
`E-DCH MACArchitecture at the user equipment
`
`Fig. 4 shows the exemplary overall E-DCH MACarchitecture on user equipmentside. A
`new MACfunctional entity, the MAC-eu 403,
`is added to the MAC architecture of
`Rel/99/4/5. The MAC-eu 405entity is depicted in more detail in Fig. 5.
`
`30
`
`There are M different data flows (MAC-d) carrying data packets to be transmitted from
`user equipment to Node B. These data flows can have different QoS (Quality of Service),
`e.g. delay and error requirements, and may require different configurations of HARQ
`
`5
`
`Ex.1007 / Page 7 of 59
`
`Ex.1007 / Page 7 of 59Ex.1007 / Page 7 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`instances. Therefore the data packets can bestoredin different Priority Queues. The set
`of HARQ transmitting and receiving entities,
`located in user equipment and Node B
`respectively will be referred to as HARQ process. The scheduler will consider QoS
`parameters in allocating HARQ processes to different priority queues. MAC-eu entity
`receives scheduling information from Node B (network side) via Layer 1 signaling.
`
`E-DCH MACArchitecture at the UTRAN
`
`In soft handover operation the MAC-eu entities in the E-DCH MACArchitecture at the
`UTRANside maybedistributed across Node B (MAC-eub) and S-RNC (MAC-eur). The
`scheduler in Node B choosesthe active users and performsrate control by determining
`and signaling a commanded rate,
`suggested rate or TFC (Transport Format
`Combination) threshold that
`limits the active user (UE) to a subset of the TCFS
`(Transport Format Combination Set) allowed for transmission.
`
`In Fig. 6 the Node B MAC-eu
`Every MAC-eu entity corresponds to a user (UE).
`architecture is depicted in more detail. It can be noted that each HARQ Receiverentity is
`assigned certain amountor area of the soft buffer memory for combining the bits of the
`packets from outstanding retransmissions. Once a packet is received successfully,it is
`forwarded to the reordering buffer providing the in-sequence delivery to upperlayer.
`According to the depicted implementation, the reordering buffer resides in S-RNC during
`soft handover (see 3GPP TSG RAN WG1, meeting #31: “HARQ Structure”, Tdoc R1-
`030247, available of http:/Awww.3gpp.org).
`In Fig. 7 the S-RNC MAC-eu architecture
`which comprises the reordering buffer of the corresponding user (UE) is shown. The
`numberof reordering buffers is equal to the numberof data flows in the corresponding
`MAC-eu entity on user equipment side. Data and control information is sent from all
`Node Bs within Active Set to S-RNC during soft handover.
`
`It should be noted that the required soft buffer size depends on the used HARQ scheme,
`e.g. an HARQ schemeusing incremental redundancy (IR) requires more soft buffer than
`one with chase combining (CC).
`
`10
`
`20
`
`25
`
`E-DCH Signaling
`
`30
`
`E-DCH associated control signaling required for the operation of a particular scheme
`consists of uplink and downlink signaling. The
`signaling depends on uplink
`enhancements being considered.
`
`Ex.1007 / Page 8 of 59
`
`Ex.1007 / Page 8 of 59Ex.1007 / Page 8 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`In order to enable Node B controlled scheduling (e.g. Node B controlled time and rate
`scheduling), user equipment has to send some request message on the uplink for
`transmitting data to the Node B. The request message maycontain status information of
`a user equipmente.g. buffer status, power status, channel quality estimate. The request
`messageis in the following referred to as Scheduling Information (Sl). Based on this
`information a Node B can estimate the noise rise and schedule the UE. With a grant
`
`message sentin the downlink from the Node B to the UE, the Node B assigns the UE the
`TFCS with maximum data rate and the time interval, the UE is allowed to send. The
`grant messageis in the following referred to as Scheduling Assignment(SA).
`
`10
`
`15
`
`In the uplink user equipment has to signal Node B with a rate indicator message
`information that is necessary to decode the transmitted packets correctly, e.g. transport
`block size (TBS), modulation and coding scheme (MCS)level, etc. Furthermore, in case
`HARQis used, the user equipment has to signal HARQ related control information (e.g.
`Hybrid ARQ process number, HARQ sequence numberreferred to as New Data
`Indicator (NDI) for UMTS Rel. 5, Redundancy version (RV), Rate matching parameters
`
`etc.)
`
`After reception and decoding of transmitted packets on enhanced uplink dedicated
`channel (E-DCH) the Node B hasto inform the user equipmentif transmission was
`successful by respectively sending ACK/NAKin the downlink.
`
`20
`
`Mobility Managementwithin Rel99/4/5 UTRAN
`
`Before explaining some procedures connected to mobility management, some terms
`frequently used in the following are definedfirst.
`
`A radio link may be defined as a logical association between single UE and a single
`UTRANaccesspoint. Its physical realization comprises radio bearer transmissions.
`
`25
`
`30
`
`A handover may be understood as a transfer of a UE connection from one radio bearer
`to another (hard handover) with a temporary break in connection or inclusion / exclusion
`of a radio bearer to / from UE connection so that UE is constantly connected UTRAN
`(soft handover). Soft handover is specific for networks employing Code Division Multiple
`Access (CDMA)technology. Handover execution may controlled by S-RNCin the mobile
`radio network whentaking the present UTRANarchitecture as an example.
`
`Ex.1007 / Page 9 of 59
`
`Ex.1007 / Page 9 of 59Ex.1007 / Page 9 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`The active set associated to a UE comprises a setof radio links simultaneously involved
`in a specific communication service between UE and radio network. An active set update
`procedure may be employed to modify the active set of the communication between UE
`and UTRAN. The procedure may comprise three functions: radio link addition, radio link
`removal and combined radio link addition and removal. The maximum numberof
`
`simultaneous radio links is set to eight. New radio links are added to the active set once
`the pilot signal strengths of respective base stations exceed certain threshold relative to
`the pilot signal of the strongest memberwithin active set.
`
`10
`
`15
`
`A radiolink is removed from the active set oncethepilot signal strength of the respective
`
`basestation exceeds certain threshold relative to the strongest memberof the active set.
`Threshold for radio link addition is typically chosen to be higherthan that for the radio link
`deletion. Hence, addition and removal events form a hysteresis with respect to pilot
`signal strengths.
`
`Pilot signal measurements may be reported to the network (e.g to S-RNC) from UE by
`means of RRC signaling. Before sending measurementresults, somefiltering is usually
`performed to average out the fast fading. Typicalfiltering duration may be about 200 ms
`contributing to handover delay. Based on measurementresults, the network (e.g. S-
`RNC) may decide to trigger the execution of one of the functions of active set update
`procedure (addition / removal of a Node B to / from current Active Set).
`
`20
`
`E-DCH — Node B controlled scheduling
`
`Node 8B controlled scheduling is one of the technical features for E-DCH which is
`foreseen to enable more efficient use of the uplink power resource in order to provide a
`higher cell throughput in the uplink and to increase the coverage. The term “Node B
`controlled scheduling” denotes the possibility for the Node B to control, within the limits
`set by the RNC, the set of TFCs from which the UE may choosea suitable TFC. The set
`of TFCs from which the UE may choose autonomously a TFCis in the following referred
`
`to as “Node B controlled TFC subset”.
`
`The “Node B controlled TFC subset” is a subset of the TFCS configured by RNC as seen
`in Fig. 8. The UE selects a suitable TFC from the “Node B controlled TFC subset”
`employing the Rel5 TFC selection algorithm. Any TFC in the "Node B controlled TFC
`subset” might be selected by the UE, provided there is sufficient power margin, sufficient
`data available and TFC is not in the blocked state. Two fundamental approaches to
`
`25
`
`30
`
`Ex.1007 / Page 10 of 59
`
`Ex.1007 / Page 10 of 59Ex.1007 / Page 10 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`scheduling UE transmission for the E-DCH exist. The scheduling schemes canail be
`viewed as management of the TFC selection in the UE and mainly differs in how the
`Node B caninfluence this process and the associated signaling requirements.
`
`Node B controlled Rate Scheduling
`
`The principle of this scheduling approach is to allow Node B to contro! and restrict the
`transport format combination selection of the user equipment by fast TFCS restriction
`control. A Node B may expand/reduce the “Node B controlled subset”, which user
`equipment can choose autonomously on suitable transport format combination from, by
`Layer-1 signaling.
`In Node B controlled rate scheduling ali uplink transmissions may
`occurin paralle| but at a rate low enough such that the noiserise threshold at the Node B
`is not exceeded. Hence, transmissions from different user equipments may overlap in
`time. With Rate scheduling a Node B canonlyrestrict the uplink TFCS but does not have
`any control of the time when UEsare transmitting data on the E-DCH. Due to Node B
`being unaware of the numberof UEstransmitting at the same time no precise control of
`the uplink noise rise in the cell may be possible (see 3GPP TR 25.896: "Feasibility study
`for Enhanced Uplink for UTRA FDD (Release 6)", version 1.0.0, available at
`
`http:/Awww.3gpp.org).
`
`Two new Layer-1 messages are introduced in order to enable the transport format
`combination contro! by Layer-1 signaling between the Node B and the user equipment. A
`Rate Request (RR)may be sent in the uplink by the user equipmentto the Node B. With
`the RR the user equipment can request the Node B to expand/reduce the “Node
`controlled TFC Subset” by one step. Further, a Rate Grant (RG) may be sent in the
`downlink by the Node B to the user equipment. Using the RG, the Node B may change
`the “Node B controlled TFC Subset”, e.g. by sending up/down commands. The new
`
`10
`
`15
`
`20
`
`25
`
`“Node B controlled TFC Subset”is valid until the next timeit is updated.
`
`Node B controlled Rate and Time Scheduling
`
`The basic principle of Node B controlled time and rate scheduling is to allow
`(theoretically only) a subset of the user equipments to transmit at a given time, such that
`the desired total noise rise at the Node B is not exceeded. instead of sending up/down
`
`30
`
`commands to expand/reduce the “Node B controlled TFC Subset” by one step, a Node B
`may update the transport format combination subset to any allowed value through
`explicit signaling, e.g. by sending a TFCSindicator (which could be a pointer).
`
`Ex.1007 / Page 11 of 59
`
`Ex.1007 / Page 11 of 59Ex.1007 / Page 11 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`Furthermore, a Node B maysetthe start time and the validity period a user equipmentis
`allowed to transmit. Updates of the “Node B controlled TFC Subsets”for different user
`equipments may be coordinated by the scheduler in order to avoid transmissions from
`
`multiple user equipments overlapping in time to the extent possible.
`
`In the uplink of
`
`CDMAsystems, simultaneous transmissions always interfere with each other. Therefore
`
`by controlling the number of user equipments, transmitting simultaneously data on the E-
`
`DCH, Node B may have more precise control of the uplink interference level in the cell.
`
`The Node B scheduler may decide which user equipments are allowed to transmit and
`
`the corresponding TFCSindicator on a per transmission time interval (TT!) basis based
`on, for example, buffer status of the user equipment, power status of the user equipment
`
`10
`
`and available interference Rise over Thermal (RoT) margin at the Node B.
`
`15
`
`20
`
`25
`
`30
`
`Two new Layer-1 messagesare introduced in order to support Node B controlled time
`and rate scheduling. A Scheduling Information Update (S1) may be sentin the uplink by
`the user equipmentto the NodeB.If user equipmentfinds a need for sending scheduling
`request to Node B (for example new data occurs in user equipment buffer), a user
`equipment may transmit
`required scheduling information. With this
`scheduling
`information the user equipment provides Node B information on its status, for exampleits
`buffer occupancy andavailable transmit power.
`
`A Scheduling assignment (SA) may be transmitted in the downlink from a Node B to a
`user equipment. Upon receiving the scheduling request the Node B may schedule a user
`equipment based on the scheduling information (SI) and parameters like available RoT
`margin at the Node B. In the Scheduling Assignment (SA) the Node B may signal the
`TFCSindicator and subsequenttransmissionstart time and validity period to be used by
`the user equipment.
`
`Node B controlled time and rate scheduling provides a more precise RoT control
`compared to the rate-only controlled scheduling as already mentioned before. However
`this more precise control of the interference at this Node B is obtained at the cost of
`
`more signaling overhead and scheduling delay (scheduling request and scheduling
`assignment messages) compared to rate control scheduling.
`
`In Fig. 9 a general scheduling procedure with Node B controlled time and rate scheduling
`is shown. When a user equipment wants to be scheduled for transmission of data on E-
`DCHit first sends a scheduling request to Node B. Tpop denotes here the propagation
`time on the air interface. The contents of this scheduling request are information
`
`10
`
`Ex.1007 / Page 12 of 59
`
`Ex.1007 / Page 12 of 59Ex.1007 / Page 12 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`(scheduling information) for example buffer status and power status of the user
`
`the Node B may process the
`equipment. Upon receiving that scheduling request,
`obtained information and determine the scheduling assignment. The scheduling will
`require the processing time Tschedule-
`
`The scheduling assignment, which comprises the TFCS indicator and the corresponding
`
`transmission start time and validity period, may be then transmitted in the downlink to the
`
`user equipment. After receiving the scheduling assignment the user equipmentwill start
`
`transmission on E-DCHin the assigned transmissiontimeinterval.
`
`The use of either rate scheduling or time and rate scheduling may be restricted by the
`available power as the E-DCHwill have to co-exist with a mix of other transmissions by
`the user equipments in the uplink. The co-existence of the different scheduling modes
`may provide flexibility in serving different traffic types. For example, traffic with small
`amount of data and/or higher priority such as TCP ACK/NACK maybesent using only a
`
`rate control mode with autonomous transmissions compared to using time and rate-
`
`15
`
`control scheduling. The former would involve lower
`
`latency and lower signaling
`
`overhead.
`
`Radio Link Control Protocol (RLC)
`
`In the following the operation of the RLC protocol layer will be briefly summarized.It
`
`should be noted that the level of details in this and all paragraphs referring to RLC
`
`20
`
`protocol is kept only to an extent sufficient to provide an understanding of the description
`
`of the presentinvention.
`
`The radio link control protocol
`is the layer two protocol used in 3G UMTScellular
`systemsfor flow control and error recovery for both user and control data. There are
`three operational modes for RLC in UMTS: transparent mode (TM), unacknowledged
`mode (UM) and acknowledged mode (AM). Each RLC entity is configured by RRC to
`
`25
`
`operate in one of these modes (see 3GPP TS 25.322, "Radio Access Network; Radio
`
`Link Control
`
`(RLC) protocol specification; (Release 6)’, version 6.0.0, available at
`
`http:/Awww.3gpp.org).
`
`The service the RLC layer provides in the control plane is called Signaling Radio Bearer
`
`30
`
`(SRB).
`In the user plane, the service provided by RLC layer is called a Radio Bearer
`(RB) only if the PDCP (Packet Data Convergence Protocol) and BMC (Broadcast
`
`11
`
`Ex.1007 / Page 13 of 59
`
`Ex.1007 / Page 13 of 59Ex.1007 / Page 13 of 59
`TESLA, INC.
`
`TESLA, INC.TESLA, INC.
`
`

`

`WO 2005/125252
`
`PCT/EP2005/006361
`
`Multicast Control) protocols are not used by that service. Otherwise the RB service is
`
`provided by PDCP or BMC.
`
`In transparent mode no protocol overhead is added to RLC SDUs (Service Data Units)
`received from higher layer through TM-SAP (Transparent Mode-Service Access Point).
`
`In special cases transmission with limited segmentation/reassembly capability may be
`accomplished.
`It may be negotiated in the radio bearer setup procedure, whether
`
`segmentation/reassembly is used. The transparent modeis mainly used for very delay-
`sensitive services like speech.
`
`In unacknowledged modedata delivery may not be guaranteed si

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket