(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`
`(19) World Intellectual Property
`Organization
`International Bureau
`
`I lllll llllllll II llllll lllll lllll lllll llll I II Ill lllll lllll lllll 111111111111111111111111111111111
`
`( 43) International Publication Date
`8 July 2004 (08.07.2004)
`
`PCT
`
`(10) International Publication Number
`WO 2004/057896 Al
`
`(51) International Patent Classification7:
`H04L 12/56
`
`H04Q 7/38,
`
`(21) International Application Number:
`PCT /EP2003/0143 24
`
`(22) International Filing Date:
`16 December 2003 (16.12.2003)
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`English
`
`English
`
`(30) Priority Data:
`02028630.8
`
`20 December 2002 (20.12.2002) EP
`
`(71) Applicant (for all designated States except US): MAT(cid:173)
`SUSHITA ELECTRIC INDUSTRIAL CO., LTD.
`[JP/JP]; 1006, Kadoma, Kadoma City, Osaka 571-8501
`(JP).
`
`(72) Inventors; and
`(75) Inventors/Applicants (for US only): SEIDEL, Eiko
`[DE/DE]; Moosbergstr. 97 a-b, 64285 Darmstadt (DE).
`PETROVIC, Dragan [YU/DE]; Am Kaiserschlag 15,
`64295 Darmstadt (DE).
`
`(74) Agent: KUHL, Dietmar; Griinecker, Kinkeldey, Stock(cid:173)
`mair & Schwanhausser, Maximilianstrasse 58, 80538
`Miinchen (DE).
`
`(81) Designated States (national): 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, Fl, GB, GD,
`GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, KP, KR,
`KZ, LC, LK, LR, LS, LT, LU, LV, MA, MD, MG, MK, MN,
`MW, MX, MZ, NI, NO, NZ, OM, PG, PH, PL, PT, RO, RU,
`SC, SD, SE, SG, SK, SL, SY, TJ, TM, TN, TR, TT, TZ, UA,
`UG, US, UZ, VC, VN, YU, ZA, ZM, ZW.
`
`(84) Designated States (regional): ARIPO patent (BW, GH,
`GM, KE, LS, MW, MZ, SD, SL, SZ, TZ, UG, ZM, ZW),
`
`[Continued on next page}
`
`---iiiiiiii
`
`iiiiiiii
`
`(57) Abstract: The present invention is related to communication systems compris(cid:173)
`ing transmitters and receivers in communication with one another using a control
`channel and a shared data channel for data transmission. To ensure secure data de(cid:173)
`livery to one or more legitimate receivers the present invention provides a transmitter
`which modifies the transmission data to be transmitted via said shared data channel
`in accordance with a receiver specific identifier, signals to said receiver via the con(cid:173)
`trol channel to receive said modified transmission data and transmits said modified
`transmission data over the shared data channel. The receiver monitors said control
`channel for an indication to receive transmission data which have been modified at
`the transmitter in accordance with a receiver specific identifier, receives said modi(cid:173)
`fied transmission data on said shared data channel and reconstructs said transmission
`data from said modified transmission data in accordance with said receiver specific
`identifier.
`
`MAC-hs PDU
`
`CRC field calculation
`
`Bit scrambling
`
`Code block
`segmentation
`
`Channel coding
`
`Rate matching
`
`HybridARQ
`
`Interleaving
`
`Constellation
`rearrangement
`for 16QAM
`
`Physical channel
`mapping
`
`Physical channels
`
`User Equipment
`Identifier
`(UEID)
`
` Nokia v. IV II LLC
`Ex. 1009 / Page 1 of 41
`
`--!!!!!!!!
`iiiiiiii --
`--
`
`- !
`
`!!!!!!!
`iiiiiiii
`
`iiiiiiii ----
`
`

`

`WO 2004/057896 Al
`
`I lllll llllllll II llllll lllll lllll lllll llll I II Ill lllll lllll lllll 111111111111111111111111111111111
`
`Eurasian patent (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM),
`European patent (AT, BE, BG, CH, CY, CZ, DE, DK, EE,
`ES, Fl, FR, GB, GR, HU, IE, IT, LU, MC, NL, PT, RO, SE,
`SI, SK, TR), OAPI patent (BF, BJ, CF, CG, CI, CM, GA,
`GN, GQ, GW, ML, MR, NE, SN, TD, TG).
`
`Published:
`with international search report
`
`before the expiration of the time limit for amending the
`claims and to be republished in the event of receipt of
`amendments
`
`For two-letter codes and other abbreviations, refer to the "Guid(cid:173)
`ance Notes on Codes and Abbreviations" appearing at the begin(cid:173)
`ning of each regular issue of the PCT Gazette.
`
`Ex. 1009 / Page 2 of 41
`
`

`

