Exhibit 1006.09
`
`ZTE Corporation and ZTE (USA) Inc.
`
`

`
`TS
`
`v2.3.0 (1999-06)
`
`Technical Specification
`
`3"’ Generation Partnership Project (3GPP);
`Technical Specification Group (TSG) RAN;
`Working Group 2 (WG2);
`
`Services provided by the Physical Layer
`
`The present document has been developed within the 3” Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of
`3GPPi
`The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
`Specification.
`Specifications and reports for iniplenientation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners‘ Publications Offices.
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09—00001
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`Reference
`
`<Workitem> (<ShortfI|ename>.PDF)
`
`Keywords
`Digital cellular telecommunications system,
`Universal Mobile Telecommunication System
`(UMTS), UTRA, IMT—2000
`
`3GPP
`
`Postal address
`
`Office address
`
`Internet
`
`secretariat@3gpp.org
`Individual copies ofthis deliverable
`can be downloaded from
`http://www.3gpp.org
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`1 Contents
`
`3.1
`
`Definitions
`
`3.2 Abbreviations
`
`4.1
`
`4.2
`
`5.1
`
`5.2
`
`5.3
`
`6.1
`
`6.2
`
`Interface to MAC
`
`Interface to RRC
`
`General
`
`Overview of L1 functions
`
`L1 interactions with L2 retransmission functionality
`
`Uplink models
`
`Downlink models
`
`6.3
`
`Relay link Model
`
`General concepts about Transport Channels
`Transport Block
`7.1.2
`Transport Block Set
`Transport Block Size
`Transport Block Set Size
`Transmission Time interval
`
`Transport Format
`Transport Format Set
`Transport Format Combination
`Transport Format Combination Set
`Transport Format Indicator (TFI)
`Transport Format Combination Indicator (TFCI)
`
`Types of Transport Channels
`
`Slotted Mode
`
`8.1
`
`8.2
`
`Uplink
`
`Downlink
`
`9.1 Measured time difference to cell
`
`9.2
`
`9.3
`
`9.4
`
`9.5
`
`9.6
`
`9.7
`
`9.8
`
`9.9
`
`Primary CCPCH DL TX power
`
`UL load
`
`Path loss
`
`Primary CCPCI-I RX EC/In
`
`Primary CCPCH RX SIR (RSCP/ISCP)
`
`Primary CCPCH RX power (RSCP)
`
`E./10
`
`SIR
`
`9.10 Received signal code power (RSCP)
`
`9.11 Signal strength
`
`9.12 DL Transport CI-I BLER
`
`9.13 DL Transport CH BER
`
`9.14
`
`LIE Transmission Power
`
`3GPP
`
`

`
`9.15 Parameters for UE Positioning
`
`10.1 Generic names of primitives between layers 1 and 2
`10.1.1
`PHY-CONNECT
`10.1.2
`PHY-DISCONNECT
`10.1.3
`PHY-DATA
`10.1.4
`PHY-STATUS
`
`10.2 Generic names of primitives between layers 1 and 3
`10.2.1
`STATUS PR1M1T1VES
`10.2.2
`CONTROL PRIMITIVES
`
`10.3 Parameter definition
`
`10.3.1
`10.3.2
`1033
`
`1034
`10.3.5
`
`Received transmission quality parameters
`Radio link to be reported
`Error code
`
`Physical channel description
`Action
`
`11.1 Downlink Frame format
`
`11.2 Uplink Frame format
`
`11.3 Order of bit transmission
`
`TS 25.302 V2.3.0 (1999-06)
`
`21
`
`21
`21
`21
`22
`22
`
`22
`22
`23
`
`24
`
`24
`24
`24
`
`24
`24
`
`25
`
`25
`
`25
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00004
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`Intellectual Property Rights
`
`Foreword
`
`This Technical Specification has been produced by the 3Gl’P.
`The contents of the present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents ofthis TS, it will be re-released by the TSG with an identifying
`change of release date and an increase in version number as follows:
`Version 3.y.z
`where:
`
`x the first digit:
`l
`presented to TSG for information;
`2 presented to TSG for approval;
`3
`Indicates TSG approved document under change control.
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
`updates, etc.
`the third digit is incremented when editorial only changes have been incorporated in the specification.
`
`1 Scope
`The present document is a technical specification ofthe services provided by the physical layer of UTRA to upper
`layers.
`
`2 References
`References may be made to:
`a) specific versions of publications (identified by date ofpublication, edition number, version number, etc.), in
`which case, subsequent revisions to the referenced document do not apply;
`b) all versions up to and including the identified version (identified by “up to and including“ before the version
`identity);
`c) all versions subsequent to and including the identified version (identified by "onwards“ following the version
`identity); or
`d) publications without mention of a specific version, in which case the latest version applies.
`A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
`number.
`
`ETSI UMTS 23.10 : UMTS Access Stratum Services and Functions
`3GPP TS 25.301 : Radio Interface Protocol Architecture
`
`3GPP TS 252i 2 : UTRA FDD multiplexing, channel coding and interleaving description
`3GPP TS 25.222 : UTRA TDD multiplexing, channel coding and interleaving description
`
`1
`2
`
`3
`4
`
`I l [ l
`
`3 Definitions and Abbreviations
`
`3.1 Definitions
`See [3] for a definition of fundamental concepts and vocabulary.
`
`3.2 Abbreviations
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00005
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`Automatic Repeat Request
`Broadcast Control Channel
`Broadcast Channel
`Control-
`Call Control
`Common Control Channel
`Control Channel
`
`Coded Composite Transport Channel
`Core Network
`
`Cyclic Redundancy Check
`Dedicated Control (SAP)
`Dynamic Channel Allocation
`Dedicated Control Channel
`Dedicated Channel
`Downlink
`Drift Radio Network Controller
`Dovvnlink Shared Channel
`Dedicated Traffic Channel
`Forward Link Access Channel
`
`FAUSCH
`FCS
`FDD
`GC
`HO
`
`Fast Uplink Signaling Channel
`Frame Check Sequence
`Frequency Division Duplex
`General Control (SAP)
`Handover
`International Telecommunication Union
`
`kilo-bits per second
`Layer 1 (physical layer)
`Layer 2 (data link layer)
`Layer 3 (network layer)
`Link Access Control
`
`Location Area Identity
`Medium Access Control
`
`Mobility Management
`Notification (SAP)
`ODMA Common Control Channel
`ODMA Dedicated Control Channel
`ODMA Dedicated Channel
`
`Opportunity Driven Multiple Access
`ODMA Random Access Channel
`ODMA Dedicated Traffic Channel
`
`Paging Control Channel
`Paging Channel
`Protocol Data Unit
`
`Physical layer
`Physical Channels
`Random Access Channel
`Radio Link Control
`Radio Network Controller
`
`Radio Network Subsystem
`Radio Network Temporaiy Identity
`Radio Resource Control
`Service Access Point
`
`Synchronization Control Channel
`Synchronization Channel
`Service Data Unit
`
`Serving Radio Network Controller
`Serving Radio Network Subsystem
`Traffic Channel
`
`Time Division Duplex
`Transport Format Combination Indicator
`Transport Format Indicator
`
`Z-TE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00006
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`Temporaiy Mobile Subscriber Identity
`Transmit Power Control
`User-
`
`User Equipment
`User Equipment with ODMA relay operation enabled
`Uplink
`Universal Mobile Telecommunications System
`UTRAN Registration Area
`UMTS Terrestrial Radio Access
`UMTS Terrestrial Radio Access Network
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00007
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`4 Interfaces to the physical layer
`The physical layer (layer 1) is the lowest layer in the OSI Reference Model and it supports all functions required for the
`transmission of bit streams on the physical medium.
`The physical layer interfaces the Medium Access Control (MAC) Layer and the Radio Resource Control (RRC) Layer
`as depicted in figure 2.1.
`
`La}/GI3
`
`R i R
`adio
`
`l RR .,
`,
`esource Contro (
`C)
`C
`
`Medium Access Control
`
`(M ‘ C)
`C
`
`CPHY primitives
`
`Pl-[Y prifnitjves
`
`C
`
`p
`Physical Layer
`
`C
`
`Figure 1 : Interfaces with the Physical Layer
`
`4.1 Interface to MAC
`The physical layer interfaces the MAC entity oflayer 2.. Communication between the Physical Layer and MAC is in
`an abstract way performed by means of PHY-primitives defined which do not constrain implementations.
`NOTE:
`The terms physical layer and layer l, will be used synonymously in this description.
`The PHY-primitives exchanged between the physical layer and the data link layer provide the following functions:
`I
`transfer of transport blocks over the radio interface
`I
`indicate the status of the layer 1 to layer 2
`
`4.2 Interface to RRC
`The physical layer interfaces the RRC entity of layer 3 in the UE and in the network.
`
`Communication is performed in an abstract way by means of CPHY-primitives. They do not constrain
`implementations.
`
`The CPHY-primitives exchanged between the physical layer and the Network layer provide the following function:
`
`0
`
`control of the configuration of the physical layer
`
`The currently identified exchange of information across that interface have only a local significance to the UE or
`Network.
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00008
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`5 Services and functions of the physical layer
`
`5.1 General
`The physical layer offers data transport services to higher layers. The access to these services is through the use of
`transport channels via the MAC sub-layer. The characteristics ofa transport channel are defined by its transport format
`(or format set), specifying the physical layer processing to be applied to the transport channel in question, such as inner
`channel coding and interleaving, and any service-specific rate matching as needed.
`
`The physical layer operates exactly according to the Ll radio frame timing. A transport block is defined as the data
`accepted by the physical layer to be jointly encoded. The transmission block timing is then tied exactly to this Ll frame
`timing, e.g. every transmission block is generated precisely every lOms, or a multiple of l0 ms.
`
`A UE can set up multiple transport channels simultaneously, each having own transport characteristics (eg. offering
`different error correction capability). Each transport channel can be used for information stream transfer of one radio
`bearer or for layer 2 and higher layer signalling messages.
`
`The multiplexing ofthese transport channels onto the same or different physical channels is carried out by Ll. In
`addition, the Transport Format Combination Indication field (TFCI) shall uniquely identify the transport format used by
`each transport channel of the Coded Composite Transport Channel within the current radio frame.
`
`5.2 Overview of L1 functions
`The physical layer performs the following main functions:
`
`FEC encoding/decoding oftransport channels
`
`Measurements and indication to higher layers (e.g. FER, SIR, interference power, transmission power, etc...)
`
`Macrodiversity distribution/combining and soft handover execution
`
`Error detection on transport channels
`
`Multiplexing of transport channels and demultiplexing of coded composite transport channels
`
`Rate matching
`
`Mapping of coded composite transport channels on physical channels
`
`Modulation and spreading/demodulation and despreading of physical channels
`
`Frequency and time (chip, bit, slot, frame) synchronization
`
`Closed-loop power control
`
`Power weighting and combining of physical channels
`
`RF processing
`
`5.3 L1 interactions with L2 retransmission functionality
`Provided that the RLC PDUs are mapped one-to-one onto the Transport Blocks, Error indication may be provided by
`Ll to L2. For that purpose, the Ll CRC can be used for individual error indication of each RLC PDU. The Ll CRC
`will then serve multiple purposes:
`0 Error indication for uplink macro diversity selection combining (Li)
`I Frame error indication for speech services
`I Quality indication
`0 Error indication for L2 retransmissions
`
`As a conclusion, Ll needs to give an error indication to L2 for each erroneous Transport Block delivered.
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00009
`
`

`
`10
`
`TS 25.302 V2.3.0 (1999-06)
`
`6 Model of physical layer of the UE
`
`6.1 Uplink models
`Figure 2 shows models of the UE’s physical layer in the uplink for both FDD and TDD mode. It shows two models:
`DCH model and RACH model. Only one type of transport channel is used at a time by one UE. Hence, both models are
`not in use simultaneously within one UE. More details can be found in [3] and [4].
`
`Editors note.‘ Models for uplink transport channels currently markedfis will be necessary iflhese channels are
`included in the description.
`
`DCH model
`
`DCH DCH DCH
`
`FAUSCH model
`
`RACH model
`
`FAUSCH
`
`RACH
`
`multiplexing
`
`
`Transport
`Format Combination
`
`InEjTi::a(t%
`
`Coded Composite
`ransport Channel
`(CCTrCH)
`
`:rt1ti1fltiplexmg/
`
`
`
`_
`
`Physical Channe
`V
`Data Streams
`- TPC
`
`Coding and
`
`CPCHinodd
`
`CPCH
`
`CPCH (Note 1)
`
`Coding and
`multiplexing
`
`Coded Composite
`ransport Channel
`(CC'l‘rCH)
`
`Demultiplexing
`s o littin
`
`
`
`
`Physical Channel
`Data streams _N°te 2)
`
`Note 1: The need to multiplex several CPCH transport channels is FFS
`Note 2: Only the data part of the CPCH can be mapped on multiple physical channels
`
`Figure 2: Model ofthe UE’s physical layer — uplink
`
`The DCH model shows that one or several DCHs can be processed and multiplexed together by the same coding and
`multiplexing unit. The detailed functions ofthe coding and multiplexing unit are not defined in this document but in [3]
`
`3GPP
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09—00010
`
`

