Apple Computer Inc. v. Burst.com, Inc.

Filing 109

Declaration of Sheila Hemami in Support of 107 Response Burst.com, Inc's Opposition to Plaintiff Apple Computer, Inc.'s Motion for Summary Judgment on Invalidity Based on Kramer and Kepley Patents filed byBurst.com, Inc.. (Attachments: # 1 Exhibit A to S. Hemami Declaration# 2 Exhibit B to S. Hemami Declaration# 3 Exhibit C to S. Hemami Declaration# 4 Exhibit D to S. Hemami Declaration# 5 Exhibit E to S. Hemami Declaration# 6 Exhibit F to S. Hemami Declaration# 7 Exhibit G to S. Hemami Declaration# 8 Exhibit H to S. Hemami Declaration# 9 Exhibit I to S. Hemami Declaration# 10 Exhibit J to S. Hemami Declaration# 11 Exhibit K to S. Hemami Declaration)(Related document(s) 107 ) (Crosby, Ian) (Filed on 6/7/2007)

Apple Computer Inc. v. Burst.com, Inc.

Doc. 109 Att. 6

Case 3:06-cv-00019-MHP

Document 109-7

Filed 06/07/2007

Page 1 of 8

Dockets.Justia.com

Case 3:06-cv-00019-MHP

Document 109-7

Filed 06/07/2007

Page 2 of 8

INTERNATIONAL TELECOMMUNICATION UNION

ITU-T
TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU

Q.921
(03/93)

DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1

ISDN USER-NETWORK INTERFACE-DATA LINK LAYER SPECIFICATION

ITU-T Recommendation Q.921
(Previously "CCITT Recommendation")

Case 3:06-cv-00019-MHP

Document 109-7

Filed 06/07/2007

Page 3 of 8

FOREWORD
The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. ITU-T Recommendation Q.921 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).

___________________

NOTES 1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. 2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.

ITU 1994 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.

Case 3:06-cv-00019-MHP

Document 109-7

Filed 06/07/2007

Page 4 of 8

CONTENTS
Recommendation Q.921 (03/93)

Page 1 2 General ........................................................................................................................................................... Frame structure for peer-to-peer communication........................................................................................... 2.1 General.............................................................................................................................................. 2.2 Flag sequence.................................................................................................................................... 2.3 Address field..................................................................................................................................... 2.4 Control field...................................................................................................................................... 2.5 Information field............................................................................................................................... 2.6 Transparency..................................................................................................................................... 2.7 Frame check sequence (FCS) field ................................................................................................... 2.8 Format convention ............................................................................................................................ 2.9 Invalid frames ................................................................................................................................... 2.10 Frame abort....................................................................................................................................... Elements of procedures and formats of fields for data link layer peer-to-peer communication .................... 3.1 General.............................................................................................................................................. 3.2 Address field format ......................................................................................................................... 3.3 Address field variables ..................................................................................................................... 3.4 Control field formats......................................................................................................................... 3.5 Control field parameters and associated state variables.................................................................... 3.6 Frame types....................................................................................................................................... Elements for layer-to-layer communication ................................................................................................... 4.1 General.............................................................................................................................................. 4.2 Primitive procedures ......................................................................................................................... 4.3 Block interaction diagram of the data link layer............................................................................... Definition of the peer-to-peer procedures of the data link layer .................................................................... 5.1 Procedure for the use of the P/F bit .................................................................................................. 5.2 Procedures for unacknowledged information transfer...................................................................... 5.3 Terminal endpoint identifier (TEI) management procedures............................................................ 5.4 Initialization of data link layer parameters ....................................................................................... 5.5 Procedures for establishment and release of multiple frame operation ............................................ 5.6 Procedures for information transfer in multiple frame operation ..................................................... 5.7 Re-establishment of multiple frame operation.................................................................................. 5.8 Exception condition reporting and recovery..................................................................................... 5.9 List of system parameters ................................................................................................................. 5.10 Data link layer monitor function....................................................................................................... 1 1 1 1 1 2 2 3 3 3 5 5 5 5 5 5 7 8 10 13 13 18 18 22 22 22 23 32 33 36 40 41 43 44 46 47 47 47 50 51 51 85 86 86 i

3

4

5