`WO 2004/057896
`
`PCT/EP2003/014324
`
`Receiver Specific Data Manipulation in
`a Communication System
`
`The present invention is related to communication systems comprising transmitters and
`
`receivers in communication with one another using a control channel and a shared data
`
`5
`
`channel for data transmission.
`
`High Speed Downlink Packet Access (HSDPA) is a new technique that is standardized in
`
`UMTS Release 5. It shall provide higher data rates in the downlink by introducing en(cid:173)
`
`hancements at the air interface such as adaptive modulation and coding. HSDPA relies
`on Hybrid Automatic Repeat Request protocol (HARQ) Type 11/111, rapid selection of us-
`ers using shared channels and adaptation of transmission format parameters according
`
`10
`
`to the time varying channel conditions.
`
`The High Speed Downlink Shared Channel (HS-DSCH) is a high rate downlink transport
`
`channel for data transmission shared by several user equipments (UEs). The shared
`
`data channel (HS-DSCH) is transmitted over the entire cell or over parts of the cell using
`
`15
`
`e.g. beam-forming antennas. The shared data channel is associated with one downlink
`
`Dedicated Physical Channel (DPCH) to provide functions as transmitting pilot bits and
`transmit power control commands. Furthermore, there are one or several shared control
`
`channels (HS-SCCH). The shared control channel is a fixed rate downlink physical
`
`channel (e.g. 60 kbps, spreading factor SF=128) used to carry downlink signaling related
`to shared data channel transmissions. The signaling on the control channel is used to
`
`20
`
`indicate to a receiver that transmission data for the informed receiver are about to be
`
`send to it via the shared data channel. For each transmission time interval (TTI) in which
`data via the shared data channel are transmitted, each shared control channel carries
`
`shared data channel-related downlink signaling for one UE (e.g. used codes, modulation
`
`25
`
`scheme, transport block size). Only if the control channel information is received, the UE
`has the information to receive, despread and decode the shared data channel.
`
`There is a fixed time offset between the start of the shared control channel (HS-SCCH)
`
`information (indication) and the start of the corresponding shared data channel informa(cid:173)
`tion (transmission data) as seen in Figure 14. The shared data channel is carried by the
`30 High Speed Physical Downlink Shared Channel (HS-POSCH).
`
`Ex. 1009 / Page 3 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`The number of control channels as seen from the UE's point-of-view can range from a
`
`minimum of one control channel to a maximum of four control channels. The UE has the
`
`capability to monitor up to four control channels simultaneously.
`
`The control channel carries a UE identifier (e.g. in a UE-specific cyclic redundancy check
`
`5
`
`field) that identifies the UE for which it is carrying the information necessary for decoding
`
`the HS-POSCH. The UE identifies the control channel carrying information for it by de(cid:173)
`scrambling the first part of the control channel by the UE identity. This part contains the
`
`canalization code set and the modulation scheme for the shared data channel allocation
`
`with the second part containing the transport block size and Hybrid ARO related informa-
`tion (Hybrid-ARO process information, Redundancy and Constellation version). One cy(cid:173)
`
`10
`
`clic redundancy check (CRC) is calculated over both parts and attached to the control
`
`channel information. The UE identifier (UE ID) is similar to the shared data channel Ra(cid:173)
`
`dio Network Temporary Identity (HS-RNTI). The term UE ID is used on the physical layer
`
`PHY, while the term HS-RNTI is used in the radio resource control RRC layer. This iden-
`
`15
`
`tifiers uniquely identify a UE within the cell.
`
`In Figure 15 it is shown how different MAC-d SDUs are concatenated to form a data
`
`transmitted via the physical channels. The transmitted data are secured by a CRC field.
`Besides the shared control channel signaling carried on the control channel there is in(cid:173)
`
`band signaling on shared data channel within the Medium Access Control header (MAC-
`
`20
`
`hs header) of MAC-hs protocol data unit (POU). These parameters are for instance sig(cid:173)
`naled to support to identify the reordering queue (by means of a priority class identifier)
`
`and to provide in-sequence delivery (by means of transmission sequence numbers) at
`
`the UE. These parameters are protected by the same physical layer CRC as the POU
`Data block.
`
`25
`
`Figure 16 shows the encoding chain used to encode the data transmitted via the shared
`
`control channel as an allocation message. As shown in the Figure, information such as a
`
`channelization-code-set Xccs. modulation scheme information Xms. transport-block size
`information Xtbs, Hybrid-ARO process information xhap. redundancy and constellation ver(cid:173)
`
`sion information Xrv, a new data indicator Xnd and a receiver specific identifier, i.e. a user
`equipment identity Xue is transmitted in the control channel information indicating to a re(cid:173)
`
`30
`
`ceiver to receive data on the shared data channel. These parameters are needed by the
`
`receiver to successfully receive and reconstruct the data directed to it on the shared data
`channel. Figure 16 shows how these parameters are multiplexed, coded and mapped to
`
`2
`
`Ex. 1009 / Page 4 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`the shared control channel. The realization of these functions are described in the follow(cid:173)
`ing:
`
`The 16 bit UE identity is mapped such that Xue,1 corresponds to the Most Significant Bit
`and Xue,16 to the Least Significant Bit. The channelization-code-set information Xccs,1, Xccs,2,
`... , Xccs,7 and modulation-scheme information Xm.1 are multiplexed together. This gives a
`sequence of bits x1.1, x1.2, ... , x1.a where
`
`5
`
`X1,i = Xccs,i
`
`X1,; = Xms,i-7
`
`i=1,2, ... ,7
`
`i=B
`
`The transport-block-size information Xtbs.1, Xtbs,2, ... , Xtbs,6, Hybrid-ARQ-process informa-
`tion Xhap, 1,Xhap,2, Xhap,3, redundancy version information Xrv, 1, Xrv,2, Xrv,3 and the new data
`indicator Xnd.1 are multiplexed together. This gives a sequence of bits X2.1, X2.2, ... , x2.13
`where
`
`X2J = Xtbs,i
`
`X2,i = Xnd,i-12
`
`i=1,2,. . .,6
`
`i=7,8,9
`
`i=10, 11, 12
`
`i=13
`
`10
`
`15
`
`From the sequence of bits X1,1, X1.2, ... , X1.a. x2.1, x2.2, ... , x2.13 a 16 bits CRC attachment
`for shared control channel is calculated.
`
`20
`
`The calculation of the CRC field gives a sequence of bits c1, c2, ... , c16. This sequence of
`bits is then masked with the UE Identity Xue,1, Xue,2, ... , Xue,16 and then appended to the
`sequence of bits x2.1, x2.2, ... , X2,13 to form the sequence of bits Y1, Y2, ... , Y2s, where
`
`i=1,2,. . ., 13
`
`i=14, 15, ... ,29
`
`25
`
`Rate 1/3 convolutional coding, is applied to the sequence of bits x1,1,x1,2, ... ,x1.8 . This
`gives a sequence of bits z1.1, z1,2, ... , z1,4a. Further, rate 1/3 convolutional coding, is ap(cid:173)
`plied to the sequence of bits Y1, Y2, ... , Y29. This gives a sequence of bits z2.1, z2.2, ... ,
`Z2,111.
`
`3
`
`Ex. 1009 / Page 5 of 41
`
`

`