`
`11
`
`TS 25.302 V2.3.0 (1999-06)
`
`and [4]. The single output data stream from the coding and multiplexing unit is denoted Coded Composite Transport
`Channel (CCTrCH).
`
`The bits on a CCTrCH Data Stream can be mapped on the same Physical Channel and should have the same C/I
`requirement.
`
`On the downlink, multiple CCTrCH can be used simultaneously with one UE. In the case of FDD, only one fast power
`control loop is necessaiy for these different CCtrCH, but the different CCtrCH can have different C/I requirements to
`provide different QoS on the mapped Transport Channels. In the case of TDD, different power control loops can be
`applied for different CCTrCH. One physical channel can only have bits coming from the same CCTrCH.
`
`On the uplink and in the case of FDD, only one CCTrCH can be used simultaneously. On the uplink and in the case of
`TDD, multiple CCTrCH can be used simultaneously.
`
`When multiple CCTrCH are used by one UE, one or several TFCI can be used, but each CCTrCH has only zero or one
`corresponding TFCI. In the case of FDD, these different words are mapped on the same DPCCH. In the case of TDD,
`these different TFCI can be mapped on different DPCCH.
`
`The data stream ofthe CCTrCH is fed to a data demultiplexing/splitting unit that demultiplexes/splits the CCTrCH’s
`data stream onto one or several Physical Channel Data Streams.
`
`Editors '5 note: The term "'splitting" usedfor above fitnction in FDD mode has been replaced by
`”demultiplexing/splitting”. The intention ofusing the term splitting is to express that this function is performed on bit
`level not on some block level. The term demultiplexing/‘splitting shall cover both cases, block or bit level
`denmltiplexing, where block lengths larger than I bit may be applied in the TDD mode. This needs to be confirmed by
`the L1 group
`
`The current configuration of the coding and multiplexing unit is either signalled to, or optionally blindly detected by,
`the network for each l0 ms frame. If the configuration is signalled, it is represented by the Transport Format
`Combination Indicator (TFCI) bits. Note that the TFCI signalling only consists of pointing out the current transport
`format combination within the already configured transport format combination set. In the uplink there is only one
`TFCI representing the current transport formats on all DCHs of one CCTrCH simultaneously. In FDD mode, the
`physical channel data stream canying the TFCI is mapped onto the physical channel carrying the power control bits and
`the pilot.
`
`For the FAUSCH, there is no coding, since the FAUSCH is only used for the transmission of a reservation request by
`sending an up-link signalling code (USC) at the time-offset allocated for the specific UE during the lO ms frame. Due
`to the fixed time-offset allotted to a specific UE, the FAUSCH is a dedicated control channel.
`
`The model for the RACH case shows that RACH is a common type transport channel in the uplink. RACHs are always
`mapped one-to-one onto physical channels, i.e. there is no physical layer multiplexing of RACH. Service multiplexing
`is handled by the MAC layer. The CPCH which is another common type transport channel has a physical layer model
`as shown in the above figure.
`
`6.2 Downlink models
`Figure 3 and Figure 4 show the model of the UE’s physical layer for the downlink in FDD and TDD mode,
`respectively. Note that there is a different model for each transport channel type.
`
`Editors note: Models for downlink transport channels currently markedfis will be necessary if these channels are
`included in the description.
`
`

`
`12
`
`TS 25.302 V2.3.0 (1999-06)
`
`FACH
`model
`
`FACH
`
`PCH
`model
`
`BCH
`model
`
`DCH
`model
`
`PCH
`
`BCH
`
`DCH DCH DCH
`
`Decoding and
`
`demultiplexing
`
`Coded Composite
`Transport Channel
`(CCTrCH)
`
`
`
`Physical Channel
`Data Streams
`
` Cell 1
`
`Cell 2
`Cell 3
`
`—>TPC stream 1, TFCI
`
`—>TPC stream 2, TFCI
`—>TPC stream 3, TFCI
`
`
`
`:
`:
`
`:
`:
`
`Figure 3: Model ofthe UE’s physical layer — downlink FDD mode
`
`FACH
`model
`
`FACH
`
`PCH
`model
`
`BCH
`model
`
`DCH
`model
`
`PCH
`
`BCH
`
`DCH DCH DCH
`
`Decoding and
`
`demultiplexing
`
`Coded Composite
`Transport Channel
`(CCTrCH)
`
`
`
`Physical Channel
`Data Streams
`
`Decoding
`
`Figure 4: Model of the UE’s physical layer— downlink TDD mode
`
`For the DCH case, the mapping between DCHs and physical channel data streams works in the same way as for the
`uplink. Note however, that the number of DCHs, the coding and multiplexing etc. may be different in uplink and
`downlink.
`
`In the FDD mode, the differences are mainly due to the soft and softer handover. Further, the pilot, TPC bits and TFCI
`are time multiplexed onto the same physical channel(s) as the DCHs. Further, the definition of physical channel data
`stream is somewhat different from the uplink
`
`Note that it is logically one and the same physical data stream in the active set of cells, even though physically there is
`one stream for each cell‘ The same processing and multiplexing is done in each cell. The only difference between the
`cells is the actual codes, and these codes correspond to the same spreading factor.
`
`3GPP
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09—00012
`
`

`
`13
`
`TS 25.302 V2.3.0 (1999-06)
`
`The physical channels carrying the same physical channel data stream are combined in the UE receiver, excluding the
`pilot, and in some cases the TPC bits. TPC bits received on certain physical channels may be combined provided that
`UTRAN has informed the UE that the TPC information on these channels is identical.
`
`The downlink models for the BCH, PCH and FACH show that BCH, PCH and FACH are always mapped one-to-one
`onto physical channels, ie. there is no physical layer multiplexing of BCH, PCH and FACH. Service multiplexing is
`handled by the MAC layer. Note, in the TDD mode there is the SCH in addition (not shown in Figure 4).
`
`6.3 Relay link Model
`The Relay link applies to the TDD mode only. The applicability to the FDD mode is FFS.
`
`Figure 4 illustrates the model of the UE’s physical layer for the TDD mode.
`
`ODCH model
`
`ORACHmodel
`
`ODCH
`
`ORACH
`
`
`
`Figure 5 : Model ofthe UE’s physical layer - relay link TDD mode.
`
`The ORACH is a channel used within UE’s to transmit and receive probing messages, and also to transmit and receive
`small packets of information. The ODCH is used to transmit larger amounts of data over a number of hops between
`UE’s.
`
`7 Formats and configurations for L1 data transfer
`
`7.1 General concepts about Transport Channels
`Layer 2 is responsible for the mapping of data onto Ll via the Ll/L2 interface that is formed by the transport channels.
`In order to describe how the mapping is performed and how it is controlled, some definitions and terms are required.
`The required definitions are given in the following sections. Note that the definitions are generic for all transport
`channel types, ie. not only for DCHs.
`
`All Transport Channels are defined as unidirectional (i.e. uplink, downlink, or relay-link). This means that a UE can
`have simultaneously (depending on the services and the state of the UE) one or several transport channels in the
`downlink, and one or more Transport Channel in the uplink.
`
`7.1.1 Transport Block
`This is the basic unit exchanged between L1 and MAC, for L1 processing.
`
`A Transport Block typically corresponds to an RLC PDU or corresponding unit. In the TDD mode it may possibly also
`be formed by a MAC peer-to-peer message. Layer 1 adds a CRC for each Transport Block.
`
`3GPP
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09—00013
`
`