Annex A ­ Provision of point-to-point signalling connections ............................................................................... Annex B ­ SDL for point-to-point procedures...................................................................................................... B.1 General.............................................................................................................................................. B.2 An overview of the states of the point-to-point data link layer entity .............................................. B.3 Cover notes ....................................................................................................................................... B.4 The use of queues ............................................................................................................................. B.5 SDL representation ........................................................................................................................... Annex C ­ SDL representation of the broadcast procedures.................................................................................. Annex D ­ State transition table of the point-to-point procedures of the data link layer .......................................... D.2 Key to the state transition table......................................................................................................... Recommendation Q.921 (03/93)

Case 3:06-cv-00019-MHP

Document 109-7

Filed 06/07/2007

Page 5 of 8
Page

Annex E ­ Protocol Implementation Conference Statement (PICS) to Recommendation Q.921 for Basic Rate (User-side)...................................................................................................................................................... E.1 General.............................................................................................................................................. E.2 Abbreviations and special symbols................................................................................................... E.3 Instructions for completing for PICS Proforma................................................................................ E.4 Global statement of conformance ..................................................................................................... E.5 Protocol Capabilities (PC) ................................................................................................................ E.6 Frames ­ Protocol Data Units (FR) .................................................................................................. E.7 System parameters (SP) .................................................................................................................... Appendix I ­ Retransmission of REJ response frames........................................................................................... I.1 Introduction ...................................................................................................................................... I.2 Procedure .......................................................................................................................................... Appendix II ­ Occurrence of MDL-ERROR indication within the basic states and actions to be taken by the management entity ......................................................................................................................................... II.1 Introduction ...................................................................................................................................... II.2 Layout of Table II.1.......................................................................................................................... II.3 Preferred management actions.......................................................................................................... Appendix III III.1 III.2 III.3 III.4 ­ Optional basic access deactivation procedures .............................................................................. Introduction ...................................................................................................................................... Description of the Conceptual Model............................................................................................... Deactivation procedure with MPH-DEACTIVATE indication........................................................ Deactivation procedure without MPH-DEACTIVATE indication...................................................

147 147 147 148 148 149 153 154 155 155 155 156 156 156 156 158 158 158 159 162 163 163 163 166

Appendix IV ­ Automatic negotiation of data link layer parameters..................................................................... IV.1 General.............................................................................................................................................. IV.2 Automatic negotiation of data link layer parameter values .............................................................. References .................................................................................................................................................................

ii

Recommendation Q.921

(03/93)

Case 3:06-cv-00019-MHP
Recommendation Q.9211)
Recommendation Q.921 (03/93)

Document 109-7

Filed 06/07/2007

Page 6 of 8

ISDN USER-NETWORK INTERFACE ­ DATA LINK LAYER SPECIFICATION
(Malaga-Torremolinos, 1984; modified at Helsinki, 1993)

1

General

This Recommendation specifies the frame structure, elements of procedure, format of fields and procedures for the proper operation of the Link Access Procedure on the D-channel, LAPD. The concepts, terminology, overview description of LAPD functions and procedures, and the relationship with other Recommendations are described in general terms in Recommendation Q.920 [1].
NOTES 1 As stated in Recommendation Q.920 [1], the term "data link layer" is used in the main text of this Recommendation. However, mainly in figures and tables, the terms "layer 2" and "L2" are used as abbreviations. Furthermore, in accordance with Recommendations Q.930 [2] and Q.931 [3], the term "layer 3" is used to indicate the layer above the data link layer. 2 All references within this Recommendation to "layer management entity" and/or "connection management entity" refer to those entities at the data link layer.

The abstract test suites for testing conformance to this Recommendation are contained in Recommendation Q.921 bis [4].

2
2.1

Frame structure for peer-to-peer communication
General

All data link layer peer-to-peer exchanges are in frames conforming to one of the formats shown in Figure 1. Two format types are shown in the figure: format A for frames where there is no information field and format B for frames containing an information field.

2.2

Flag sequence

All frames shall start and end with the flag sequence consisting of one 0 bit followed by six contiguous 1 bits and one 0 bit. The flag preceding the address field is defined as the opening flag. The flag following the Frame Check Sequence (FCS) field is defined as the closing flag. The closing flag may also serve as the opening flag of the next frame, in some applications. However, all receivers must be able to accommodate receipt of one or more consecutive flags. See ISDN User-Network Interfaces: Layer 1 Recommendations I.430 [5] and I.431 [6] for applicability.

2.3

Address field

