throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`LIVE NATION ENTERTAINMENT, INC.,
`Petitioner
`v.
`SONGKICK.COM B.V.,
`Patent Owner
`____________
`
`Case PGR2017-00038
`Patent 9,466,035
`____________
`
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`37 C.F.R. § 42.207
`
`
`
`
`
`
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`TABLE OF CONTENTS
`

`
`I. 
`
`INTRODUCTION .................................................................................. 1 
`
`II.  FACTUAL BACKGROUND ................................................................. 2 
`
`A.  Economic Context of Electronic Event-Ticket Sales .......................... 2 
`
`B.  Developments in Anti-Bot Technology ............................................... 7 
`
`1.  Compaq Computer’s U.S. Patent No. 6,195,698, filed in 1998 ....... 8 
`
`2.  Reshef et al. U.S. Patent Publication No. 2005/0114705, first filed
`
`in 1997
`
`9 
`
`C.  Recent Developments in Electronic Event-Ticket Sales ................... 11 
`
`1.  McEwen U.S. Patent Publication No. 2016/0078370 .................... 11 
`
`2.  Scarborough U.S. Patent Publ’n. No. 2015/0066546 ..................... 15 
`
`3.  Shivakumar U.S. Patent Publ’n. No. 2015/0134371 ...................... 21 
`
`III.  THE PATENTED INVENTION .......................................................... 23 
`
`A.  Overview of the ’035 Patent .............................................................. 23 
`
`B.  Claims of the ’035 Patent ................................................................... 26 
`
`IV.  PROSECUTION HISTORY OF THE ’035 PATENT AND ’811
`
`PATENT 27 
`
`ii
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`A.  Allowance of ’035 Patent .................................................................. 27 
`
`B.  Similarity between Claims of ’035 Patent and ’811 Patent ............... 29 
`
`C.  Third-Party Submission during Prosecution of ’811 Patent .............. 31 
`
`D.  Examiner Interview during Prosecution of ’811 Patent .................... 32 
`
`E.  Examiner’s Reasons for Allowing ’811 Patent ................................. 33 
`
`V.  ALL GROUNDS SHOULD BE DENIED UNDER SECTION 325(d)
`
`
`
`35 
`
`A.  Section 325(d) Applies to Third-Party Submissions Previously
`
`Presented to the Office in Related Applications .................................................. 36 
`
`B.  Section 101 Ground Based on FairWarning Was Previously
`
`Presented 37 
`
`C.  Section 103 Ground Based on Scarborough Was Previously
`
`Presented 41 
`
`VI.  PETITION SHOULD BE DENIED UNDER SECTION 324(a) ......... 43 
`
`A.  Claim Construction ............................................................................ 43 
`
`1.  “receiver” ........................................................................................ 43 
`
`2.  “login” ............................................................................................. 43 
`
`3.  “tagging…” and “linking…” .......................................................... 44 
`
`iii
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`4.  “real-time” ...................................................................................... 44 
`
`5.  “flag” ............................................................................................... 44 
`
`B.  Ground 1: Patent Eligibility of Claims 1-19 under FairWarning .... 44 
`
`C.  Ground 2: Obviousness of Claims 1, 4-9, 12-16, and 19 based on
`
`Scarborough and McEwen ................................................................................... 47 
`
`1.  Claims 1, 4-9, 12-16 Implicitly Require Two Partitions ................ 47 
`
`2.  Scarborough Does Not Teach the ’035 Patent’s Two Partitions .... 48 
`
`3.  McEwen Does Not Teach the ‘035 Patent’s Two Partitions .......... 52 
`
`4.  A Combination of Scarborough and McEwen Does Not Teach the
`
`’035 Patent’s Two Partitions ............................................................................ 54 
`
`D.  Ground 3: Obviousness of Claims 2, 3, 10, 11, 17, and 18 based on
`
`Scarborough, McEwen, and Shivakumar ............................................................ 55 
`
`VII.  CONCLUSION .................................................................................. 56 
`
`
`
`
`
`
`
`iv
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Ex. No.
`
`
`
`Preliminary Response
`
`EXHIBIT LIST
`
`
`
`Description
`
`2001
`
`2002
`
`2003
`
`2004
`
`2005
`
`2006
`
`2007
`
`2008
`
`2009
`
`U.S. Patent No. 9,639,811 (the “’811 patent”)
`
`Prosecution History of U.S. Patent App. No. 15/099,750, which
`issued as the ’811 patent
`
`U.S. Patent No. 8,578,500 (“the ’500 patent”)
`
`Dean Budnick & Josh Baron, Ticket Masters: The Rise of the
`Concert Industry and How the Public Got Scalped (2011), p. 229.
`
`Federal Bureau of Investigation press release: Three Plead Guilty in
`“Wiseguys” Scheme to Purchase 1.5 Million Premium Tickets to
`Events Through Computer Hacking and Fraud (2012),
`https://archives.fbi.gov/archives/newark/press-
`releases/2010/nk111810.htm (last visited October 17, 2017).
`
`United States of America v. Kenneth Lowson, et al., 2:10-cr-00114-
`KSH, D.N.J, Indictment, filed February 23, 2010.
`
`Jason Koebler, The Man Who Broke Ticketmaster (Feb. 2017), Vice
`Magazine, available at
`https://motherboard.vice.com/en_us/article/mgxqb8/the-man-who-
`broke-ticketmaster (retrieved October 17, 2017).
`
`Kim Zetter, Wiseguys Plead Guilty in Ticketmaster Captcha Case
`(November 19, 2010), WIRED,
`https://www.wired.com/2010/11/wiseguys-plead-guilty/(retrieved
`October 17, 2017).
`Hayley Tuskayama, The Switch: The Surprising Tools Bots Use To
`Get Around Those Pesky Captchas (June 9, 2016), The Washington
`Post, available at https://www.washingtonpost.com/news/the-
`switch/wp/2016/06/09/the-surprising-tool-bots-use-to-get-around-
`those-pesky-captchas/?utm_term=.69e1ac980514 (retrieved October
`17, 2017
`
`v
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`2010
`
`2011
`
`2012
`
`2013
`
`2014
`
`2015
`
`2016
`
`Biz Carson, Meet the Startup That Kept Scalpers From Buying Up
`All the Tickets to Adele’s Sold-Out Show (December 20, 2015),
`BUSINESS INSIDER, http://www.businessinsider.com/songkick-
`helps-adele-sell-tickets-2015-12 (retrieved October 17, 2017).
`
`Talk of the Town, December 16, 2015 blog entry,
`http://talktown.blog.myajc.com/2015/12/16/5-things-to-remember-
`when-buying-adele-tickets/, (retrieved October 17, 2017).
`
`Andrew Flanagan, Ticketmaster's President Delivered a Morale-
`Boosting Memo in the Wake of Adele Disappointments (December
`18, 2015), BILLBOARD,
`http://www.billboard.com/articles/business/6813819/ticketmaster-
`ceo-memo-adele (retrieved October 17, 2017).
`
`Adrienne Green, Adele Versus the Scalpers (December 21, 2015),
`The Atlantic,
`https://www.theatlantic.com/business/archive/2015/12/adele-
`scalpers/421362/ (retrieved October 17, 2017).
`
`Stuart Dredge, Despite Privacy Scare, Adele Smashes Secondary
`Ticket Market (December 2, 2015), MUSIC ALLY,
`http://musically.com/2015/12/02/despite-privacy-scare-adele-
`smashes-secondary-ticketing-market/ (retrieved October 17, 2017).
`
`Record of the Day press release: Music Industry Innovation Saves
`UK Adele Fans £4.2m (2015),
`https://www.recordoftheday.com/news-and-press/music-industry-
`innovation-saves-uk-adele-fans-42m (last visited October 17, 2017).
`
`Record of the Day editorial: Adele and Songkick’s partnership
`appears to have produced remarkable success in reducing secondary
`ticketing, David Balfour suggests. We’re not remotely surprised
`therefore that some want to portray it as a failure (2015),
`https://www.recordoftheday.com/news-and-press/adele-songkick-
`produced-remarkable-success-or-failure (retrieved October 17,
`2017).
`
`vi
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`2017
`
`CAPTCHA, Wikipedia, the free encyclopedia,
`https://en.wikipedia.org/wiki/CAPTCHA#cite_note-:0-3 (retrieved
`on October 17, 2017).
`
`vii
`
`

`

`I.
`
`INTRODUCTION
`
`Songkick.com B.V. (“Patent Owner”) files this preliminary response to the
`
`post-grant review petition (Paper 1) filed by Live Nation Entertainment, Inc.
`
`(“Petitioner”) against U.S. Patent No. 9,466,035 (“the ’035 patent”). For reasons
`
`explained herein, the petition should be denied under 35 U.S.C. § 325(d) as relying
`
`on the “same or substantially the same prior art or arguments previously …
`
`presented to the Office,” in a 41-page Third-Party Submission during prosecution
`
`of the ’035 patent’s direct child application (Ex. 2002 pages 57-97), or
`
`alternatively denied under 35 U.S.C. § 324(a) as failing to meet the threshold for
`
`institution for substantially the same reasons the Examiner gave in an extensive,
`
`12-page Notice of Allowability explaining in detail why the Third Party’s proposed
`
`§ 101 rejection based on FairWarning and proposed § 103 rejection based on
`
`Scarborough were not adopted. (Ex. 2002 pages 8-23.)
`
`In its petition, Petitioner does not even acknowledge the previous Third-
`
`Party Submission (which contains language carried-over verbatim into the
`
`petition), much less does Petitioner specifically point out any errors in the
`
`Examiner’s Notice of Allowability. Petitioner, therefore, has failed to meet its
`
`“initial burden” with respect to previously-considered art and arguments under
`
`§ 325(d), such that the Examiner’s findings may be “treated as undisputed fact,”
`
`according to an expanded panel of the Board (that included the Chief Judge). See
`
`1
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Ziegmann v. Stephens, IPR2015-01860, Paper 13, at slip op. 10 (PTAB Sept. 6,
`
`2017) (Ruschke, Boalick, Kim, DeFranco, Mayberry, JJ.) (“[W]hen a prior art
`
`reference presented in a petition was already considered substantively by the
`
`Examiner, the petitioner has the initial burden to identify such errors made by the
`
`examiner with respect to that prior art reference. Any factual finding made by the
`
`examiner and not contested by the petitioner may be treated as undisputed fact for
`
`the purposes of evaluating petitioner’s assertions concerning examiner error under
`
`Section 325(d).”) (citations omitted) (emphases added).
`
`II. FACTUAL BACKGROUND
`
`A. Economic Context of Electronic Event-Ticket Sales
`
`Ticketweb sold the first ticket via the internet in 1995. The following year,
`
`Ticketmaster sold their first ticket online. As Ticketmaster’s SVP of New Media,
`
`Alan Citron, said of the time, “There was this joke that would go around the office
`
`that you don’t want to find out that, for the first on-sale that occurs on the internet,
`
`some kid named Skippy has gotten hold of all the tickets. There was always the
`
`threat hanging in the air. So we had to make sure this thing could not be hacked.”
`
`(Ex. 2004 para 2.)
`
`Evidence of how brokers would go on to take advantage of Ticketmaster’s
`
`online ticket sales can be found in the aftermath of a federal indictment filed
`
`2
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`against Wiseguys Tickets in 2010. The Wiseguys’ business model was to
`
`“wholesale” the tickets they procured to a vast network of brokers. The brokers
`
`were willing to pay Wiseguys Tickets more than the face value of the tickets,
`
`because the tickets could be resold to the public at even greater prices. (Ex. 2005
`
`para 7.)
`
`As the indictment notes, “Because the Event Agreements required Online
`
`Ticket Vendors to sell tickets on a first-come, first-served basis, Online Ticket
`
`Vendors invested millions of dollars in technology that created virtual ‘queues’ to
`
`serve would-be Internet purchasers in the order they arrived. On these systems,
`
`how quickly an on-line purchaser reached the virtual queue would determine which
`
`tickets that user could purchase, or whether the user could purchase tickets at all.”
`
`(Ex. 2006 §1:i.)
`
`Early on, Wiseguys became aware that the webpage at which to purchase
`
`tickets for a given event would load in staggered fashion based on geography,
`
`meaning that the sale for an event would start for customers at slightly different
`
`times depending on from where they were trying to connect. The difference in start
`
`times was only one of several seconds, but those critical few seconds was all it
`
`took to give Wiseguys an outsized advantage. The company rented 30 servers
`
`spread across the country in order to exploit this loophole, guaranteeing that at
`
`3
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`least a portion of their connections would consistently occur within the first
`
`seconds of the onsale. (Ex. 2007 pages 3-7.)
`
`By the early 2000s, Ticketmaster and other online ticketing providers were
`
`regularly implementing CAPTCHA (“Completely Automated Public Turing test to
`
`tell Computers and Humans Apart”) in an attempt to reduce the increasingly
`
`aggressive efforts of scalpers. CAPTCHA typically asked the customer to correctly
`
`transcribe the letters of a word displayed on screen in a distorted image before
`
`being allowed to search for tickets. The belief was that while CAPTCHA would
`
`make it slower for customers to purchase their tickets, it would prevent the
`
`automated programs that were becoming increasingly common from speeding
`
`through the purchase process vacuuming up large quantities of tickets before
`
`customers had a chance. Automated programs, or bots, could be programmed to
`
`follow all of the standard steps necessary to search for and purchase tickets much
`
`faster than a human user ever could hope to, enabling scalpers to harvest huge
`
`amounts of tickets with minimal investment. (Ex. 2008.)
`
`However, as CAPTCHA technology advanced, so did scalpers’ technology.
`
`Pretty soon scalpers began using a technology called Optical Character
`
`Recognition (“OCR”) to overcome more complex instances of CAPTCHA. OCR
`
`converts images of typed, handwritten or printed text into machine-encoded text.
`
`This technology was then connected to bots that could request thousands of tickets
`
`4
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`within a minute, regardless of how many tens of thousands or millions of distorted
`
`images were in a ticketing company’s CAPTCHA library.
`
`Human intervention also helped defeat CAPTCHA. For example, “the Bots
`
`transmit in real-time images of the CAPTCHAs they encounter on Ticketmaster
`
`and other sites to armies of ‘typers,’ human workers in foreign countries where
`
`labor is less expensive. These typers—employed by companies such as Death by
`
`CAPTCHA, Image Typerz, and DeCaptcher—read the CAPTCHAs in real-time
`
`and type the security phrases into a text box for the Bot to use to bypass ticket
`
`vendors’ defenses and use their sites.” (Ex. 2009)
`
`And, while all bots are undesirable purchasers, not all undesirable
`
`purchasers are bots, and therefore undesirable purchasers continued to be
`
`problematic.
`
`Patent Owner’s unique solution, which was conceived after its experience
`
`working with scores of frustrated clients, including Paul McCartney, Ed Sheeran,
`
`Red Hot Chili Peppers, Lady Antebellum, Eric Church, Jack Johnson and Keith
`
`Urban, addressed both human and non-human undesirable purchasers.
`
`Patent Owner launched its own solution in November of 2015 for Adele,
`
`whose last album was the fastest selling album in recorded music history. After a
`
`five-year hiatus from performing in concert and innumerable sales records broken,
`
`Adele returned to the stage. It was clear that despite the large number of concert
`
`5
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`dates to which she committed, there was no way she would be able to satiate
`
`demand. At the same time, she wanted to keep ticket prices reasonable, in order to
`
`not alienate her broad fan base. (Ex. 2010. ; Ex. 2011.)
`
`And, demand there was. Ticketmaster’s President, North America, reported
`
`that Adele’s ticket sales generated “easily an all-time record” in terms of traffic,
`
`with “10 million+ fans rushing to our site”. (Ex. 2012.) As well, many millions
`
`purchased tickets to her shows across Europe and in her home country of Britain,
`
`where Patent Owner handled the majority of ticket sales for Adele. Due to Patent
`
`Owner’s new technology, tickets to Adele’s tour went overwhelmingly to the fans
`
`that had waited years for her to return to the stage, not to scalpers. The Atlantic
`
`reported that, “as a result of [Patent Owner’s] efforts, more Adele fans were able to
`
`buy their tickets at normal prices instead of the exorbitant fees scalpers (or “touts”
`
`as British people call them) charge.” (Ex. 2013.) Trade publication, MusicAlly,
`
`surveyed the amount of tickets on the re-sale market for Adele versus other high-
`
`profile acts whose sales occurred in the same period, reporting that the “figures
`
`were startling”: “the average number of secondary tickets per Coldplay gig was
`
`2,939, compared to 1,548 for Rihanna and just 54 for Adele.” (Ex. 2014.) Chris
`
`Carey, the CEO of Media Insight, a consulting firm, found that Patent Owner’s
`
`“music industry innovation saves UK Adele Fans £4.2m.” (Ex. 2015.) Prestigious
`
`UK music business daily, Record of the Day, wrote:
`
`6
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`“We’d like to see some greater transparency/detail released by [Patent
`
`Owner] around this ‘tout-finding’ process. This is not because we question the
`
`company’s morals or methodologies. It’s more because [Patent Owner] has just
`
`done more in one campaign to address the issue of touting than has been achieved
`
`to date by any other party in any other sector. Further detail would be eagerly
`
`received.” (Ex. 2016.)
`
`Adele would go on to perform more than 100 shows, and add four farewell
`
`shows at Wembley Stadium in her hometown of London, as a gift to fans. In all,
`
`Patent Owner sold nearly 500,000 tickets to Adele’s fans, and saw approximately
`
`only 2% of these tickets only appear on the re-sale market. Seeing the impact of
`
`Patent Owner’s patented technology, other artists, including Katy Perry and Jack
`
`Johnson began to use it for their ticketing.
`
`B. Developments in Anti-Bot Technology
`
`Internet users have long wanted to prevent computers from “reading” text. A
`
`primitive technique was to replace a word with look-alike characters. HELLO
`
`could become |‐|3|_|_() or )‐(3££0, as well as numerous other variants.
`
`One of the earliest commercial uses of CAPTCHAs was in the Gausebeck-
`
`Levchin test. In 2000, idrive.com began to use CAPTCHA in connection with a
`
`signup page. In 2001, PayPal used such tests as part of a fraud prevention strategy
`
`7
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`in which they asked humans to "retype distorted text that programs have difficulty
`
`recognizing." [Ex. 2017 (internal citations omitted).]
`
`1. Compaq Computer’s U.S. Patent No. 6,195,698, filed in 1998
`
`Compaq detected bots by presenting to a would-be user a “riddle” derived
`
`from a distorted and camouflaged text string on the hypothesis that only a human
`
`user could identify the source text. Compaq’s FIG. 4. showing a riddle, is
`
`reproduced below, left.
`
`Compaq’s Abstract states, in
`
`part:
`
`The string is randomly
`
`modified either visually or audibly
`
`to form a riddle. The original string
`
`becomes the correct answer to the
`
`riddle…Hopefully, the answer is a user's guess for the correct answer. The server
`
`determines if the guess is the correct answer, and if so, the access request is
`
`accepted. If the correct answer is not received within a predetermined amount of
`
`time, the connection…is terminated…on the assumption that an automated agent is
`
`operating…on behalf of the user.”
`
`8
`
`

`

`PGR2017-00038
`Patent 9,466,035
`2. Reshef et al. U.S. Patent Publication No. 2005/0114705, first
`filed in 1997
`
`Preliminary Response
`
`
`
`Reshef detects bots using its method for discriminating automatic
`
`computerized action from a human performed action. Reshef, Abstract.
`
`The method applies human advantage in applying sensory and cognitive
`
`skills to solving simple problems that prove to be extremely hard for computer
`
`software. Such skills include, but are not limited to processing of sensory
`
`information such as identification of objects and letters within a noisy graphical
`
`environment…The method for discriminating between humans and computerized
`
`actions can be used during authentication, to limit access by automated agents, and
`
`for confirmation of actions. Id.
`
`9
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Reshef FIG. 8a, below left, shows a “prior art” login web page that has only
`
`standard fields for entry of user name and PIN number. Reshef FIG. 8b, below
`
`right, shows the prior art login web page
`
`with the addition of “human ability
`
`challenge 506.” Reshef ¶ 70. Reshef
`
`states, “[i]n order for a user to gain access
`
`to a particular computer resource on
`
`application server 100, the user must
`
`provide a valid username, PIN# and an
`
`answer to human ability challenge 506. The proxy program on proxy server 106
`
`verifies that the answer provided in prompt 50S to human ability challenge 506 is
`
`correct. If the answer is verified, the proxy program allows access for client 102 to
`
`application server 100.” Id.
`
`10
`
`

`

`PGR2017-00038
`Patent 9,466,035
`C. Recent Developments in Electronic Event-Ticket Sales
`
`
`
`Preliminary Response
`
`1. McEwen U.S. Patent Publication No. 2016/0078370
`
`McEwen adopted CAPTCHA technology for identifying bot-based ticket
`
`purchase attempts in an electronic event-ticketing system. McEwen FIG. 1,
`
`reproduced at left, emphasis added,
`
`shows an overview of McEwen ticket
`
`interaction system 100, in which user
`
`105 requests tickets for an event that
`
`was established in ticket management
`
`system 150 by event-provider (a
`
`promoter or producer) 115. Ticket management system 150 is vulnerable to bot
`
`scalpers via internet 130. System 150 can store a user’s request in a “queue,” for
`
`that event, in queue database 180.
`
`McEwen provides users with an opportunity to register for the event.
`
`Registration requires completion of verification steps that are useful for
`
`discriminating between human and robot users.
`
`A user that passes the verification steps can then submit a ticket request prior
`
`to an onsale period. Para 4. Bots are less likely to pass the verification steps, and
`
`thus are less likely to be granted an opportunity to submit a ticket request prior to
`
`the onsale period (a “pre-onsale request”). This handicaps a bot user, who must
`
`11
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`not only wait until the actual onsale period, but also must still overcome the
`
`verification hurdle. See, e.g., McEwen at para 4.
`
`McEwen discloses that there can be multiple onsale periods. Each period
`
`can be open to users having different characteristics. Exemplar characteristics
`
`include “users having a credit card of a particular brand”, and the “general public.”
`
`Para 100.
`
`McEwen also can score requests based
`
`on a user’s performance during the
`
`verification steps. Para 5. McEwen ticket
`
`requestor 230 (McEwen FIG. 2, right,
`
`emphasis added), which is in direct
`
`communication with CAPTCHA Engine 235,
`
`and can generate the score. A score above a
`
`threshold can indicate that registration is
`
`complete. The score can be used for
`
`“prioritization” of one or more user ticket requests. Para 76. (Elsewhere, in para
`
`55, McEwen states that it is queue engine 245 that generates a score.)
`
`McEwen discloses a long list (below, emphasis added) of techniques that
`
`can be used for generating a score:
`
`12
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`
`
`13
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`In connection with the list, McEwen states that “the score can optionally
`
`provide more gradations of performance than a simple pass/fail indication…” For
`
`example, the score may be valued at one of at least three possible values, such as:
`
`“A,” “B,” or “C.” McEwen’s sole strictly ternary example of a “score” is: “likely a
`
`robot, likely not a robot, and indeterminate as to whether the user is a robot or not.”
`
`para 107.
`
`Among McEwen’s items for “generating a score” are:
`
`(1) Algorithm to rank users into multiple (e.g., 3) buckets; and
`
`(2) Algorithm to order users within each bucket.
`
`McEwen does not disclose how ranking into multiple buckets can be used to
`
`generate a score. McEwen does not disclose how ordering users within each
`
`bucket can be used to generate a score. McEwen does not disclose what a
`
`“bucket” is or what a “bucket” does.
`
`McEwen does disclose that different queues may be established based on a
`
`user’s pricing “preferences or restrictions,” and on a user’s seating “preferences or
`
`restrictions.” para 89.
`
`Queue engine 245 can prioritize already-approved requests. The requests
`
`can be ranked relative to each other. McEwen para 55.
`
`The requests can be placed in “prioritization groups” by comparing its score
`
`to one or more thresholds. Requests such as those associated with pre-onsale
`
`14
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`registration, stronger estimation of being human, stronger estimation of not being a
`
`threat, and reference to an event on a user social-network site can be assigned to
`
`“higher priority” groups. Para 55.
`
`Queue engine 245 can prioritize the requests based on their scores, and can
`
`assign a request to a group in a queue. In “one instance,” requests having scores
`
`below a threshold are not even added to the queue. Para 110.
`
`McEwen states that “In some instances, all pending pre-onsale requests are
`
`prioritized over all pending onsale requests within a given queue.” Para 110.
`
`2. Scarborough U.S. Patent Publ’n. No. 2015/0066546
`
`Scarborough, which is also owned by the Petitioner, discloses a “learning
`
`model” that provides an additional level of power to segregate bot-based ticket
`
`purchase attempts in an electronic event-ticketing system. Scarborough discloses
`
`heuristically changing the criteria by which a user (an “actor,” in Scarborough’s
`
`nomenclature) is determined to be a “good actor.” Scarborough Abstract. Because
`
`the model is “dynamic,” Scarborough, Title, the model “can make it difficult for
`
`actors to understand what attributes are being currently favored.” Scarborough
`
`para 5. Good actors may be provided with preferential opportunities to purchase
`
`tickets. Scarborough para 5.
`
`15
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Scarborough FIG. 1, reproduced at
`
`left, emphasis added, shows an overview
`
`of Scarborough ticket interaction system
`
`100, in which actors 105 (-1 and -2)
`
`request tickets for an event that was
`
`established in ticket management system
`
`150. Ticket management system 150 is vulnerable to bot scalpers via internet 140.
`
`Scarborough FIG. 2, at right, emphasis
`
`added, shows details of Scarborough ticket
`
`management system 150.
`
`Scarborough ticket management system
`
`150 communicates with the actor via client
`
`interface engine 205.
`
`Model engine 215 evaluates attributes
`
`of each actor. Scarborough para 43. The
`
`attributes can include, for example,
`
`membership in a group, speed of responding to presentations, scar para 44, whether
`
`the actor positively responded to electronic presentation associated with the event
`
`(a Facebook “like”), Scarborough para 45, and whether an actor attended a specific
`
`event, Scarborough para 45.
`
`16
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Model engine 215 includes a learning algorithm that can detect when actors
`
`“seem to be altering their activity in an attempt to cause system 150 to falsely
`
`characterize” actors. If so, the learning algorithm can “initiate an adjustment in the
`
`characterization-assessment procedure, such that the procedure evaluates different
`
`attributes or changes weights of attributes” to properly characterize bots that learn
`
`to behave more like humans. Scarborough para 55.
`
`Scarborough good-actor detector 225 (shaded green) operates on output of
`
`model engine 215 to provide a positive estimation that an actor is a good actor.
`
`Scarborough para 56. The estimation may be a score that “reflects an estimate of
`
`an extent to which an actor possesses [a] characteristic or a confidence of the
`
`characteristic assessment made by good-actor detector 225.” Scarborough para 58.
`
`Ticket data store 240 keeps track of ticket attributes, such as availability,
`
`“on-reserve,” “on hold,” “assigned,” “purchased,” and “restricted.” Scarborough
`
`para 62.
`
`Pricing engine 230 “sets a price for each ticket” in data store 240.
`
`Scarborough para 60. “Each ticket may be associated with one or more prices
`
`(e.g., a normal price, a good-actor price and/or a bad-actor price; or a scale of
`
`prices along which a price is to be selected based on an actor characterization
`
`score)…” Scarborough para 63.
`
`17
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Pricing engine 230 does not determine good-actor status, but can “identify
`
`variations to the price” based on a good-actor status previously determined by
`
`good-actor detector 225. Scarborough para 60.
`
`Ticket engine 235 manages, updates and monitors ticket data store 240.
`
`Scarborough para 62. Scarborough FIG. 4, entirely reproduced, below right,
`
`emphasis added, shows process 400 for
`
`“biasing ticket offerings to favor good
`
`actors.” Scarborough para 111.
`
`In step 405 (“Define actor
`
`characteristic”), actor characteristic
`
`definer 210 (shown in Scarborough
`
`FIG. 2) defines an actor characteristic
`
`(such as “true fan,” “likely to attend an
`
`event,” and “estimated to be a human
`
`and not a robot”). Scarborough para
`
`111.
`
`In step 410 (“Determine characterization-assessment procedure”), model
`
`engine (shown in Scarborough FIG. 2) selects a test for the presence of the defined
`
`actor characteristic. The selection can be made to “make it difficult for actors to
`
`guess the attributes being considered.” Scarborough para 112.
`
`18
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`Steps 415 (“Determine value for each attribute for actor”) and 420 (“Perform
`
`procedure”), and decision 425 (“Actor a good actor?”), are shaded green to show
`
`that they are performed by good-actor detector 225, which is shaded green in
`
`Scarborough FIG. 2.
`
`At step 415, good-actor detector provides a value, whether binary or on a
`
`scale, for each attribute that the selected test requires. Scarborough para 113.
`
`At step 420, good-actor detector 225 performs the selected test. The outcome
`
`of the test may be a score that relates to the “performance” of the actor under test.
`
`Scarborough para 114. Based on the score, good-actor detector 225, at decision
`
`block 420, “estimates whether the actor is a good actor.” Good-actor detector 225
`
`may decide based on whether the score “exceeds a threshold in a good-actor
`
`direction.” Scarborough para 115.
`
`If good-actor detector 225 does not issue a good actor determination, ticket
`
`engine subsequently proceeds with normal protocols at step 430a (“Proceed with
`
`normal protocol”). “Normal protocols” include offering tickets in a “normal
`
`order,” in a “normal fashion,” at “normal prices” and conforming to a “normal
`
`selection of tickets.” Scarborough para 116.1
`
`
`1 The Petitioner identified a typographical error in Scarborough para 116,
`
`first sentence, and proposed to cure the error by adding the “not” between “is” and
`
`19
`
`

`

`PGR2017-00038
`Patent 9,466,035
`
`
`
`Preliminary Response
`
`If good-actor detector 225 does issue a good-actor determination, ticket
`
`engine 235 proceeds with biasing step 430b (“Bias ticket offerings to favor actor”).
`
`In the biasing, ticket engine 235 provides a bias—relative to the normal
`
`protocol. The bias may be an offer of tickets that are not available to other actors,
`
`
`“a good actor,” so that the sentence would read, “Upon estimating that actor is not
`
`a good actor, ticket engine 235 proceeds with normal protocols at block 430a.”
`
`Petitioner’s petition at 47. Patent Owner suggests that Scarborough’s teachings
`
`about good-actor detector 225 compel a different cure: viz., the addition of “not”
`
`between “upon” and “estimating,” so that the sentence would read, “Upon not
`
`estimating that actor is a good actor, ticket engine 235 proceeds with normal
`
`protocols

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