throbber
WILEY
`
`
`WireIe§5
`
`and MOIJIIE
`Ne_twork
`Architectures
`
` Yi—Bing Lin
`
`Imrich Chlamtac 77
`Page1of5
`
`
`
`

`
`Publisher: Robert Ipsen
`Editor: Carol Long
`Associate Editor: Margaret I-Iendrey
`Managing Editor: Micheline Frederick
`Text Design 8: Composition: Integre Technical Publishing Co., Inc.
`
`Designations used by companies to distinguish their products are often claimed as
`trademarks. In all instances where John Wiley 8: Sons, Inc., is aware of a claim, the product
`names appear in initial capital or ALL CAPITAL LETTERS. Readers, however, should contact
`the appropriate companies for more complete information regarding trademarks and
`registration.
`
`This book is printed on acid-free paper.
`Copyright © 2001 by Yi-Bing Lin 8: Imrich Chlamtac. All rights reserved.
`
`Published by Iohn Wiley 8: Sons, Inc.
`
`Published simultaneously in Canada.
`
`No part of this publication may bereproduced, stored in a retrieval system or transmitted
`in any form or by any means, electronic, mechanical, photocopying, recording, scanning or
`otherwise, except as permitted under Sections 107 or 108 of the 1976 United States
`Copyright Act, without either the prior written permission of the Publisher, or
`authorization through payment of the appropriate per-copy fee to the Copyright
`Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978)
`750-4744. Requests to the Publisher for permission should be addressed to the Permissions
`Department, Iohn Wiley 8: Sons, Inc., 605 Third Avenue, New York, NY 10158-0012, (212)
`850-6011, fax (212) 850-6008. E-Mail: PERMREQ@WILEY.COM.
`
`This publication is designed to provide accurate and authoritative information in regard to
`the subject matter covered. It is sold with the understanding that the publisher is not
`engaged in professional services. If professional advice or other expert assistance is
`required, the services of a competent professional person should be sought.
`
`Library of Congress Cataloging-in-Publication Data:
`
`0471-39492-0
`
`Printed in the United States of America
`
`10 9 8 7 6 5 4 3
`
`Page 2 of 5
`
`Page 2 of 5
`
`

`
`lntersystem Handoff and Authentication in IS-41
`
`101
`
`I A'TCAP message can have multiple components; each component
`performs one action. For simplicity, IS-41 TCAP messages are com-
`posed of a single component. Some personal communication service
`implementations under advanced intelligent network platform use
`multiple component TCAP messages.
`
`6.2 5-41 Authenticaton
`
`The EIA/TIA Telecommunications Systems Bulletins (TSB) 51 defines proto-
`cols for authentication, voice privacy, and signaling message encryption,
`which have been incorporated into IS-41 Revision C and later versions.
`The TSB—51 algorithm is based on private key cryptographic techniques in
`which a secret key, known as shared secret data (SSD), is shared between the
`MS and the authentication center (AuC). This key is known only to these
`two parties.
`a
`I
`Two authentication schemes have been proposed in TSB-51. In the
`without-sharing (WS) scheme, the SSD is shared only between the authenti-
`cation center and the MS. In the sharing (S) scheme, the SSD or some aspect
`of SSD may be shared with the Visited system as well. Since the Visited
`system has the SSD, it can authenticate the MS at call origination or de-
`livery, thereby considerably reducing message flow and call setup time.
`However, as will be seen later, this scheme requires additional message
`exchanges during registration. Thus, there is/a trade-off between the two
`schemes, based on the expected number of calls to /from the user between
`two consecutive registrations. For a user with high call frequency, sharing
`the SSD with the visited system is beneficial; consequently, the S scheme
`is preferable. For a user with high mobility rate, sharing SSD with the Vis-
`ited system results in considerably increased traffic; consequently, the WS
`scheme is preferable. For a given user, the call and the move frequencies
`may vary from time to time; therefore, it is desirable to switch between
`the two authentication schemes as the user's behavior changes. We de-
`scribe two adaptive algorithms to select the authentication scheme for a
`user. Performance studies indicate that as call or move frequencies of a
`user change, the adaptive algorithms automatically select the appropriate
`authentication scheme in real time.
`
`6.2.1 Privacy and Authentication in TSB-51
`
`In AMPS, every MS is associated with a mobile identification number
`(MIN) and an electronic serial number (ESN). A MIN is a North American
`
`Page 3 of 5
`
`Page 3 of 5
`
`

`
`102
`
`Wireless and Mobile Network Architectures
`
`Numbering Plan (NANP) number that serves as a mobile telephone
`number. MlNs are programmed into MS at purchase, and are known to
`the customers. An ESN is created at manufacture, and the customers are
`not supposed to be aware of it. The ESN is a 32-bit serial number where
`the highest~or_der 8 bits represent the manufacturer's code. The remaining
`bits are used as a unique MS number.
`When the first AMPS network was built at Bell Labs, few users were
`
`expected. ESN was considered sufficient to authenticate a user. Some
`unscrupulous people figured out that they could receive MINS and ESNS
`over the air and then reprogram phones so that other cellular users
`would get the bills. Scanning test equipment for intercepting MIN/ESN
`combinations is legitimately available. Cloned phones can be created
`following the scanning and reprogramming procedures. To address
`this serious security issue, this section describes two EIA/ TIA TSB-51
`schemes for privacy and authentication. We first describe the without-
`sharing (WS) scheme, then show how it differs from the sharing (S)
`scheme. To facilitate the discussion that follows, we reiterate notions
`and terminologies introduced in Chapter 5, Section 5.2. The AuC is a
`database connected to the HLR, which provides it with the authentication
`parameters and ciphering keys used to ensure network security. The AuC
`is solely responsible for maintaining and updating the SSDs. Users move
`about location areas (LAS) belonging to one or more PCS service providers
`(PSPS). Each PSP may provide -some combination of BSs for offering
`wireless access to the MSS. These BSs are controlled by MSCS. Associated
`with each location area is a Visitor location register (VLR). The VLRs may
`be part of the PSP network. It is likely that the VLRS are collocated with
`MSCS. For demonstration purposes, we assume that VLRs are separated
`from the PSP network. Note that the results of this section are not affected
`by the locations of VLRS. One or more home location registers (HLRS) are
`maintained by the PSP, which maintain user profiles, current location area,
`and so on.
`
`56.2.2 Without-Sharing (WS) Scheme
`
`In the WS scheme, the SSD is known to the AuC and the MS only. Message
`flow for privacy and authentication of the WS scheme is described below.
`
`6.2.2.7 Registration (Location Update)
`
`The authentication message flow for MS registration is shown in Figure 6.5
`and is described in the following steps:
`
`Page 4 of 5
`
`Page 4 of 5
`
`