The address field shall consist of two octets as illustrated in Figure 1. The format of the address field is defined in 3.2. A single octet address field is reserved for LAPB (link access procedure ­ balanced) operation in order to allow a single LAPB [7] data link connection to be multiplexed along with LAPD data link connections.
NOTE ­ The support of a LAPB data link connection within the D-channel is optional at both the network and user side.

_______________
1) This Recommendation will be included in the Series I Recommendations (1993) under the number I.441.

Recommendation Q.921

(03/93)

1

Case 3:06-cv-00019-MHP
2.4 Control field

Document 109-7

Filed 06/07/2007

Page 7 of 8

The control field shall consist of one or two octets. Figure 1 illustrates the two frame formats (A and B), each with a control field of one or two octets, depending upon the type of frame. The format of the control field is defined in 3.4.

Format A
8 7 6 5 4 3 2 1 8 7 6

Format B
5 4 3 2 1

0

1

1

Flag 1 1

1

1

0

Oc tet

1
2

0

1

1

Flag 1 1

1

1

0

Octet

1
2

Address (high order octet) Address (low order octet) Control (Note 2) Control (Note 2)

Address (high order octet) Address (low order octet) Control (Note 1) (Note 2) Control (Note 1) (Note 2)

3 4

3 4 5

5 Information FCS (first octet) FCS (second octet) Flag 1 1 N­2
N­2

. . . .

FCS (first octet) FCS (second octet) Flag 1 1

N­2 N­1 N

0

1

1

1

1

0

N

0

1

1

1

1

0

T116 1580-94/d0 1

NOTE S 1 For an acknowledged operation format B applies and one octet control field is used. 2 For multiple frame operation frames with sequence numbers contain a two octet control field and frames without sequence numbers contain a one octet control field. Connection management information transfer frames contain a one octet control field.

FIGURE 1/Q.921 Frame formats
FIGURE 1/Q.921 1161580...[D01] = 15.5 CM

2.5

Information field

The information field of a frame, when present, follows the control field (see 2.4 above) and precedes the frame check sequence (see 2.7 below). The contents of the information field shall consist of an integer number of octets. The maximum number of octets in the information field is defined in 5.9.3.

2

Recommendation Q.921

(03/93)

Case 3:06-cv-00019-MHP
2.6 Transparency

Document 109-7

Filed 06/07/2007

Page 8 of 8

A transmitting data link layer entity shall examine the frame content between the opening and closing flag sequences, (address, control, information and FCS fields) and shall insert a 0 bit after all sequences of five contiguous 1 bits (including the last five bits of the FCS) to ensure that a flag or an abort sequence is not simulated within the frame. A receiving data link layer entity shall examine the frame contents between the opening and closing flag sequences and shall discard any 0 bit which directly follows five contiguous 1 bits.

2.7

Frame check sequence (FCS) field

The FCS field shall be a 16-bit sequence. It shall be the ones complement of the sum (modulo 2) of: a) the remainder of xk (x15 + x14 + x13 + x12 + x11 + x10 + x9 + x8 + x7 + x6 + x5 + x4 + x3 + x2 + x + 1) divided (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, where k is the number of bits in the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding bits inserted for transparency, and the remainder of the division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, of the product of x16 by the content of the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding bits inserted for transparency.

b)

As a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all 1s and is then modified by division by the generator polynomial (as described above) on the address, control and information fields; the ones complement of the resulting remainder is transmitted as the 16-bit FCS. As a typical implementation at the receiver, the initial content of the register of the device computing the remainder is preset to all 1s. The final remainder, after multiplication by x16 and then division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1 of the serial incoming protected bits and the FCS, will be 0001110100001111 (x15 through x0, respectively) in the absence of transmission errors.

2.8
2.8.1

Format convention
Numbering convention

The basic convention used in this Recommendation is illustrated in Figure 2. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to n. 2.8.2 Order of bit transmission

The octets are transmitted in ascending numerical order; inside an octet bit 1 is the first bit to be transmitted. 2.8.3 Field mapping convention

When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. The lowest bit number associated with the field represents the lowest order value. For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 3 illustrates a field that spans from bit (1, 3) to bit (2, 7). The high order bit of the field is mapped on bit (1, 3) and the low order bit is mapped on bit (2, 7). An exception to the preceding field mapping convention is the data link layer FCS field, which spans two octets. In this case, bit 1 of the first octet is the high order bit and bit 8 of the second octet is the low order bit (see Figure 4).

Recommendation Q.921

(03/93)

3