`
`7.1.2Transport Block Set
`This is defined as a set of Transport Blocks which are exchanged between Ll and MAC at the same time instance using
`the same transport channel.
`
`TS 25.302 V2.3.0 (1999-06)
`
`7.1.3Transport Block Size
`This is defined as the number of bits in a Transport Block.
`
`7.1.4 Transport Block Set Size
`This is defined as the number of bits in a Transport Block Set.
`
`7.1 .5Transmission Time Interval
`This is defined as the inter-arrival time of Transport Block Sets, and is equal to the periodicity at which a Transport
`Block Set is transferred by the physical layer on the radio interface. It is always a multiple ofthe minimum interleaving
`period (eg. 10ms, the length of one Radio Frame). The MAC delivers one Transport Block Set to the physical layer
`every TTI.
`
`Figure 6 shows an example where Transport Block Sets, at certain time instances, are exchanged between MAC and L1
`via three parallel transport channels. Each Transport Block Set consists of a number of Transport Blocks. The
`Transmission Time Interval, ie. the time between consecutive deliveries of data between MAC and Ll, is also
`illustrated. Last, the case when the last Transport Block is smaller than the allowed size is shown, with the topmost
`Transport Block being partially empty.
`
`DCHI
`
`Transport Block
`
`TTWSPWT B1991‘
`
` TI’aI1sn1issit3I1 Time Interval
`
`DCH2
`
` 'l'ransmission Time intervalT
`
`DCH3
`
`‘M ‘_Ti‘aI1s1nissioIi
`Time Interval
`
`Transv°rtB1°°k
`
`Figure 6. Exchange of data between MAC and L1
`
`7.1.6Transport Format
`This is defined as a format offered by L1 to MAC (and vice versa) for the delivery ofa Transport Block Set during a
`Transmission Time Interval on a Transport Channel. The Transport Format constitutes of two parts — one dynamic part
`and one semi-static part.
`
`Attributes of the dynamic part are:
`- Transport Block Size
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00014
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`- Transport Block Set Size
`0 Transmission Time Interval (optional dynamic attribute for TDD only)
`
`Attributes of the semi-static part are:
`I Transmission Time Interval (mandatory for FDD, optional for the dynamic part of TDD NRT bearers)
`0 Error protection scheme to apply
`0 Type of error protection e.g. Turbo Code, Convolutionnal Code
`0
`convolutional code ratio
`
`0 Resulting code ratio after static rate matching
`Size of CRC
`
`0
`
`In the following example, the Transmission time Interval is seen as a semi-static part
`Example:
`0 Dynamic part: {320 bits, 640 bits}, Semi-static pait: {I0ms, Inner coding only, repeat 1/12 ofthe bits}
`
`7.1 .7Transport Format Set
`This is defined as the set ofTranspoit Formats associated to a Transpoit Channel.
`
`The semi-static parts of all Transport Formats are the same within a Transport Format Set.
`
`Effectively the first two attributes of the dynamic part form the instantaneous bit rate on the Transport Channel.
`Variable bit rate on a Transport Channel may, depending on the type of service which is mapped onto the transport
`channel, be achieved by changing between each Transmission Time Interval one of the following:
`1.
`the Transpoit Block Size only
`2.
`the Transport Block Set Size only
`3. both the Transport Block Size and the Transport Block Set Size
`
`Example I:
`0 Dynamic part: {.20 bits, 20 bits}, {40 bits, 40 bits}; {SO bits, 80 bits}; {I60 bits, I60 bits}
`I Semi-static part: {I Oms, Inner coding only, repeat 1/1 2 of the bits}
`
`Example 2:
`0 Dynamic part: (320 bits, 320 bits}, (320 bits, 640 bits}, (320 bits, I280 bits}
`I Semi-static part: {I0ms, Inner coding only, repeat I/I2 ofthe bits}
`
`The first example may correspond to a Transport Channel carrying a speech service, requiring blocks delivered on a
`constant time basis. In the second example, which illustrates the situation where a non-real time service is carried by the
`Transport Channel, the number of blocks delivered per Transmission Time Interval varies between the different
`Transport Formats within the Transport Format Set. Referring to Figure 6, the Transport Block Size is varied on DCHI
`whereas the Transport Block Set Size is fix. That is, a Transport Format Set where the dynamic part has a variable
`Transport Block Size has been assigned for DCHI. On DCH2 and DCH3 it is instead the Transport Block Set Sizes that
`are varied. That is, the dynamic parts of the corresponding Transport Format Sets include variable Transport Block Set
`Sizes.
`
`7.1.8 Transport Format Combination
`The layer 1 multiplexes one or several Transport Channels, and for each Transport Channel, there exists a list of
`transport formats (Transport Format Set) which are applicable. Nevertheless, at a given point of time, not all
`combinations may be submitted to layer 1 but only a subset, the Transport Format Combination. This is defined as an
`authorised combination of the combination of currently valid Transport Formats that can be submitted simultaneously
`to the layer I for transmission on a Coded Composite Transport Channel of a UE, i.e. containing one Transport Format
`from each Transport Channel.
`
`Example:
`
`DCHI: Dynamic part: {2O bits, 20 bits}, Semi-static part: {IOms, Inner coding only, repeat I/12 ofthe bits}
`DCH2: Dynamic part: {32O bits, 1280 bits}, Semi-static part: { lOms, Inner coding only, puncture I/14 ofthe bits}
`DCH3: Dynamic part: {32O bits, 320 bits}, Semi-static part: {40ms, Outer coding, repeat I/20 ofthe bits}
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00015
`
`

