throbber
Gunnar Heine
`Holger Sagkob
`
` 2011
`
` Ex. 2011-0001
`
`IPR Licensing, Inc.
`Exhibit .
`ZTE Corp v. IPR Licensing, Inc.
`IPR2014-00525 
`
`

`

`Library of Congress Cataloging-in-Publication Data
`Heine, Gunnar.
`GPRS: gateway to third generation mobile networks I Gunnar Heine, Holger
`Sagkob.
`(Artech House mobile communications series)
`p. em . . -
`Includes bibliographical references and index.
`ISBN 1-58053-159-8 (alk. paper)
`1. Mobile computing. 2. Mobile communication systems.
`II. Title.
`III. Series.
`
`I. Sagkob, Holger.
`
`QA76.59 .H45 2003
`004.6-dc21
`
`2002043670
`
`British Library Cataloguing in Publication Data
`Heine, Gunnar
`GPRS: gateway to third generation mobile networks. -
`communications series)
`1. General Packet Radio Service 2. Global system for mobile communications
`I. Title
`II. Sagkob, Holger
`621.3'8456
`
`{Artech House mobile
`
`ISBN 1-58053-159-8
`
`Cover design by Igor Valdman
`
`© 2003 ARTECH HOUSE, INC.
`685 Canton Street
`Norwood, MA 02062
`
`All rights reserved. Printed and bound in the United States of America. No part of this book
`may be reproduced or utilized in any form or by any means, electronic or mechanical,
`including photocopying, recording, or by any information storage and retrieval system, without
`permission in writing from the publisher.
`All terms mentioned in this book that are known to be trademarks or service marks have
`been appropriately capitalized. Artech House cannot attest to the accuracy of this information.
`Use of a term in this book should not be regarded as affecting the validity .of any trademark
`or service mark.
`
`International Standard Book Number: 1-58053-159-8
`Library of Congress Catalog Card Number: 2002043670
`
`10 9 8 7 6 5 4 3 2 1
`
` Ex. 2011-0002
`
`

`

`The Air Interface in GPRS
`
`3.1 The 52 Multiframe
`
`In the first chapter, we paid special attention to describing the frame hierarchy
`with 26 multiframe and 51 multiframe. One of the reasons for this is the
`definition of an additional multiframe type especially for GPRS. This new
`52 multiframe with a period of exactly 240 ms is essential for understanding
`the resource administration and operation of GPRS.
`Note that the 52 multiframe corresponds in terms of period to exactly
`two consecutive 26 multiframes as illustrated in Figure 3.1. F~r this reason,
`the function of synchronizing the mobile station to the BTS does not have
`to be altered (see also 1.6.6.1). In short, the 52 multiframe number is
`obtained by halving the 26 multiframe number. The current GPRS burden
`determines how many time slots on which ARFCNs traverse the 52
`multiframe instead of the 26 multiframe and 51 multiframe. At a given
`point, there may only be one time slot configured for GPRS, which means
`using the 52 multiframe, whereas later, all eight time slots may be reserved
`on this frequency for GPRS and therefore configured with the 52 multiframe.
`Whatever the case may be, GPRS and GSM cannot coexist on one time
`slot. Depending on the burden, the services are switched from one to the
`other. We are pointing this out so clearly here because this is one of the
`most frequently asked questions in our GPRS courses.
`
`3.1.1 Structure and Multiplexing on the 52 Multiframe
`The decisive factor for GPRS is the division of a 52 multiframe into 12
`radio blocks, where each radio block is four repetitions of the same time
`
`89
`
` Ex. 2011-0003
`
`

`

`. 90
`
`GPRS: Gateway to Third Generation Mobile Networks
`
`~0 1213(415
`1 burst (577 ,us)
`
`6
`
`71
`
`Figure 3.1 The GSM frame hierarchy with the 52 multiframe for GPRS.
`
`slot. Figure 3.2 shows the fine structure of the 52 multiframe with the 12 radio
`blocks and the TDMA frames for timing advance control and interference
`measurements.
`It is the radio blocks that constitute the atomic resource unit of GPRS.
`While a user in GSM always receives a complete time slot as a resource for
`data transmission, only radio blocks, as parts of time slots, are allocated in
`GPRS. In this way, several subscribers can share a single time slot. A further
`peculiarity of GPRS is that the resources in the uplink and downlink direc(cid:173)
`tions are almost completely independent from one another. In particular,
`the allocation of radio blocks for data transmission in GPRS is either uplink
`or downlink. Of course, bidirectional data transmission is also possible and
`is used. These, however, require two resource allocations, one per direction.
`There is no certainty that a subscriber will be allocated the same time
`slot(s) for transmission in both directions. This depends in particular on the
`multislot class of his device.
`In other words, a subscriber only receives the resources that are actually
`needed at any given time in accordance with the resource on demand concept
`
` Ex. 2011-0004
`
`

`

`Figure 3.2 The fine structure of the 52 multiframe.
`
` Ex. 2011-0005
`
`~ ~
`~ .......
`"!
`~
`~
`~
`~
`.......
`;:::!
`~
`~
`
`(C
`
`.....
`
`

`

`92
`
`GPRS: Gateway to Third Generation Mobile Networks ·
`
`of packet switched data transmission. Here, a single time slot in each direction
`can be used almost simultaneously by several subscribers.
`At this point, it is often asked how many subscribers can be allocated
`resources simultaneously on one time slot and per direction. It is still too
`early to answer this question. However, we would like to point out that in
`accordance with the 52 multiframe period, not more than 12 subscribers
`can use the same time slot within 240 ms and per direction. The transmission
`rate is also accordingly low in such a case.
`Mixed configurations on an ARFCN are of course also possible-in -
`fact, they are predominant. As Figure 3.3 illustrates, several time slots for
`circuit switched GSM can be configured on one frequency, while GPRS
`subscribers share the other time slots.
`.

`Resource allocation in GPRS will be discussed in a later section.
`
` Ex. 2011-0006
`
`

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