`
`488
`
`Wireless and Mobile Network Architectures
`
`three dimensions. According to Andy Hopper at Cambridge University,
`”With active bat, it is possible to determine the spatial relationships of
`people, displays, telephones, keyboards, and so on, and configure them
`automatically to create a truely active office environment.” Details of active
`badges and sentient computing can be found in www.uk.research.att.com.
`
`24.3 Bluetooth
`
`The efforts to develop an integrated voice/ data home wireless network
`started in 1998, when two working groups began establishing industry
`standards in this area: the Home RF Working Group (HRFWG) and the
`Bluetooth Special Interest Group (SIG). Bluetooth technology was a spin-
`off of an internal Ericsson project on wireless connectivity. Understanding
`that it would be the best way to make the technology successful, Ericsson
`made Bluetooth available to the rest of the industry. Consequently, along
`with Nokia, IBM, Intel, and Tobisha, Ericsson founded Bluetooth. In
`addition to these two groups, at company named Home Wireless Network
`(HWN) debuted proprietary home wireless products in January 1999.
`I-IWN, with Lucent as its major investor, is targeting home and small
`businesses, offering integrated voice and data products.
`As data and voice merge in the everyday lives of people, an integrated
`cordless system based on the Bluetooth technology should facilitate access
`to voice and data. It should also stir the growth of cordless phones, and
`expand to small office applications. Bluetooth operates in the 24-2483
`GI-lz ISM band. It utilizes fast-frequency hopping with spread-spectrum
`techniques, whereby packets are delivered in specified time slots at up to
`723.2 Kbps. Bluetooth units (such as mobile handsets, PCs, PDAs, printers,
`and so on) can be connected through the Bluetooth radio link to form a
`piconet in the office environment.
`Figure 24.5 illustrates the Bluetooth protocol stack. A host controller
`interface is defined, which provides higher-layer protocols and a command
`interface to control the baseband and link manager, and to access hardware
`status and control registers. The Bluetooth protocols are described as
`follows.
`
`24.3.1 Buetooth Core Protocols
`
`These include Bluetooth RF, baseband, Link Manager Protocol (LMP),
`Logical Link and Control Adaptation Protocol (LZCAP) and Service
`
`Page 5 of 5
`
`Page 5 of 5

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