`WO 2004/057896
`
`PCT/EP2003/014324
`
`Note that the coded sequence lengths result from the termination of K=9 convolutional
`
`coding being fully applied.
`
`The rate matched bits r1.1,r1,2 ... r1,4o shall be masked in an UE specific way using the UE
`identity Xue,1, Xue,2, ... , Xue,1 6, to produce the bits S1,1,S1,2 ... S1,4o-
`
`5
`
`Intermediate code word bits bi, i=1,2 ... ,48, are defined by encoding the UE identity bits
`using the rate Y2 convolutional coding. Eight bits out of the resulting 48 convolutionally
`encoded bits are punctured using the rate matching, that is, the intermediate code word
`
`bits b1, b2, b4, ba, b42, b4s, b47, b4a, are punctured to obtain the 40 bit UE specific
`
`scrambling sequence C1, c2, .... C40.
`
`10
`
`The mask output bits s1.1,s1.2 ... S1,4o are calculated as follows:
`
`s1.k =(r1.k + ck) mod 2
`
`fork= 1,2 .. .40
`
`Since the control channels are shared channels they can be received by many UEs in a
`
`cell. The UEs that are assigned to monitor up to four control channels, will decode the
`
`information and check whether in their UE ID is used in e.g. a UE specific CRC field con-
`
`15
`
`tained in the control channel information. If the CRC is correct it is assumed that the con(cid:173)
`
`trol channel has been transmitted for this UE and the transmission data on the shared
`
`data channel are directed to this particular UE. The UE will read the signaling data and
`
`receive the shared data channel on which data is being transmitted for the UE.
`
`The control channel for example is protected by a 16 bit CRC field. This means there is
`approximately a likelihood of 2"16 for an illegitimate decoding attempt by a receiver. If no
`precautions are taken it could happen that a UE illegitimately receives the transmission
`
`data by successfully receiving and decoding the control channel information. Due to the
`UE specific masking of R1 the code allocation and the modulation format (8 bit in all) will
`usually be corrupted (likelihood of 2"8
`} if received by a receiver with a wrong UE ID. Nev-
`ertheless it can happen the code allocation and modulation format are by chance re(cid:173)
`
`20
`
`25
`
`ceived correctly and then the receiver is able to receive and decode the shared data
`
`channel. This may not seem to be critical since the correct receiver will receive the data
`
`independently from the second wrong receiver. Although a error rate is marginal, this can
`
`cause serious malfunction if the decoded MAC-hs SDUs are unintentionally delivered to
`
`30
`
`higher layer and are mixed up with other correct data flows. Also when considering the
`
`high number of UEs in a communication network and the many decoding attempts em(cid:173)
`
`ploying CRC checks, it becomes more likely that a UE illegitimately successfully receives
`4
`
`Ex. 1009 / Page 6 of 41
`
`

`

`WO 2004/057896
`
`PCT/EP2003/014324
`
`information on the shared data channel. Passing these information to a higher process(cid:173)
`ing layer, such as applications can cause serious malfunctions in the UE (receiver).
`
`In state of the art system such error behavior is usually excluded not only having a UE
`
`identifier in the resource assignment message but to have a second UE identifier on the
`data channel. For instance the 16 bit UE ID could be included in-band in the packet
`header e.g. in the MAC-hs header on the shared data channel's data packets or in the
`header of higher layer protocols. This will result in a doubled protection on control chan(cid:173)
`nel as well as on the shared data channel. In other words, any extra data overhead will
`
`reduce bandwidth efficiency on the shared data channels. Another option would be to
`add overhead on the signaling channel (e.g. lower coding rate, larger CRC, UE ID) to
`exclude such misinterpretation completely. Any further error protection in terms of addi(cid:173)
`tional bits assigned to headers as overhead information on the shared data channels will
`increase the data rate of the these channels which is not acceptable from radio efficiency
`point of view. The codes that need to be reserved for the signaling purpose should have
`a low spreading factor since they are just used during the an allocation message. In any
`of the state of the art solution additional overhead for the UE ID would be transmitted
`
`every transmission time interval although the error behavior is almost a marginal error
`case. Further if the UE ID is transmitted on the shared signaling or data channel, there is
`an increased receiver complexity because the receiver has to extract the identifier and
`has to compare it with the known identifier.
`
`It is therefore the object of the present invention to provide methods for data transmis(cid:173)
`
`sion and reception to ensure secure data delivery to one or more legitimate receivers. It
`is a further object of the present invention to prevent non legitimate receivers from cor(cid:173)
`rect reception. It is still a further object of the present invention to provide respective
`transmitters and receivers as well as a communication system employing at least one of
`the transmitters and receivers.
`
`The present invention is based on the idea that by introducing a receiver specific identi(cid:173)
`fier in the data manipulation of the coding chain of the shared data channels (HS-DSCH),
`by means of verifying data integrity information (CRC check) of the transmitted shared
`channel's in the decoding chain at the receiver, a receiver can be bared from passing
`
`illegitimately received data to a further processing layer in the receiver. Thus, even in
`case the receiver, e.g. by accident, correctly decodes an allocation message from the
`control channel informing it to receive transmission data on the shared data channel
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`5
`
`Ex. 1009 / Page 7 of 41
`
`

`

`WO 2004/057896
`
`PCT/EP2003/014324
`
`though it is not intended to receive this HS-DSCH-information, the verification of the re(cid:173)
`ceived transmission data in the decoding chain at the receiver will fail, as the illegitimate
`
`receiver will not use the same receiver specific identifier in the decoding chain of the
`
`shared data channel as the transmitter used in its coding chain for the shared data chan-
`
`5
`
`nel. As the receiver specific identifier becomes an integral part of the coding and decod(cid:173)
`
`ing chain in the transmitter and the receiver there is no need to add overhead information
`
`to packet headers, thus that bandwidth efficiency is maintained and data security is es(cid:173)
`
`tablished.
`
`The present invention provides a method for transmitting data from a transmitter to a re-
`ceiver of a communication system using a control channel and shared data channel for
`
`1 O
`
`data transmission, wherein transmission data to be transmitted via the shared data
`
`channel are modified in accordance with a receiver-specific identifier. Next a transmitter
`
`signals to a receiver via the control channel to receive the modified transmission data.
`
`The transmitter transmits said modified transmission data over the shared data channel.
`
`15
`
`The modification of transmission data refers to the coding chain of the transmitter, in
`which the transmitter prepares transmission data for transmission over physical shared
`
`data channels.
`
`The coding chain provides several steps in which the receiver specific identifier may be
`
`used to modify the transmission data. The receiver specific identifier is preferably the
`
`20
`
`user equipment identifier (UE ID).
`
`It is further preferred that the receiver-specific identifier is used in a data scrambling step
`
`in the coding chain to enable secure data communication. The transmitter may therefore
`
`comprises scrambling means that employ a scrambling function to scramble the trans(cid:173)
`mission data, wherein said scrambling function is initialized with the receiver specific
`
`25
`
`identifier. In order to execute the scrambling function, a transmitter may employ a shift
`
`register and/or uses a digital signal processor for executing shift operation to scramble
`the transmission data.
`
`Another possibility to modify the transmission data in a transmitter in accordance with the
`
`receiver specific identifier is to generate an error checking sequence for the transmission
`data, wherein said error checking sequence is masked with the receiver specific identi(cid:173)
`
`30
`
`fier. Thus, in case an illegitimate receiver would employ the wrong receiver specific iden(cid:173)
`
`tifier to unmask said error checking sequence causes the data integrity check to fail.
`
`6
`
`Ex. 1009 / Page 8 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`Another step in which the transmitter may include the receiver specific identifier in the
`coding chain is the segmenting of transmission data into data blocks. The size of the
`
`data blocks and/or the number of data blocks when segmenting the transmission data
`can be determined in accordance with the receiver specific identifier. Again, the verifica-
`
`5
`
`tion of the data integrity of the received transmission data in an illegitimate receiver
`
`would fail if the receiver would employ the wrong receiver specific identifier to combine
`
`the data blocks.
`
`Another further possibility to include the receiver specific identifier in the coding chain is
`
`the step of channel coding. The channel coder performs channel coding of the transmis-
`sion data and comprises an interleaver which interleaves the transmission data in the
`
`10
`
`coder using an interleaving pattern which is determined in accordance with the receiver
`
`specific identifier. The interleaver in the channel coder may comprise storage means for
`
`storing a plurality of interleaving patterns, which are selected in accordance with said
`
`receiver specific identifier and/or uses a digital signal processor for determining said in-
`
`15
`
`terleaving pattern in accordance with the receiver specific identifier. Again, data verifica(cid:173)
`tion would fail in case a receiver illegitimately receives data on the shared data channel.
`
`Another possibility to include the receiver specific identifier in the coding chain of the
`transmitter is the step of rate adaptation, which matches the data rate of the transmission
`
`data to the channel capacity, that is the maximum bit rate of the transmission channels
`
`20
`
`(shared data channels). Matching is done by either by puncturing the transmission data
`to reduce the transmission data rate using a puncturing pattern, which is selected in ac(cid:173)
`
`cordance with that receiver-specific identifier or by repeating some of the transmission
`
`data or by adding dummy information to the transmission data to increase the transmis(cid:173)
`sion data rate, wherein the repeated and/or dummy information is added at positions
`
`25 within the transmission data, which are determined in accordance with the receiver spe(cid:173)
`
`cific identifier. For performing rate adaptation (rate matching), data modification means of
`
`the transmitter comprises rate adaptation means for matching the data rate of the trans(cid:173)
`mission data to the channel capacity. The rate adaptation means comprises storing
`
`means for storing a plurality of puncturing patterns, which are selected in accordance
`30 with the receiver specific identifier and/or uses a digital signal processor for determining
`
`said puncturing pattern in accordance with the receiver specific identifier.
`
`Moreover, during the generation of redundancy versions of transmission data in the cod(cid:173)
`ing chain of the transmitter the receiver specific identifier can be employed. In case of
`
`7
`
`Ex. 1009 / Page 9 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`employing hybrid ARQ schemes in the transmitter data, the redundancy version of the
`
`transmission data are generated using a puncturing pattern, which is determined in ac(cid:173)
`cordance with the receiver specific identifier.
`
`Further, the receiver specific identifier can be employed in an interleaving step of the
`
`5
`
`data modification scheme (coding chain) in the transmitter. In the step of interleaving
`
`interleaving patterns are used in accordance with the receiver specific identifier, wherein
`
`the interleaving pattern determines the positioning of data blocks within the transmission
`
`data in the interleaving step.
`
`Moreover, the receiver specific identifier may also be used when rearranging a symbol
`
`10
`
`constellation of demodulation schemes. In this step in the coding chain, the symbol con(cid:173)
`
`stellation data bits of the transmission data are mapped to modulation symbols, wherein
`
`the mapping is determined in accordance with the receiver specific identifier.
`
`Finally, a further possibility to employ receiver specific identifier in the coding chain is the
`
`mapping of transmission data to physical channels. In this step of mapping transmission
`
`15
`
`data to physical channels, data blocks of that transmission data are matched to physical
`channels, wherein the sequence in which the data blocks are mapped on the physical
`
`channels is determined in accordance with said receiver-specific identifier. Depending on
`
`the access scheme the physical channels will correspond to one or more codes, fre(cid:173)
`
`quencies or time slots or any combination.
`
`20
`
`In all the data modification steps in the coding chain of the transmitter described above a
`
`receiver has to employ the same receiver specific identifier in the decoding chain to suc(cid:173)
`
`cessfully reconstruct the transmission data. In case a receiver employs the wrong re(cid:173)
`
`ceiver specific identifier that is an identifier different from that used in the transmitter in
`the coding chain, the verification of the data integrity in a CRC check during data recon-
`
`25
`
`struction will fail. Thus, the received data is not passed to a higher processing layer and
`data security is established.
`
`For receiving and recombining the modified data at the receiving end, the present inven(cid:173)
`tion provides a receiver for monitoring said control channel for an indication to receive
`
`transmission data which have been modified at the transmitter in accordance with a re-
`
`30
`
`ceiver specific identifier. Further, a receiver comprises receiving means for receiving the
`
`modified transmission data on the shared data channel. Moreover, the receiver com-
`
`8
`
`Ex. 1009 / Page 10 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`prises data reconstruction means for reconstructing said transmission data from said
`modified transmission data in accordance with the receiver's specific identifier.
`
`It is important that the receiver verifies the integrity of the transmission data using an er(cid:173)
`
`ror checking sequence using verification means comprised in the data reconstruction
`
`5 means. As explained before, reconstructing transmission data will fail in case the re(cid:173)
`
`ceiver does not use the same receiver specific identifier in the decoding chain as used by
`
`a transmitter in its coding chain. Also the step of checking data integrity can be employed
`
`to insure that no illegitimate receiver successfully receives and decode data from the
`
`shared data channel by masking the error checking sequence with the receiver specific
`identifier.
`
`1 O
`
`In case the receiver specific identifier has been used in a scrambling process at the
`
`transmitter, the receiver's data reconstruction means employs de-scrambling means for
`
`de-scrambling the modified transmission data.
`
`The de-scrambling means may employ a de-scrambling function to de-scramble the
`
`15 modified transmission data, wherein said de-scrambling function is initialized with the
`
`receiver specific identifier for the de-scrambling process, the de-scrambling means may
`
`comprise a shift register and/or uses a digital signal processor for executing shift opera(cid:173)
`tions to de-scramble the modified transmission data.
`
`In order to undo the step of segmenting in the transmitter, the step of reconstructing the
`
`20
`
`transmission data in the receiver concatenates the modified transmission data segments
`into a data block. In this step, the size of segmented modified transmission data blocks
`
`and/or the number of modified transmission data segments is determined in accordance
`
`with the receiver's specific identifier.
`
`Further, the data reconstruction means may comprise a channel decoder for channel
`
`25
`
`decoding the transmission data. The channel decoder may further comprise a de(cid:173)
`interleaver for the interleaving set modified transmission data. The step of channel de(cid:173)
`
`coding performs the steps of channel decoding the modified transmission data and de(cid:173)
`interleaving said modified transmission data in the decoder using a de-interleaving pat(cid:173)
`
`tern determined in accordance with the receiver specific identifier.
`
`30
`
`The receiver may further perform the step of combining the transmission data from re-
`
`dundancy versions of the received modified transmission data. This step is necessary in
`case the transmitter generated redundancy versions of the transmission signals. The
`9
`
`Ex. 1009 / Page 11 of 41
`
`

`

`WO 2004/057896
`
`PCT/EP2003/014324
`
`step of combining said transmission data combines redundancy versions of said modified
`transmission data, wherein said redundancy versions are de-punctured using a punctur(cid:173)
`
`ing pattern being selected in accordance with the receiver specific identifier.
`
`The step of reconstructing the transmission data may further comprise matching the data
`
`5
`
`rate of the modified transmission data to a data rate of the transmission data prior to
`
`modification at the transmitter. The step is necessary to redo the rate matching in the
`transmitter to obtain the original transmission data in their original data rate. At the re(cid:173)
`
`ceiver, the step of matching the data rate depuncture the transmission data using a
`
`puncturing pattern selected in accordance with the receiver specific identifier. This step is
`
`10
`
`necessary in case the receiver puncture the transmission data to reduce the data rate. In
`
`case the transmitter increase the data rate of the transmission data during the modifica(cid:173)
`
`tion, the receiver removes repeated information and/or dummy information from the
`modified transmission data, wherein said repeated and/or dummy information is removed
`
`from positions within the modified transmission data, which are determined in accor-
`
`15
`
`dance with the receiver specific identifier.
`
`The data reconstruction means comprise rate matching means for matching the data rate
`
`of the modified transmission data to a data rate of a transmission data prior to modifica(cid:173)
`tion, wherein the data rate adaptation means comprise this storing means for storing a
`
`plurality of puncturing patterns and/or uses a digital signal processor for determining said
`
`20
`
`puncturing pattern in accordance with the receiver specific identifier.
`
`In case the transmitter employed an interleaver for interleaving the transmission data
`
`during the modification process, the receiver will execute de-interleaving the modified
`
`transmission data as a step of reconstructing the transmission data. In order to execute
`
`the interleaving of the modified transmission data, the data reconstruction means com-
`
`25
`
`prises a de-interleaver. The de-interleaver may comprise a storage means for storing a
`
`plurality of de-interleaving patterns and/or uses a digital signal processor for determining
`said de-interleaving pattern in accordance with the receiver specific identifier. The step of
`
`de-interleaving uses a de-interleaving pattern determined in accordance with the receiver
`
`specific identifier, wherein the de-interleaving pattern determines the positioning of data
`blocks within the modified transmission data.
`
`30
`
`To reverse the step of de-mapping the transmission data to physical channels in the
`transmitter, the receiver performs the step of combining the modified transmission data
`segments received via physical channel to a serial data stream, wherein the sequence in
`
`10
`
`Ex. 1009 / Page 12 of 41
`
`

`

`WO 2004/057896
`
`PCT /EP2003/014324
`
`which the data segments are combined to form the serial data stream is determined in
`accordance with the receiver specific identifier. In order to redo the rearrangement of the
`
`symbol constellation in the transmitter, the receiver performs the step of de-mapping the
`
`symbols of the received modified transmission data into information bits employing a de-
`
`5 mapping pattern determined in accordance with the receiver specific identifier during the
`
`reconstruction of transmission data.
`
`As for the encoding chain of the transmitter, it is important to recognize that for the de(cid:173)
`
`coding chain, the same receiver specific identifier, such as a user-equipment identifier,
`
`has to be used to successfully reconstruct the original transmission data that have been
`
`10 modified by the transmitter in its encoding chain. As the receiver specific identifier may
`
`be used in one or several of the mentioned steps in the encoding chain, for example, in
`
`the steps of scrambling, generating an error checking sequence, segmenting, channel
`coding, rate matching, interleaving, etc., the receiver has to use the same receiver spe(cid:173)
`
`cific identifier in the respective steps in the decoding chain, for example, in the steps of
`
`15
`
`de-scrambling, verifying the data integrity, combining the data segments, channel d