`
`16
`
`TS 25.302 V2.3.0 (1999-06)
`
`7.1.9 Transport Format Combination Set
`This is defined as a set of Transport Format Combinations on a Coded Composite Transport Channel.
`
`Example:
`
`Dynamic part:
`
`Combination I: DCHI: {Z0 bits, 20 bits}, DCH2: {320 bits, 1280 bits}, DCH3: {320 bits, 320 bits}
`Combination 2: DCHI: {4O bits, 40 bits}, DCH2: {32O bits, I280 bits}, DCH3: {320 bits, 320 bits}
`Combination 3: DCHI: {I60 bits, 160 bits}, DCH2: {32o bits, 320 bits}, DCH3: {32o bits, 320 bits}
`
`Semi-static part:
`
`DCHI: {lOms, Inner coding only, repeat l/12 ofthe bits}
`DCH2: { lOms, Inner coding only, puncture 1/14 of the bits}
`DCH3: {40ms, Outer coding, repeat 1/20 of thebits}
`
`The Transport Format Combination Set is what is given to MAC for control. However, the assignment of the Transport
`Format Combination Set is done by L3. When mapping data onto Ll, MAC chooses between the different Transport
`Format Combinations given in the Transport Format Combination Set. Since it is only the dynamic part that differ
`between the Transport format Combinations, it is in fact only the dynamic part that MAC has any control over.
`
`The semi-static part, together with the target value for the L1 closed loop power control, correspond to the service
`attributes:
`
`0 Quality (e.g. BER)
`0 Transfer delay
`
`These service attributes are then offered by Ll . However, it is L3 that guarantees that the Li services are fulfilled since
`it is in charge of controlling the L1 configuration, ie. the setting of the semi-static part of the Transport Formats.
`Furthermore, L3 controls the target for the L1 closed loop power control through the outer loop power control (which
`actually is a quality control rather than a power control).
`
`Note that a Transport Format Combination Set need not contain all possible Transport Format Combinations that can be
`formed by Transport Format Sets of the corresponding Transport Channels. It is only the allowed combinations that are
`included. Thereby a maximum total bit rate of all transport channels ofa Code Composite Transport Channel can be set
`appropriately. That can be achieved by only allowing Transport Format Combinations for which the included Transport
`Formats (one for each Transport Channel) do not correspond to high bit rates simultaneously.
`
`The selection of Transport Format Combinations can be seen as a fast part of the radio resource control. The dedication
`of these fast parts of the radio resource control to MAC, close to L1, means that the flexible variable rate scheme
`provided by Ll can be fully utilised. These parts of the radio resource control should be distinguished from the slower
`parts, which are handled by L3. Thereby the bit rate can be changed very fast, without any need for L3 signalling.
`
`Transport Format Indicator (TFI)
`7.1.10
`The TFI is a label for a specific transport format within a transport format set. It is used in the inter-layer
`communication between MAC and LI each time a transport block set is exchanged between the two layers on a
`transport channel.
`
`Transport Format Combination Indicator (TFCI)
`7.1.11
`This is a representation of the current Tran sport Format Combination.
`
`There is a one-to-one correspondence between a certain value of the TFCI and a certain Transport Format
`Combination. The TFCI is used in order to inform the receiving side of the currently valid Transport Format
`Combination, and hence how to decode, de-multiplex and deliver the received data on the appropriate Transport
`Channels.
`
`MAC indicates the TFI to Layer 1 at each delivery of Transport Block Sets on each Transport Channel. Layer 1 then
`builds the TFCI from the TFIs of all parallel transport channels of the UE , processes the Transport Blocks
`appropriately and appends the TFCI to the physical control signalling . Through the detection of the TFCI the receiving
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00016
`
`

`
`17
`
`TS 25.302 V2.3.0 (1999-06)
`
`side is able to identify the Transport Format Combination. For FDD, in case of limited Transport Format Combination
`Sets the TFCI signalling may be omitted, instead relying on blind detection. Nevertheless, from the assigned Transport
`Format Combinations, the receiving side has all information it needs in order to decode the information and transfer it
`to MAC on the appropriate Transport Channels.
`
`The multiplexing and exact rate matching patterns follow predefined rules and may therefore be derived (given the
`Transport Format Combinations) by transmitter and receiver without signalling over the radio interface.
`
`When the meaning of the TFCI field needs to be reconfigured, two procedures can be used depending on the level of
`reconfiguration:
`
`0
`
`Complete reconfiguration of TFCI: In this procedure all TFCI values are reinitialized and new values
`are defined instead. The complete reconfiguration requires an explicit synchronization between the UE
`and UTRAN regarding when the reconfiguration becomes valid.
`
`Incremental reconfiguration of TFCI: In this procedures, a part of the TFCI Values before and after the
`reconfiguration remain identical (note that this must be true for at least a TFCI that carry the signaling
`connection). This procedure supports addition, removal or redefinition of TFCI values. This procedure
`does not require an explicit execution time. This procedure may imply the loss of some user-plane data.
`
`7.2 Types of Transport Channels
`A general classification of transport channels is into two groups:
`
`0
`
`0
`
`common channels and
`
`dedicated channels (where the UEs can be unambiguously identified by the physical channel, i.e. code and
`frequency)
`
`Common transport channel types are:
`
`1. Random Access Channel(s) (RACH) characterized by:
`
`0
`
`0
`
`0
`
`0
`
`existence in uplink only,
`
`limited data field. The exact number of allowed bits is FFS.
`
`collision risk,
`
`open loop power control,
`
`2. ODMA Random Access Channel(s) (ORACH) characterized by:
`
`used in TDD mode only (FDD is for FFS)
`
`existence in relay-link
`
`collision risk,
`
`open loop power control,
`
`no timing advance control
`
`3. Forward Access Channel(s) (FACH) characterized by:
`
`0
`
`existence in downlink only,
`
`possibility to use beam forming,
`
`possibility to use slow power control,
`
`possibility to change rate fast (each l0ms),
`
`lack of fast power control and
`
`4. Broadcast Channel (BCH) characterized by:
`
`I
`
`existence in downlink only,
`
`ZTE Corporation and ZTE (USA) Inc.
`
`Exhibit 1006.09-00017
`
`

`
`TS 25.302 V2.3.0 (1999-06)
`
`I
`
`I
`
`low fixed bit rate and
`
`requirement to be broadcast in the entire coverage area of the cell.
`
`5. Paging Channel (PCH) characterized by:
`
`I
`
`I
`
`I
`
`existence in downlink only,
`
`possibility for sleep mode procedures and
`
`requirement to be broadcast in the entire c