throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`———————
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`———————
`
`Apple Inc.,
`
`Petitioner,
`
`- vs. -
`
`Togail Technologies Ltd.,
`
`Patent Owner.
`
`U.S. Patent No. 10,791,502
`
`———————
`
`DECLARATION OF CRAIG BISHOP
`
`Ex.1005
`APPLE INC. / Page 1 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`
`
`I.
`
`TABLE OF CONTENTS
`
`INTRODUCTION ............................................................................................... 3
`
`II. QUALIFICATIONS ........................................................................................... 4
`
`III. PUBLIC AVAILABILITY OF 3GPP STANDARDS PROPOSALS AND
`TDOCS ....................................................................................................................... 9
`
`a.
`
`b.
`
`c.
`
`d.
`
`e.
`
`f.
`
`Prominence and Purpose of 3GPP ........................................................ 9
`
`3GPP’s Policy of Making Documents Public .....................................11
`
`3GPP Structure and Standards Development Process ........................11
`
`3GPP Documents – TDocs ..................................................................13
`
`Distribution over the 3GPP Listserv ...................................................15
`
`The 3GPP Website’s Public File Repository ......................................18
`
`IV. Ex.1007, R2-1801795 (“OPPO”) ......................................................................26
`
`V. Ex.1108, R2-1802094 (“Vivo”) ........................................................................29
`
`VI. Ex.1012, R2-1800041 (“Asustek”) ...................................................................33
`
`VII. Ex.1013, R2-1708072 (“Huawei”) ...................................................................37
`
`VIII.
`
`DECLARATION.................................................................................41
`
`
`
`
`
`
`
`
`
`2
`
`Ex.1005
`APPLE INC. / Page 2 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`I.
`
`INTRODUCTION
`
`I, Craig Bishop, declare as follows:
`
`
`
`I have been retained as an independent expert witness on behalf of
`
`Apple Inc. related to Inter Partes Review (“IPR”) of U.S. Patent No. 10,791,502
`
`(“the ’502 patent”).
`
`
`
`I am being compensated for my work in this matter at my accustomed
`
`hourly rate. I am also being reimbursed for reasonable and customary expenses
`
`associated with my work and testimony in this investigation. My compensation is
`
`not contingent on the results of my study, the substance of my opinions, or the
`
`outcome of this matter.
`
`
`
`In the preparation of this declaration I have reviewed Exhibits
`
`Ex.1007, Ex.1008, Ex.1012, and Ex.1013, each of which is a type of material that
`
`experts in my field would reasonably rely upon when forming their opinions.
`
`
`
`In forming the opinions expressed within this declaration, I have
`
`considered:
`
`1) The exhibits listed above; and
`
`2) My own academic background, knowledge, and professional
`
`experiences in the field of wireless communications and 3GPP
`
`standards-development, as described below.
`
`
`
`Although I have attempted to organize the information presented in
`
`
`
`3
`
`Ex.1005
`APPLE INC. / Page 3 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`this declaration into helpful sections and/or divisions, my opinions are supported
`
`by the information in the declaration in its entirety.
`
`II. QUALIFICATIONS
`
` My complete qualifications and professional experience are described
`
`in my curriculum vitae, a copy of which has been submitted as Ex.1006. The
`
`following is a summary of my relevant qualifications and professional experience.
`
`
`
`I earned my Bachelor of Electronic Engineering degree with Honors
`
`from Polytechnic of Central London in 1989. In 2005, I earned my MSC in
`
`Computer Science with Distinction from the University of Kent.
`
`
`
`After graduating with my first degree, I worked as an operations
`
`engineer at the British Broadcasting Corporation (BBC) for 4 years, then as a civil
`
`servant at the UK Radiocommunications Agency until 1996, during which time I
`
`became involved in telecommunications standardization in the European
`
`Telecommunication Standards Institute (“ETSI”), working in particular in
`
`Technical Committee Radio Equipment and Systems (TC RES2) concerned with
`
`the standardization of Private Mobile Radio (PMR). From 1994 through 1996, I
`
`acted as Rapporteur for voice and data related PMR standards ETS 300 113, ETS
`
`300 219 and ETS 300 390. I participated as the only TC RES2 delegate on behalf
`
`of the UK Radiocommunications Agency, generating proposals in support of UK
`
`administration and business requirements, downloading and reviewing other
`
`
`
`4
`
`Ex.1005
`APPLE INC. / Page 4 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`meeting input documents when available, and proposing changes as necessary to
`
`ensure input documents and the resulting specifications were in line with said
`
`requirements.
`
`
`
`In 1996, I joined Samsung Electronic Research Institute as a Senior
`
`Standards Engineer where I worked for 16 years, eventually becoming Director of
`
`Standards and Industry Affairs in 2011. My work at Samsung mainly focused on
`
`the standardization of GSM/GPRS, UMTS, and LTE/EPS systems. Initially, I
`
`participated in ETSI Special Mobile Group (SMG) committees SMG1, SMG2,
`
`SMG4, SMG5, SMG9 and relevant UMTS related sub-committees until 1999,
`
`working on the air interface radio access network protocols, service, and terminal
`
`aspects of UMTS and GSM/GPRS. I was specifically involved in the ETSI SMG2
`
`meetings leading up to selection of WCDMA as the radio access technology for the
`
`Frequency Division Duplex mode of UMTS.
`
` Beginning in 1998, I worked as a Principal Standards Engineer on the
`
`3rd Generation Partnership Project (3GPP) on UMTS. I have been involved with
`
`3GPP since its inception. I attended the inaugural 3GPP TSG meetings held in
`
`December 1998, and I began attending Working Group (WG) meetings in 1999. I
`
`mainly attended Radio Access Network (RAN) WG1, RAN WG2, Services &
`
`System Aspects (SA) WG1, Terminals (T) WG2, and other Working Groups and
`
`Technical Specification Group (TSG) plenary meetings covering similar technical
`
`
`
`5
`
`Ex.1005
`APPLE INC. / Page 5 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`aspects as in my previous work in ETSI. As examples, RAN WG1 was, and is, a
`
`Working Group responsible for the specification of the physical layer of the latest
`
`wireless cellular standards, and RAN WG2 was, and is, a Working Group
`
`responsible for signaling protocol layers 2 and 3 residing just above the physical
`
`layer. As part of this work, I would prepare meeting contributions in support of
`
`Samsung’s research and development activities. Also, by way of preparation for
`
`each meeting, I would download contributions, typically all of the meeting’s
`
`contributions, and review those of interest to Samsung, and where necessary,
`
`prepare additional input to the meeting based on said review.
`
` Beginning in 2000, I acted as project manager and then as system
`
`engineer at Samsung, providing technical requirements for the team working on
`
`Samsung’s UMTS modem development. This involved scrutiny of ongoing
`
`standardization work, particularly in RAN WG1, RAN WG2, and TSG Core
`
`Network (CN) WG1, from which I would download, and assess the impact of,
`
`contributions on Samsung’s development project, ensuring that Samsung’s
`
`development team was kept informed about the latest developments as layers 2 and
`
`3 of the UMTS standard were stabilized.
`
` During this period, in addition to authoring and presenting technical
`
`contributions for the 3GPP standard, and producing technical requirements for the
`
`radio modem, I acted as Rapporteur for 3GPP Technical Reports covering User
`
`
`
`6
`
`Ex.1005
`APPLE INC. / Page 6 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`Equipment (“UE”) capability requirements (3GPP TR 21.904) from 1999–2000,
`
`and the Evolution of the 3GPP System (3GPP TR 21.902) in 2003 (the first Study
`
`Item to consider the 3GPP system beyond UMTS towards LTE/EPS).
`
`
`
`In 2005, I became Head of Advanced Technologies, Standards and
`
`Regulation (ATSR) at Samsung. In addition to my managerial duties which
`
`included responsibility for standards, research, and regulatory engineers including
`
`three standards engineers who were regularly attending RAN WG2 and Core
`
`Network and Terminals (CT) WG1 Working Groups, I personally continued to
`
`work on 3GPP standardization issues. From 2005 until 2008, I regularly attended
`
`and participated in SA WG2 meetings, and from 2008 until 2011 I regularly
`
`attended and participated in SA WG1 meetings. I also attended SA plenary
`
`meetings from 2008 until I left Samsung in 2013. As well as generating
`
`contributions in support of Samsung’s research and development as preparation for
`
`each meeting, I would download and review documents from other 3GPP
`
`members, identifying those of interest to Samsung and, where necessary, preparing
`
`additional contributions on behalf of Samsung. The work required a sound working
`
`knowledge of the broader 3GPP system to ensure effective management of the
`
`ATSR team, effective participation in meeting discussions, expert assessment of
`
`third-party standards contributions, and provision of implementation guidance to
`
`Samsung developers.
`
`
`
`7
`
`Ex.1005
`APPLE INC. / Page 7 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
` From 2006 until I stopped attending SA WG1 meetings in 2011, I
`
`authored and presented over 100 contributions to SA WG2 and SA WG1 meetings
`
`at 3GPP and appeared as an author/co-author on 18 patent applications related to
`
`User Equipment operation in the IMS and the 3GPP Core Network.
`
`
`
`In 2011, I became Director of Standards and Industry Affairs at
`
`Samsung, and in November of that year I was elected to the Board of ETSI on
`
`which I served for a term of 3 years until November 2014.
`
` My company Bishop Communications Ltd is a member of ETSI, and
`
`as part of various projects undertaken, I have continued to regularly access the
`
`3GPP and ETSI document servers, and to keep abreast of 3GPP and ETSI
`
`document handling practices.
`
` Through my extensive work on 3GPP standardization issues, I have
`
`become very familiar with 3GPP’s practices relating to making final specifications,
`
`draft standards, and standards-related contributions publicly available.
`
` For the purposes of my analysis in this declaration, I have been
`
`informed by counsel that a person of ordinary skill in the art (“POSITA”) in the
`
`field of the ’502 Patent in the 2017 timeframe, would include someone who had a
`
`Bachelor’s degree in electrical engineering, computer engineering, computer
`
`science, or equivalent training, and at least 2 - 3 years of technical experience
`
`working in the field of cellular telecommunication, including experience designing
`
`
`
`8
`
`Ex.1005
`APPLE INC. / Page 8 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`or implementing 4G / 5G networks. Moreover, I recognize that additional
`
`education may substitute for some of the experience, and experience may
`
`substitute for educational background.
`
`III. PUBLIC AVAILABILITY OF 3GPP STANDARDS PROPOSALS
`AND TDOCS
`
` Based on my years of experience working in various capacities on
`
`3GPP standards issues, I am familiar with the regular business practices of the 3rd
`
`Generation Partnership Project (“3GPP”) relating to technical documents including
`
`how 3GPP makes these documents public.
`
`a. Prominence and Purpose of 3GPP
`
`
`
`3GPP was inaugurated in December 1998 to produce Technical
`
`Specifications and Technical Reports for the Universal Mobile
`
`Telecommunications System (UMTS), a 3G Mobile System based on evolved
`
`GSM core networks and a new radio access network known as UTRA (UMTS
`
`Terrestrial Radio Access). Ex.1101 at 238. At that time, various standards
`
`organizations agreed to cooperate to produce a complete set of globally applicable
`
`Technical Specifications for the next 3G standard that would then be transposed
`
`into standards by regional standardizations bodies.
`
`
`
`3GPP is a partnership between organizational partners, market
`
`representation partners, and individual members such as companies. Ex.1106 at 4-8
`
`
`
`9
`
`Ex.1005
`APPLE INC. / Page 9 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`(3GPP Working Procedures, 2000). By January 2000, there were 284 companies
`
`participating as members of 3GPP. Ex.1101, 241. And by 2017, there were 583
`
`members. Ex.1112, 10.
`
`
`
`3GPP produces technical standards covering cellular
`
`telecommunications networks, including User Equipment or Mobile Device (UE)
`
`technologies, Radio Access Network (RAN) technologies, Core Network (CN)
`
`technologies, and service and system capabilities. Beginning in 1998 and
`
`continuing through today, POSITAs were tracking the developments of the latest
`
`3GPP specifications and reports to ensure that the standards being developed were
`
`in line with the technologies being developed by their employers, and vice-versa. It
`
`is my opinion that a POSITA in cellular communications would have to be familiar
`
`with 3GPP and the specification-related documents in order to properly perform
`
`their job. Indeed, even from the early days of 3GPP, textbooks and articles about
`
`cellular communications commonly directed readers to the 3GPP website for
`
`information regarding standards development. Ex.1101, 246; Ex.1107, 37. As a
`
`POSITA in cellular communications myself by 1999, I would regularly visit and
`
`refer others to the 3GPP website for the latest developments in 3G and have
`
`continued to do so since that time for the evolution and subsequent generations of
`
`mobile communications systems.
`
` My personal experience at Samsung confirms 3GPP’s prominence as
`
`
`
`10
`
`Ex.1005
`APPLE INC. / Page 10 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`the preeminent mobile communications specifications setting body even from
`
`shortly after its inauguration when engineers and managers at Samsung responsible
`
`for developing 3G modem software (but not attending 3GPP meetings) would
`
`regularly ask me about which release(s) or version(s) of given 3GPP specifications
`
`they should be developing their products. By June 2017, its preeminence had long
`
`since been secured and there were 5 billion subscribers to systems employing the
`
`GSM family of technologies specified by 3GPP. E.g., Ex.1111, Ex.1110.
`
`b. 3GPP’s Policy of Making Documents Public
`
`
`
`3GPP’s policy has always been to make 3GPP documents available to
`
`the public. Because the purpose of 3GPP was worldwide adoption of a common
`
`standard, no restrictions on distribution or discussion were placed on 3GPP
`
`documents, but rather the dissemination and sharing of 3GPP documents was
`
`specifically encouraged and necessary for creating an industry-wide standard.
`
`Ex.1108, 8 (“No password is needed to access any information on the 3GPP Web
`
`site, all information is openly published.”).
`
`c. 3GPP Structure and Standards Development Process
`
` Within 3GPP, responsibility for producing specifications has always
`
`been delegated to Technical Specification Groups (TSGs). Ex.1106, 11. At its
`
`inception, 3GPP was divided into four Technical Specification Groups (TSGs),
`
`each covering a particular category of technology, one such TSG being the Radio
`
`
`
`11
`
`Ex.1005
`APPLE INC. / Page 11 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`Access Network (RAN). POSITAs will be aware of the division of work by subject
`
`matter among the TSGs and among the Working Groups (WGs) within each TSG.
`
`Ex.1102, 175–76; Ex.1103, 46 (Figure 4.3 showing division of work by subject
`
`matter among RAN WGs in 2001). In the 2017-2018 timeframe, there remained
`
`three Technical Specifications Groups each comprising a number of Working
`
`Groups (WGs). Ex.1109. Each WG also focusses on particular subject matter, and
`
`the majority of the standards-development work is conducted at the WG level in
`
`regular (approximately bi-monthly) meetings. Ex.1101, 243. In addition,
`
`particularly at times when major new technologies are being defined, ad hoc
`
`meetings are sometimes held that focus only on those technologies, e.g., LTE, 5G
`
`New Radio (“5GNR” or just “NR”). A description of each Working Group’s
`
`technology area can be found on the Working Group home pages on the 3GPP
`
`website. See, e.g., Ex.1116 (RAN WG2 Homepage). For example, RAN WG2
`
`(also called “RAN2” or “R2”) was and remains “in charge of the Radio Interface
`
`architecture and protocols (MAC, RLC, PDCP)” including “the specification of the
`
`Radio Resource Control (RRC) protocol.” Ex.1116, 1.
`
` The Working Groups meet regularly. The attendees (also called
`
`“delegates”) at these meetings are engineers representing telecommunications
`
`companies from around the world, including Nokia, Samsung, AT&T, Ericsson,
`
`Qualcomm, and Huawei among others. Ex.1115. RAN Working Group 2 meetings
`
`
`
`12
`
`Ex.1005
`APPLE INC. / Page 12 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`often had around 300 delegates in attendance in 2017 - 2018. Ex.1115, (listing 295
`
`delegate participants at RAN WG2 Meeting #101). The vast majority of these
`
`delegates were and would have represented POSITAs.
`
` Although attendance at 3GPP meetings was generally limited to 3GPP
`
`members, the public, including POSITAs, would have been made aware of
`
`Working Group meeting dates and times as well as the technical documents it
`
`produced on 3GPP’s website. Ex.1116 (archived RAN WG2 page having links to
`
`meeting information, email exploder lists, and technical documents); Ex.1114
`
`(3GPP Calendar page). Interested POSITAs would have been well aware of the
`
`meeting information pages for each TSG Working Group in 2017 - 2018.
`
`d. 3GPP Documents – TDocs
`
` The technical specifications and reports developed by 3GPP were and
`
`are driven by the technical contributions of 3GPP member companies. As part of
`
`that development process, various types of documents are produced. As relevant to
`
`this case, the 3GPP process involves the consideration of temporary documents or
`
`“TDocs,” which are also referred to as proposals, contributions, or change requests.
`
`TDocs result in the production of technical specifications.
`
` Prior to each Working Group meeting, members of the Working
`
`Group prepare TDocs to e.g., identify, discuss, and/or propose a new feature or
`
`change(s) to an existing feature or to identify a technical issue for discussion.
`
`
`
`13
`
`Ex.1005
`APPLE INC. / Page 13 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`POSITAs will know that TDocs can be a helpful source of technical information
`
`regarding the 3GPP specifications. Ex.1102, 175 (textbook explaining that “[o]ne
`
`way to find a more detailed description of the specific methodology or parameter
`
`in the specification is to go through the contribution papers (called technical
`
`documents, or tdocs) that 3GPP uploads on their meeting website”).
`
` Each TDoc is assigned a TDoc number, according to a standard
`
`format set by 3GPP.1 As described in the 3GPP Working Procedures from 2016,
`
`the numbering system followed the format xminnzzzz. Ex.1113,19-20. This is the
`
`same format that has been in use since 1999. Within the format, “x” referred to the
`
`relevant TSG. For example, “R” was used for TSG RAN. Likewise, “m” referred
`
`to the relevant Working Group. Ex.1113, 20. A document for RAN WG2 would
`
`therefore begin with “R2.” Ex.1113, 20. The two digits “nn” represented the year
`
`(e.g., 17), and the digits “zzzz” represented the unique document number2.
`
`Ex.1113, 20.
`
` Each TDoc would include in its header the meeting at which the
`
`contributor intended the TDoc to be discussed. Most TDocs were uploaded to the
`
`
`
`1 Some documents other than technical contributions (such as meeting reports)
`were also assigned TDoc numbers, for ease of reference.
`
`2 In 1999 there were three ‘z’ digits, increasing to four in 2000. A fifth ‘z’ digit
`was added by RAN Working Group 2 from 2017 to cater for the increasing number
`of TDocs being submitted each year.
`
`
`
`14
`
`Ex.1005
`APPLE INC. / Page 14 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`3GPP website for public viewing prior to the relevant Working Group meeting
`
`listed on the TDoc, although some TDocs, including those created during
`
`meetings, were uploaded during or after the meeting. Ex.1108, 9. Specifically,
`
`“TDoc numbers start to be allocated some weeks before a 3GPP meeting, and the
`
`authors then create [the TDocs] and they or the group’s secretary uploads them to
`
`the public file server as soon as possible.” Ex.1108, 9 (emphasis added). The
`
`documents were uploaded to the public file repository in an area allocated to the
`
`particular Working Group. Ex.1116 (RAN WG2 Homepage with link to WG2’s
`
`“Meeting documents”). Immediately upon upload, any member of the public could
`
`download and access the TDocs and other documents offered for discussion. This
`
`is the process that POSITAs have known to be in place for decades which has been
`
`in place since I began attending Working Group meetings in 1999.
`
`e. Distribution over the 3GPP Listserv
`
` An important means of distributing draft specifications and other
`
`information to 3GPP members, interested POSITAs, and interested members of the
`
`public was through the 3GPP email listservs (also referred to as the “email
`
`exploder” or “email reflector”). All TSGs and Working Groups, including TSG
`
`RAN, RAN WG1, and RAN WG2, have listservs corresponding to their groups.
`
`Each listserv acts as an email alias that distributes emails and email attachments
`
`sent to that alias to every person subscribed to that listserv.
`
`
`
`15
`
`Ex.1005
`APPLE INC. / Page 15 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
` Subscribing to a listserv was simple and was open to any member of
`
`the public—not just 3GPP members. Ex.1146. The email listservs were featured
`
`prominently on 3GPP’s Specification Groups page and could be accessed via the
`
`“Email Lists” link. Ex.1145. That link would take a user to a page providing
`
`instructions to subscribe to and access the list of ETSI email listservs including
`
`those for 3GPP. Ex.1146. It is my opinion that the 3GPP email listservs were well
`
`known among persons interested in following or participating in the development
`
`of wireless cellular standards. Ex.1101, 240 (textbook noting that “[g]iven that
`
`3GPP has participants from all over the world, the use of the Internet, email
`
`exploders [i.e., listservs] and other such facilities have proved invaluable for
`
`distributing and sharing information, working drafts and so on”); Ex.1105, Section
`
`5 (“The vast majority of the technical discussions and decision making in both
`
`IETF and 3GPP is done over mailing lists. … It is recommended that interested
`
`individuals subscribe to and participate in these lists.”).
`
` There were hundreds of subscribers (and often over a thousand) to the
`
`RAN WG1 and RAN WG2 listservs. Ex.1144. The people that subscribed were
`
`typically engineers, such as me, but also technology strategists and technical
`
`managers. The subscriber list typically included at least all those persons who
`
`planned to attend an upcoming meeting where a TDoc may be discussed. The
`
`typical practice among people who were to attend an upcoming meeting was to use
`
`
`
`16
`
`Ex.1005
`APPLE INC. / Page 16 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`the WG’s listserv to review and discuss opinions about the ideas conveyed in
`
`TDocs. The email listserv for RAN WG2 provided an efficient way for
`
`contributors to quickly and efficiently disseminate their views. The number of
`
`subscribers for a particular WG listserv usually far exceeded the number of people
`
`attending those WG meetings. For example, 295 delegates attended RAN WG2
`
`Meeting #101, whereas the RAN WG2 email list had around 1000 subscribers
`
`between 2012 and 2021. See, e.g., Ex.1144, Ex.1143.
`
` No confidentiality limitations or restrictions on further dissemination
`
`were placed on documents distributed via the listservs. Ex.1108, 9 (“This
`
`distribution on the group’s email exploder is important, because once that happens,
`
`the document is effectively in the public domain, since membership of the exploder
`
`is open to all and is (almost) unpoliced.”) (emphasis added). This has been the
`
`practice and understanding since I became involved with 3GPP in 1998-1999. The
`
`listservs were also used to distribute information about upcoming TSG or WG
`
`meetings, such as invitations, draft agenda and draft reports for each meeting. E.g.,
`
`Ex.1142 (listserv emailed invitation to RAN2 meeting #101); Ex.1141 (listserv
`
`emailed draft agenda for RAN2 meeting #101); Ex.1140 (listserv email attaching
`
`draft report from RAN2 meeting #101).
`
` The listserv emails were (and remain) archived in a public online
`
`archive (available at http://list.etsi.org/scripts/wa.exe?INDEX). In my experience,
`
`
`
`17
`
`Ex.1005
`APPLE INC. / Page 17 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`this archive has existed and been accessible to POSITAs since the email lists were
`
`created in 1998. Ex.1104 (archived copy of 1998 email). Each archived email
`
`contains a computer-generated date stamp indicating when the email was sent and
`
`thereby when any attached document became publicly disclosed through
`
`distribution to listserv subscribers. The listserv archives are text searchable, and
`
`include advanced searching features. For example, and without limitation, the
`
`archives can be searched using keywords, quoted phrases, and terms and
`
`connectors (e.g., “and,” “or,” and “and not”). The archives have been text
`
`searchable since at least 2002.
`
`f. The 3GPP Website’s Public File Repository
`
` All TDocs, technical reports, and technical specifications have also
`
`always been freely available to interested POSITAs (and to any interested member
`
`of the public) through the public file repository accessible via the 3GPP website.
`
`POSITAs would have been well aware of 3GPP and of the 3GPP website. 3GPP
`
`documents were accessible to any member of the public through the 3GPP website
`
`without providing any login credentials or other exclusive access criteria.
`
`
`
`It is my opinion that, during the relevant 2017 - 2018 timeframe,
`
`POSITAs could and did locate relevant documents of interest on the 3GPP website
`
`using reasonable diligence based on the website’s indexing scheme or the TDoc’s
`
`naming convention. The documents on the 3GPP website were (and remain)
`
`
`
`18
`
`Ex.1005
`APPLE INC. / Page 18 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`organized according to the relevant Working Groups within 3GPP (each of which
`
`focused on particular subject matter) and then further organized based on the
`
`meetings of those groups. POSITAs would have known which Working Groups
`
`focused on particular subject matter.
`
` An interested POSITA (or any member of the public) could locate
`
`documents of interest by first navigating a web browser to the 3GPP website
`
`(www.3gpp.org/home.htm). For example, in the 2017 - 2018 timeframe, to locate
`
`documents from the 3GPP home page, a user could have clicked “Specification
`
`Group” and then the link to the Working Group of their choice, e.g., RAN WG2.
`
`Ex.1109; Ex.1116. The accessed page contained links to the 3GPP’s public file
`
`repository. Ex.1139. By way of an alternative to navigating to the 3GPP file
`
`repository from the 3GPP website, a user could have accessed the file repository
`
`directly through the web address www.3gpp.org/ftp. Ex.1138, or using dedicated
`
`FTP client software connecting to ftp.3gpp.org.
`
` The top two levels of indexing within the file repository are based
`
`wholly on subject matter, as reflected by the division of subject matter among the
`
`various TSGs and Working Groups. Specifically, an individual would select the
`
`relevant TSG covering the subject matter of interest:
`
`
`
`19
`
`Ex.1005
`APPLE INC. / Page 19 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`Ex.1138. If the individual were interested in the radio access aspects of 3GPP, they
`
`would click “tsg_ran.” From there, the individual would click on the particular
`
`RAN Working Group covering the subject matter of interest:
`
`
`
`
`
`20
`
`Ex.1005
`APPLE INC. / Page 20 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`
`
`Ex.1137. For example, if the individual were interested in the Radio Interface
`
`architecture and protocols (MAC, RLC, PDCP), the specification of the Radio
`
`Resource Control protocol, the strategies of Radio Resource Management and the
`
`services provided by the physical layer to the upper layers, the individual would
`
`know to choose the folder for WG2. Ex.1139.
`
` Once a user is in the relevant Working Group folder (RAN WG2 in
`
`this example), an individual would see a list of all meetings held by RAN WG2:
`
`
`
`21
`
`Ex.1005
`APPLE INC. / Page 21 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`Ex.1139. As shown, a folder existed for each meeting. For example,
`
`“TSGR2_101” corresponds to TSG RAN WG2 Meeting #101, and the timestamp
`
`associated with the meeting #101 directory indicates that as of January 27, 2018
`
`(the date of the archive in Ex.1139), it had last been updated on September 14,
`
`
`
`
`
`22
`
`Ex.1005
`APPLE INC. / Page 22 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`2017. Ex.1139.
`
` A POSITA would know which meeting(s) would have covered
`
`particular subject matter based on the publicly available meeting agendas. E.g.,
`
`Ex.1136 (proposed agenda for RAN WG2 Meeting #101). Many POSITAs would
`
`have received the meeting agendas directly via the WG listservs Ex.1141. The
`
`meeting agendas were usually stored on the 3GPP website server within the agenda
`
`folder for each meeting. Ex.1135 (RAN WG2 Meeting #101 Folder). Further, A
`
`POSITA could ascertain what subject matter was addressed at each meeting by
`
`reviewing the draft or approved report issued after each meeting. E.g., Ex.1130
`
`(draft report of RAN WG2 Meeting #101). Such reports were also included within
`
`each meeting folder:
`
`
`
`23
`
`
`
`Ex.1005
`APPLE INC. / Page 23 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`Ex.1135.
`
`In my experience, whilst the servers used for 3GPP file repository and many of its
`
`directories have been updated since 1999, the original upload date for files
`
`including specifications has always been preserved, providing a true and accurate
`
`indication of their earliest availability for download.
`
` Once an individual navigated to the desired meeting folder, for
`
`example “TSGR2_101,” the individual could then select the “docs” folder to view
`
`the documents associated with that meeting. The documents within this folder were
`
`listed by TDoc number, and POSITAs would have known to review the summary
`
`meeting report for each meeting, as well as the email listserv, to determine what
`
`topics were discussed at that meeting. Ex.1134; Ex.1140; Ex.1133 (list of TDocs
`
`submitted to RAN WG2 #101); Ex.1133 (ftp directory listing for RAN WG2 #101
`
`TDocs list). It was common knowledge that a list of TDocs existed and that it
`
`could be used to identify relevant TDocs. In the TDocs list, each TDoc was listed
`
`by TDoc number, title (reflecting subject matter), source (i.e., the party who
`
`contributed the TDoc), as well as the agenda item that TDoc related to and other
`
`parameters. Ex.1132. For example, the end of meeting (“eom”) TDocs list for from
`
`RAN WG2 Meeting #101 indicates that some 2405 documents were submitted for
`
`that meeting. Thus, a POSITA could narrow the set of relevant TDocs to those of
`
`interest based on the categorization of the TDoc by agenda item. It was also well
`
`
`
`24
`
`Ex.1005
`APPLE INC. / Page 24 of 41
`
`

`

`
`
`Declaration of Craig Bishop
`Inter Partes Review of 10,791,502
`
`known to POSITAs that a list of TDocs for a particular Working Group meeting
`
`was accessible via on the 3GPP website.
`
`

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