The FCC Approves an NOI to Dive Deeper into AI and its Effects on Robocalls and Robotexts

AI is on the tip of everyone’s tongue it seems these days. The Dame brought you a recap of President Biden’s orders addressing AI at the beginning of the month. This morning at the FCC’s open meeting they were presented with a request for a Notice of Inquiry (NOI) to gather additional information about the benefits and harms of artificial intelligence and its use alongside “robocall and robotext”. The following five areas of interest are as follows:

  • First, the NOI seeks, on whether and if so how the commission should define AI technologies for purposes of the inquiry this includes particular uses of AI technologies that are relevant to the commission’s statutory response abilities under the TCPA, which protects consumers from nonemergency calls and texts using an autodialer or containing an artificial or prerecorded voice.
  • Second, the NOI seeks comment on how technologies may impact consumers who receive robocalls and robotexts including any potential benefits and risks that the emerging technologies may create. Specifically, the NOI seeks information on how these technologies may alter the functioning of the existing regulatory framework so that the commission may formulate policies that benefit consumers by ensuring they continue to receive privacy protections under the TCPA.
  • Third, the NOI seeks comment on whether it is necessary or possible to determine at this point whether future types of AI technologies may fall within the TCPA’s existing prohibitions on autodial calls or texts and artificial or prerecorded voice messages.
  • Fourth, NOI seeks comment on whether the commission should consider ways to verify the authenticity and legitimately generate AI voice or text content from trusted sources such as through the use of watermarks, certificates, labels, signatures, or other forms of labels when callers rely on AI technology to generate content. This may include, for example, emulating a human voice on a robocall or creating content in a text message.
  • Lastly, seeks comment on what next steps the commission should consider to further the inquiry.

While all the commissioners voted to approve the NOI they did share a few insightful comments. Commissioner Carr stated “ If AI can combat illegal robocalls, I’m all for it” but he also expressed that he does “…worry that the path we are heading down is going to be overly prescriptive” and suggests “…Let’s put some common-sense guardrails in place, but let’s not be so prescriptive and so heavy-handed on the front end that we end up benefiting large incumbents in the space because they can deal with the regulatory frameworks and stifling the smaller innovation to come.”

Commissioner Starks shared “I, for one, believe this intersectionality is clinical because the future of AI remains uncertain, one thing is clear — it has the potential to impact if not transform every aspect of American life, and because of that potential, each part of our government bears responsibility to better understand the risks, opportunities within its mandate, while being mindful of the limits of its expertise, experience, and authority. In this era of rapid technological change, we must collaborate, lean into our expertise across agencies to best serve our citizens and consumers.” Commissioner Starks seemed to be particularly focused on AI’s ability to facilitate bad actors in schemes like voice cloning and how the FCC can implement safeguards against this type of behavior.

“AI technologies can bring new challenges and opportunities. responsible and ethical implementation of AI technologies is crucial to strike a balance, ensuring that the benefits of AI are harnessed to protect consumers from harm rather than amplifying the risks in increasing the digital landscape” Commissioner Gomez shared.

Finally, the topic around the AI NOI wrapped up with Chairwoman Rosenworcel commenting “… I think we make a mistake if we only focus on the potential for harm. We needed to equally focus on how artificial intelligence can radically improve the tools we have today to block unwanted robocalls and robotexts. We are talking about technology that can see patterns in our network traffic, unlike anything we have today. They can lead to the development of analytic tools that are exponentially better at finding fraud before it reaches us at home. Used at scale, we cannot only stop this junk, we can use it to increase trust in our networks. We are asking how artificial intelligence is being used right now to recognize patterns in network traffic and how it can be used in the future. We know the risks this technology involves but we also want to harness the benefits.”

What’s New in 5G – February 2023

The next-generation of wireless technologies – known as 5G – is expected to revolutionize business and consumer connectivity, offering network speeds that are up to 100 times faster than 4G LTE, reducing latency to nearly zero, and allowing networks to handle 100 times the number of connected devices, enabling the “Internet of Things.”  Leading policymakers – federal regulators and legislators – are making it a top priority to ensure that the wireless industry has the tools it needs to maintain U.S. leadership in commercial 5G deployments.  This blog provides monthly updates on FCC actions and Congressional efforts to win the race to 5G.

Regulatory Actions and Initiatives

Spectrum

  • The FCC grants relief to a 600 MHz licensee serving Tribal Nations, giving it more time to complete and deploy its wireless network.

    • On January 4, 2023, the FCC’s Wireless Telecommunications Bureau (“WTB”) released an Order granting a third request by Pine Cellular Phones, Inc. (“Pine Cellular”) to extend its construction deadline for one of its 600 MHz licenses by one year from January 9, 2023 to January 9, 2024.  In 2019, Pine Cellular was a winning bidder in the Broadcast Incentive Auction (Auction No. 1002) of two 600 MHz licenses.  After the licenses were awarded, the FCC prohibited the use of funding from the Universal Service Fund for equipment and services deemed to pose a national security risk.  Pine Cellular planned to rely on that now-prohibited equipment to meet its construction requirement, but it has since been unable to acquire and install compliant equipment due, in part, to global supply chain issues.  The WTB granted Pine Cellular’s request because it recognized that the only way for Pine Cellular to fulfill its construction requirement is to remove and replace all prohibited equipment in its network and that termination of the license would not facilitate the provision of wireless broadband service, particularly to the Choctaw Nation, which is covered by Pine Cellular’s license.

  • The FCC grants additional licenses for spectrum in the 2.5 GHz band for commercial wireless services.

    • The WTB released a Public Notice on January 5, 2023, announcing the grant of four additional licenses for spectrum in the 2.5 GHz band, the auction for which concluded on August 29, 2022.  A list of the licenses, sorted by licensee, is available here.  And list of the same licenses, sorted by market, is available here.

  • The FCC takes further action to enable commercial operations through spectrum sharing in the 3.5 GHz band.

    • On January 10, 2023, the WTB and Office of Engineering and Technology (“OET”) released a Public Notice approving the new Environmental Sensing Capability (“ESC”) sensor deployment and coverage plans of Federated Wireless in the 3.5 GHz band.  Federated Wireless is now authorized to operate its ESC sensors to protect federal incumbents in Alaska and must, among other things, operate in conjunction with at least one Spectrum Access System (“SAS”), which manages non-federal access to the 3.5 GHz band, that has been approved for commercial deployment.

    • In addition, the WTB and OET released a Public Notice on January 12, 2023, certifying that the SAS operated by RED Technologies SAS (“RED”) has satisfied the FCC’s testing requirements and been approved to begin its initial commercial deployment (“ICD”), subject to certain conditions.  After RED operates its ICD, it is required to submit a report, and assuming that the report is satisfactory, RED will then receive authorization to operate for a five-year term.

  • The FCC revises its framework for making public safety spectrum in the 4.9 GHz band available for commercial wireless services.

    • On January 18, 2023, the FCC released an Order and Further Notice of Proposed Rulemaking establishing rules that provide for a nationwide Band Manager for public safety operations in the 4940-4990 MHz (“4.9 GHz”) band.  The Order replaces the previous framework for the 4.9 GHz band, which allowed states to lease the spectrum to third parties, including commercial entities, through a designated statewide lessor.  The new framework will allow the Band Manager to coordinate all use of the spectrum nationwide, including by making it available for secondary, non-public safety use – such as commercial 5G wireless services – by allowing non-public safety entities to lease unused 4.9 GHz band spectrum.  The Further Notice seeks comment on implementing the new leasing framework and selecting the Band Manager.  Comments and reply comments on the Further Notice will be due 30 days and 60 days, respectively, after publication in the Federal Register.

Other Agency Actions

  • The Federal Aviation Administration proposes requirements to help foster coexistence between 5G operations in the C-band and aircraft relying on radio altimeters.

    • On January 22, 2023, a Notice of Proposed Rulemaking issued by the Federal Aviation Administration (“FAA”) was published in the Federal Register.  The Notice proposes to update the FAA’s existing Airworthiness Directive (“AD”) regarding the coexistence of licensees of spectrum in the 3.7-4.2 GHz band (“C-band”) and radio altimeters.  Specifically, the FAA proposes interference tolerance requirements for radio altimeters and requirements that all aircraft operating under its rules meet power spectral density requirements to operate in the contiguous U.S. after February 2, 2024.  The FAA has determined that radio altimeter tolerant airplanes will not experience unsafe conditions at any airport identified by the FAA as a 5G market.  It has also determined that any 5G C-band provider that maintains the mitigated actions, which are based on the power levels to which Verizon and AT&T previously agreed, will not have an effect on the safety of transport and commuter airplanes with radio altimeters that meet the interference tolerance requirements.  The FAA will assess changes in the agreed-upon power levels.  Comments on the FAA’s proposals are due February 10, 2023.

  • The Department of Defense seeks comment on developing a spectrum roadmap.

    • On January 4, 2023, the Department of Defense (“DoD”) released a Request for Information seeking input to support the development of a Next-Generation Electromagnetic Spectrum Strategic Roadmap, which Congress requested of DoD in a June 2022 letter.  Among other things, DoD requests input on its ability to use commercial systems for its operations and spectrum sharing.  The deadline for providing input is February 10, 2023 at 2:00 pm ET.

5G Networks and Equipment

  • The FCC reminds rip-and-replace funding recipients of their reporting obligations.

    • On January 11, 2023, the FCC’s Wireline Competition Bureau released a Public Notice reminding parties that receive funding from the FCC’s Reimbursement Program to remove and replace equipment that poses a national security risk of their obligation to file their Reimbursement Program spending reports.  The spending reports, which, among other things, must include a detailed accounting of the covered equipment and services that have been removed and replaced, are due by February 10, 2023.

©1994-2023 Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C. All Rights Reserved.

911 Network Reliability Deadline Approaching

Earlier this monththe FCC announced that its 2022 911 Reliability Certification System is now open for Covered 911 Service Providers to file annual reliability certifications.  The filings are due on October 17, 2022.  Failure to submit the certification may result in FCC enforcement action.

Background

In 2013, the FCC adopted rules aimed at improving the reliability and redundancy of the nation’s 911 network.  Those rules require Covered 911 Service Providers (“C9SP”) to take steps that promote reliable 911 service with respect to three network elements: circuit auditing, central-office backup power, and diverse network monitoring.  The Commission identified these three network elements as vulnerabilities following a derecho storm in 2012 that significantly impacted 911 service along the eastern seaboard.

Applicability. The rules apply to all C9SPs, which are defined as any entity that provides 911, E911, or NG911 capabilities such as call routing, automatic location information (ALI), automatic number identification (ANI), or the functional equivalent of those capabilities, directly to a public safety answering point (PSAP).

Certification. The rules require C9SPs to certify annually that they have met the FCC’s safe harbor provisions for each of these elements or have taken reasonable alternative measures in lieu of those safe harbor protections.  The certification must be made under penalty of perjury by a corporate officer with supervisory and budgetary authority over network operations.

In 2018 and 2020, the FCC sought comment on changes to the 911 reliability certification rules, but the rules have not yet been updated as a result of those proceedings.

Enforcement Against Noncompliant Providers

Last year, the FCC entered into eight consent decrees with Covered 911 Service Providers that failed to submit their reliability certifications in 2019, 2020, or both.  A Consent Decree typically requires the recipient to admit it violated an FCC rule, pay a fine to the federal government, and implement a Compliance Plan to guard against future rule violations.  These Compliance Plans required the C9SPs to designate a compliance officer, establish new operating procedures, and develop and distribute a compliance manual to all employees.

Additionally, the providers were required to establish and implement a compliance training program, file periodic compliance reports with the FCC detailing the steps the provider has taken to comply with the 911 rules, and report any noncompliance with 911 rules within 15 days of discovering such noncompliance.

Looking Forward

C9SPs have about one month to confirm compliance with the reliability rules and submit a required certification.  Based on the FCC’s enforcement efforts last year, C9SPs would be well-advised to work diligently to meet this upcoming deadline.

© 2022 Keller and Heckman LLP

NCLC Tells FCC “Callers can easily avoid making calls to telephone numbers that have been reassigned….” – But Is it That Simple?

The National Consumer Law Center is at it again.

In response to the Department of Health and Human Services’ recent letter to the FCC seeking clarity on whether the TCPA applies to texts it would like to make to alert Americans of certain medical benefits, the NCLC–an organization that nominally represents consumers, but really seems to represent the interests of the plaintiff’s bar–has filed a comment.

Unsurprisingly, the NCLC takes the position that HHS needs no relief. Government contractors are covered by the TCPA–it says–but the texts at issue in HHS’ letter are consented, so they’re fine. (Although it later clarifies that only “many” but not “all” of the enrollees whom HHS wishes to call have “probably” given their telephone numbers as part of written enrollment agreements–so perhaps not.)

Hmmmm. Feels like a trap. But we’ll ignore that for now.

The critical piece here though is what the NCLC–very powerful voice, for better or (often) worse–is telling the FCC about the effectiveness of the new Reassigned Number Database:

3. Callers can easily avoid making calls to telephone numbers that have been reassigned to someone other than the enrollee

A primary source of TCPA litigation risk has been calls inadvertently made to numbers that are no longer assigned to the person who provided consent. Courts have held the caller liable for making automated calls to a cell phone number that has been reassigned to someone other than the person who provided consent to be called.29

The Commission has implemented the Reassigned Number Database specifically to address that risk of liability, as well as to limit the number of unwanted robocalls:

The FCC’s Reassigned Numbers Database (RND) is designed to prevent a consumer from getting unwanted calls intended for someone who previously held their phone number. Callers can use the database to determine whether a telephone number may have been reassigned so they can avoid calling consumers who do not want to receive the calls. Callers that use the database can also reduce their potential Telephone Consumer Protection Act (TCPA) liability by avoiding inadvertent calls to consumers who have not given consent for the call.31

The database has been fully operational since November 1, 2021. It provides a means for callers to find out before making a call if the phone number has been reassigned. If the database wrongly indicates that the number has not been reassigned, so long as the caller has used the database correctly, no TCPA liability will apply for reaching the wrong party. 32 Thus, as long as HHS’s callers make use of this simple, readily available database, they can be confident that they will not be held liable for making calls to reassigned numbers.

While I steadfastly support both the creation and use of the RND, it also must be observed that there are myriad problems with the RND as it currently exists. Most importantly, the data sets in the RND are only comprehensive through October 1, 2021 and spotty back to February, 2021 (beyond which there are no records!)

So for folks like HHS–and servicers of mortgages, and retailers, and credit card companies–who want to reach customers who provided their contact information before 10/2021 or 2/2021 the RND is simply not helpful.

The NCLC’s over simplification of a critical issue is not surprising. They once told Congress that the TCPA is “Straightforward and Clear” after all.

Full comment here: NCLC Comments-c3

We’ll keep an eye on developments on HHS’ letter and all the FCC goings ons.

© 2022 Troutman Firm

FCC Subjects Robocallers and Caller Identification Fraudsters to Increased Penalties and Broader Enforcement

On May 1, 2020, the Federal Communications Commission (FCC) adopted rules to strengthen protections against robocalls and the manipulation of caller identification information to misrepresent the true identity of the caller (known as caller ID spoofing).1 The FCC’s amended rules, which implement portions of the recently-enacted Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), streamline the procedure for commencing enforcement actions against violators and expand the statute of limitations applicable to FCC proceedings against robocallers and caller ID spoofers2 (see GT Alert, TRACED Act Subjects Robocallers to Increased Penalties, Outlines Regulatory and Reporting Requirements to Deter Violations).

The FCC’s changes to its rules include the following:

  • Eliminating the requirement that the FCC issue a citation to a person or entity that violates prohibitions against robocalling before issuing a notice of apparent liability if the person or entity does not hold a license, permit, or other authorization issued by the FCC. As noted by FCC Chairman Ajit Pai in the news release accompanying the FCC’s Order: “Robocall scam operators don’t need a warning these days to know what they are doing is illegal, and this FCC has long disliked the statutory requirement to grant them mulligans.” Caller ID spoofers are already subject to FCC enforcement actions without receiving a citation as a warning.3
  • Increasing the penalty amount to up to $10,000 for each intentional unlawful robocall in addition to the monetary forfeiture permitted under 47 U.S.C. § 503 (for persons or entities that are not FCC licensees or common carriers, the forfeiture penalty shall not exceed $20,489 for each violation and $153,669 for any continuing violation).4 Importantly, each unlawful robocall is considered to be a separate violation, so the potential forfeiture amounts could be very high.
  • Extending the statute of limitations applicable to FCC enforcement actions for intentional robocall violations and for caller ID spoofing violations to four years. Under the amended rule, the FCC may not impose a forfeiture penalty against a person for violations that occurred more than four years prior to the date a notice of apparent liability is issued. The statute of limitations had been one year for all robocall violations and two years for call ID spoofing violations. This change will significantly increase the timeframe of conduct subject to FCC enforcement and that can be included in a proposed forfeiture amount.

Conclusion

The FCC’s amended rules, consistent with the TRACED Act, are intended to discourage unlawful robocalling and caller ID spoofing by abolishing the “one free pass” formerly applicable to entities that do not hold FCC authorizations, increasing the penalties for intentional violations, and expanding the statute of limitations period. This is the FCC’s most recent action to implement the TRACED Act by strengthening protections against unlawful robocalls and caller ID spoofing. Other steps recently taken by the FCC include initiating a rulemaking proceeding to prevent one-ring scams (when a caller initiates a call and allows the call to ring for a short duration with the aim of prompting the called party to return the call and be subject to charges). Given the FCC’s significant focus on combatting illegal robocalling, it is important that companies that rely on robocalls to contact consumers understand the federal laws governing such calls implement procedures to ensure that they comply with those laws and regulations.


1 The Telephone Consumer Protection Act (TCPA) (which was amended by the TRACED Act) and the FCC’s implementing regulations generally prohibit the use of autodialed, prerecorded or artificial voice calls (commonly known as robocalls) to wireless telephone numbers and the use of prerecorded or artificial voice calls to residential telephone numbers unless the caller has received the prior express consent of the called party (certain calls, such as telemarketing calls, require prior express written consent) or is subject to specified exemptions. See 47 U.S.C. § 227; 47 C.F.R. § 64.1200.

2 The FCC issued these rules pursuant to an order, rather than utilizing notice and comment procedures, because the content of the rules did not require the exercise of administrative discretion. The rules will become effective 30 days after the date of publication in the Federal Register.

3 The FCC may issue a forfeiture order if it finds that the recipient of a notice of apparent liability has not adequately responded to the FCC’s allegations. The FCC may also seek to resolve the matter through a consent order which generally requires the alleged violator to make a voluntary payment, develop a compliance plan, and file compliance reports.

4 See 47 U.S.C. § 503(b)(2)(D) as adjusted for inflation. The FCC has authority to make upward or downward adjustments to forfeiture amounts based on several factors. See 47 C.F.R. § 1.80.

©2020 Greenberg Traurig, LLP. All rights reserved.

Limiting Junk Fax Class Actions: Online Fax Services Outside Scope of TCPA FCC Rules

 

On December 9, 2019, the Federal Communications Commission (“FCC”) issued a declaratory ruling In the Matter of Amerifactors Financial Group, LLC (“Amerifactors”) concluding that modern faxing technologies are not within the scope of the Telephone Consumer Protection Act (TCPA).  The Amerifactors ruling, which follows the express language of the TCPA, determines that faxes received via an online fax service as electronic messages are effectively email and therefore are not faxes received on a “telephone facsimile machine” under the statute. This narrows the scope of the TCPA to traditional fax machines and will make it more difficult for attorneys to certify classes of fax recipients under the TCPA, ideally curbing the plethora of TCPA Fax class action lawsuits.

Amerifactors Background

In 2017, Amerifactors filed a petition for an expedited declaratory ruling asking the FCC to “clarify that faxes sent by “online fax services” are not faxes sent to “telephone facsimile machines”[1] therefore, outside of the scope of the TCPA. While faxing has declined in usage significantly, many of those who still receive faxes do so through cloud-based services that send the document via an attachment to an email.  At the time of Amerifactors’ declaratory filing, they were defending a class action suit with claims that Amerifactors violated the TCPA by sending unsolicited fax messages, the bulk of which were sent to consumers from online fax services.

FCC Ruling and Logic

In the Amerifactors ruling, the FCC explained that faxes sent by online fax services do not lead to the “specific harms” Congress sought to address in the TCPA’s Junk Fax Protection Amendment and concluded that “a fax received by an online fax service as an electronic message is effectively an email.”

Unlike printed fax messages that require the recipient to supply paper and ink, the FCC concluded consumers can manage faxes sent by online fax services the same way they manage their email by blocking senders or deleting incoming messages without printing them, short-circuiting many of the specific harms envisioned by the original legislation.  With online fax services, there is no phone-line that is occupied and therefore unavailable for other purposes, and no paper or ink used that must be supplied by the recipient.  Clarifying legislative intent, the FCC stated:

“The House Report on the TCPA makes clear that the facsimile provisions of the statute were intended to curb two specific harms: “First, [a fax advertisement] shifts some of the costs of advertising from the sender to the recipient. Second, it occupies the recipient’s facsimile machine so that it is unavailable for legitimate business messages while processing and printing the junk fax.”

In many ways, the FCC ruling in Amerifactors demonstrates FCC recognition of the changes in faxing technology.  Steven Augustino of KelleyDrye[2], one of the attorneys who represented Amerifactors,  points out that the language we use now does not match the technology that has largely replaced traditional faxing technology, instead offering a short-hand that has roots in an earlier era—and that references dead technologies.  Augustino says:

Amerifactors argued that the term “faxing” has outlived the actual technology of faxing, much in the same way that we still dial a telephone even though no one has a rotary telephone, or we “cc” people on emails but we aren’t using carbon copies.  In many ways, saying ‘I sent a fax’ is similar to that, the term has outlived the technology that has supported it.”

There is reason to believe that this is the first of many declaratory rulings on fax matters under the TCPA.  As of November 2019, there are thirty-six petitions in front of the FCC, and six of those petitions specifically address “junk” faxing rules.  These petitions represent a variety of faxing issues, such as consent and the definition of an advertisement.   The declaratory ruling in Amerifactors and the FCC’s reasoning related to technological changes will likely impact the FCC’s rule-making on similar issues.

Implications for Future TCPA Fax Class Action Lawsuits

According to Douglas B. Brown of RumbergerKirk, one of the attorneys who represented Amerifactors in the FCC’s declaratory ruling:

“While the traditional fax machine has faded out of today’s business communications, online fax services provide secure communications that are critical to providing consumers with secure information about their finances, health and other important matters. The FCC’s ruling allows for these communications to continue without interference from debilitating class-action lawsuits.”

Per Samantha Duke of RumbergerKirk who also represented Amerifactors:

“First, according to the Hobbs Act, federal district courts are bound to enforce the FCC’s rules, regulations, and orders relating to the TCPA. Thus, this declaratory ruling may impact all fax class actions filed in the district courts in the country.”

The Amerifactors ruling requires a closer look at how faxes are being received complicating how class actions are certified under the TCPA.  Per Duke:

The Amerifactors ruling now makes the method by which the fax was received key to determining whether any particular unsolicited facsimile violates the TCPA. This individualized determination will most certainly complicate any attempt to certify a TCPA-fax class action as the question of whether the facsimile was sent to an online fax service will predominate over any common issue.”

In short, unless a fax comes through an old-school fax machine, it’s outside the reach of the TCPA per the FCC’s Amerifactors ruling.


[1] See Petition for Expedited Declaratory Ruling of Amerifactors Financial Group, LLC, CG Docket Nos. 02-278, 05-338, at 2 (filed July 13, 2017) (Petition).

[2] Amerifactors Financial Group, LLC was represented by Rumberger, Kirk & Caldwell, PA attorneys Douglas B. Brown and Samantha Duke, along with attorney Steven A. Augustino of Kelley Drye & Warren LLP.


Copyright ©2019 National Law Forum, LLC

For more on the TCPA and FCC Regulations, see the National Law Review Communications, Media & Internet law section.

DOJ Seeking to End Movie Studio and Theater Antitrust Decrees amidst Streaming Competition – A New Opportunity in Theatrical Distribution?

For the film and media distribution industries, this year has been action-packed.  Production budgets are skyrocketing and new digital services have been announced or are launching with each passing month. The streaming wars are upon us. Moreover, the FCC recently voted to treat streaming services as “effective competition” to traditional cable providers (or MVPDs), thereby triggering basic cable rate de-regulation in parts of Hawaii and Massachusetts.

The distribution landscape took yet another unexpected legal twist this week. On November 18, Assistant Attorney General Makan Delrahim announced that the Antitrust Division of the Department of Justice would ask a federal court to terminate the “Paramount Consent Decrees” (the “Decrees”), which have prohibited movie studios from engaging in certain distribution practices with movie theaters since the 1940s. The DOJ filed a motion to terminate the Decrees in federal court in the Southern District of New York on November 22, 2019.  Notably, the DOJ cites streaming services and new technology as a few of the many reasons that the Decrees may no longer be necessary in what the DOJ official sees as today’s highly competitive, consumer-driven content market. Given the volatility of the content licensing space, film licensors and licensees will have to carefully consider how the DOJ’s actions will affect their content rights and options going forward.

By way of background, the Decrees emerged out of the landmark 1948 Supreme Court antitrust case, United States v. Paramount Pictures, Inc. Prior to the case, top Hollywood studios frequently owned movie theaters (thus, owning both the means of production and distribution). This vertical integration led to lower distribution costs for the studios and gave them pricing power and the ability to discriminate about which theaters distributed their films. Not surprisingly, smaller, independent theaters struggled to survive.  The problem was exacerbated by studios engaging in practices such as “block-booking” (requiring theaters to distribute all or none of the studio’s slate of films) and overbroad “clearances” (restrictions on the time which must elapse between particular runs of a film), as well as alleged horizontal conspiracies between the studios and theaters on matters like minimum ticket pricing. As part of the Decrees, the defendant studios were restricted or prohibited from engaging in these practices and were required to divest certain interests in their theaters.

The DOJ’s November 22nd motion may not come as a surprise, as the DOJ first announced that the Decrees were under review in August 2018, after which several industry players, including the National Association of Theatre Owners (NATO), submitted comments. In particular, NATO argued, despite how streaming and technology might increase competition, that block-billing would still adversely impact independent or local chains that exhibit fewer films and may not be able to afford larger blocks of films.

Delrahim summed up the DOJ’s position, stating, “the [D]ecrees, as they are, no longer serve the public interest, because the horizontal conspiracy – the original violation animating the decrees – has been stopped. […] Changes over the course of more than half a century also have made it unlikely that the remaining defendants can reinstate their cartel.” In particular, the DOJ argued that the competitive concerns of the 1940s no longer exist because the movie marketplace has changed so drastically, citing how film distributors have become less reliant on theatrical distribution with the advent of streaming. According to the DOJ, colluding to limit theatrical film distribution in today’s market “would make no economic sense.”  In addition to streaming services, Delrahim also cited new theatrical release business models (such as flat-fee multi-ticket pricing) as increasing competition and innovation in film distribution.

The DOJ acknowledged NATO’s concerns in part and asked the court to implement a two-year sunset on block-booking and circuit dealing (licensing to all theaters under common ownership, as opposed to on a theater-by-theater basis). Whether terminating the Decrees would decrease innovation, neither the motion papers nor Delrahim venture to guess. Delrahim noted that antitrust enforcers need not predict the future but need only recognize that changes are occurring. He added that practices covered by the Decrees would not become per se lawful, but would rather be subject to review under the rule of reason standard.

Commentators are split on whether termination of the Decrees that have shaped Hollywood for decades will lead to any significant change for the movie business. One thing that is important to note is that the Decrees did not outright prohibit vertical integration of studios and theaters – the defendant studios could (and did) acquire theaters after proving that such acquisitions would not unreasonably restrain trade. Further, only those studios party to the Decrees remain subject to their restrictions, meaning many of today’s top studios (that now typically own a vast portfolio of traditional and digital entertainment properties) were non-existent or much smaller in the 1940s and have not been subject to the Decrees.

While it remains to be seen how this development will play out, it is noteworthy for digital providers because it may breathe extra life back into the theatrical release window. With mammoth streaming deals inked every week, the value of the theatrical release window was seemingly diminishing for some films. But now that many studios are forgoing third-party licensing fees and instead retaining their content for their own streaming platforms, studios may begin to ask whether added revenues from ownership of a theater chain could be a potential new source of revenue and a way to gain additional control of the theatrical window. Meanwhile, the effect of lifting the Decrees may not necessarily lead to a flurry of acquisitions, as other studios involved in direct-to-consumer streaming campaigns may not have the capital or desire to exploit the termination of the Decrees. Major theater chains will likely seek to strengthen relationships with studios, while independent theaters will look for ways to succeed despite potentially rising costs.

With all of these developments, studios and media platforms will also need to carefully consider how to protect their interests when handling their licensing arrangements, given the volatility in this space and keeping in mind the two-year sunset (assuming the DOJ succeeds) on block-booking and circuit dealing. While some distributors may be looking for long-term, exclusive content deals as they roll-out their streaming services, studios and content providers may seek flexibility as their distribution options are changing day-to-day.


© 2019 Proskauer Rose LLP.

More on entertainment distribution on the National Law Review Entertainment, Art & Sports law page.

Save the Internet Act of 2019 Introduced

On 6 March 2019, Democrats in the House and Senate introduced the “Save the Internet Act of 2019.” The three-page bill (1) repeals the FCC’s Restoring Internet Freedom Order released in early 2018, as adopted by the Republican-led FCC under Chairman Ajit Pai; (2) prohibits the FCC from reissuing the RIF Order or adopting rules substantively similar to those adopted in the RIF Order; and (3) restores the Open Internet Order released in 2015, as adopted by the Democratic-led FCC under Chairman Tom Wheeler.

Major Impacts:

  • Broadband Internet Access Service (BIAS) is reclassified as a “telecommunications service,” potentially subject to all provisions in Title II of the Communications Act.

  • The three bright line rules of the Open Internet Order are restored: (1) no blocking of access to lawful content, (2) no throttling of Internet speeds, exclusive of reasonable network management practices, and (3) no paid prioritization.

  • Reinstates FCC oversight of Internet exchange traffic (transit and peering), the General Conduct Rule that authorizes the FCC to address anti-competitive practices of broadband providers, and the FCC’s primary enforcement authority over the Open Internet Order’s rules and policies.

  • Per the Open Internet Order, BIAS and all highspeed Internet access services remain subject to the FCC’s exclusive jurisdiction and the revenues derived from these services remain exempt from USF contribution obligations.

  • The prescriptive service disclosure and marketing rules of the Open Internet Order, subject to the small service provider exemption, would apply in lieu of the Transparency Rule adopted in the RIF Order.

FCC Chairman Pai promptly issued a statement strongly defending the merits and benefits of the RIF Order.

KH Assessment

  • From a political perspective, Save the Internet Act of 2019 garners support from many individuals and major edge providers committed to net neutrality principles but faces challenges in the Republican-controlled Senate.

  • In comments filed in the proceeding culminating in the RIF Order, the major wireline and wireless broadband providers supported a legislative solution that codified the no blocking and no throttling principles but not the no-paid prioritization prohibition or classifying BIAS as a telecommunications service.

It is highly unlikely that the legislation will be enacted as introduced. Though still unlikely, there is a better chance that a legislative compromise may be reached.

 

© 2019 Keller and Heckman LLP.

Now I Get It!: Using the FCC’s Order Keeping Text Messages as “Information Services” to Better Understand the Communications Act

Little known fact: the TCPA is just a tiny little part of something much bigger and more complex called the Communications Act of 1934, as amended by Telecom Act of 1996 (which the FCC loves to just call the “Communications Act.”) And yes, I know the TCPA was enacted in 1991 but trust me it is still part of the Communications Act of 1934.

The Communications Act divides communications services into two mutually exclusive types: highly regulated “telecommunications services” and lightly regulated “information services.”

So let’s look at some definitions:

A “telecommunications service” is a common carrier service that requires “the offering of telecommunications for a fee directly to the public, or to such classes of users as to be effectively available to the public, regardless of the facilities used.”

“Telecommunications” is “the transmission, between or among points specified by the end user, of information of the user’s choosing without change in the form or content of the information as sent and received.”

By contrast, an “information service” is “the offering of a capability for generating, acquiring, storing, transforming, processing, retrieving, utilizing, or making available information via telecommunications, and includes electronic publishing, but does not include any use of any such capability for the management, control, or operation of a telecommunications system or the management of a telecommunications service.”

Make sense so far? Basically a telecommunications service is something that telecommunications companies–who are common carriers– can’t tinker with and have to automatically connect without modifying. For instance, if I want to call my friends from law school and wish them well Verizon can’t say–wait a minute, Eric doesn’t have any friends from law school and refuse to connect the call. Verizon must just connect the call. It doesn’t matter who I am calling, how long the call will be, or why I’m making the call, the call must connect. The end.

Information services are totally different animals. Carriers can offer or not offer and tinker and manipulate such messages all they want–see also net neutrality.

So if text messages are a telecommunication then they must be connected without question. But if text messages are an information service then carriers can decide which messages get through and which don’t.

It might seem like you’d want text messages to be information services–after all why would we want the carriers determining how and when we can text each other? Well the FCC has an answer– automatic spam texts.

If text messages are subject to common carrier rules then people can blast your phone with spam text messages and the carriers can’t stop them. True the TCPA exists so you can sue the texter but–as we know–the vast majority of spammers are shady fly-by-nights or off-shore knuckleheads that you can’t find. So the FCC believes that keeping text messages categorized as “information services”–as they are currently defined–will keep spammers away from your SMS inbox. It issued a big order today accomplishing just that. 

And to be sure, the carriers are monitoring and block spam texts as we speak. As the FCC finds: “wireless messaging providers apply filtering to prevent large volumes of unwanted messaging traffic or to identify potentially harmful texts.”  The FCC credits these carrier efforts with keeping text messages relatively spam free:

For example, the spam rate for SMS is estimated at 2.8% whereas the spam rate for email is estimated at over 50%.  Wireless messaging is therefore a trusted and reliable form of communication for many Americans. Indeed, consumers open a far larger percentage of wireless messages than email and open such messages much more quickly.

So from a policy perspective keeping text messages as information services probably makes sense, but let’s review those definitions again.

A telecommunication service is essentially the transmission of information of the user’s choosing.

An information service is “the offering of a capability for generating, acquiring, storing, transforming, processing, retrieving, utilizing, or making available information via telecommunications.”

So is a text message the transmission of information of my choosing or is it the use of Verizon’s ability to store and retrieve information I am sending? (And is there really even a difference?)

Well the FCC says texts are absolutely information services and here’s why:

  • SMS and MMS wireless messaging services provide the capability for “storing”
    and “retrieving” information. When a user sends a message, the message is routed through servers on mobile networks. When a recipient device is unavailable to receive the message because it is turned off, the message will be stored at a messaging center in the provider’s network until the recipient device is able to receive it.

  • SMS and MMS wireless messaging services also involve the capability for “acquiring” and “utilizing” information. As CTIA explains, a wireless subscriber can “ask for and receive content, such as weather, sports, or stock information, from a third party that has stored that information on its servers. SMS subscribers can ‘pull’ this information from the servers by making specific requests, or they can signal their intent to have such information regularly ‘pushed’ to their mobile phone.

  • SMS and MMS wireless messaging services involve “transforming” and
    “processing” capabilities. Messaging providers, for example, may change the form of transmitted information by breaking it into smaller segments before delivery to the recipient in order to conform to the character limits of SMS.

Yeah…I guess. But realistically when I send a text I just want it to get there there the way I sent it. Maybe there’s some storing and utilizing and processing or whatever but not very much.

And that was Twilio’s point. It asserted:  “the only offering that wireless carriers make to the public, with respect to messaging, is the ability of consumers to send and receive messages of the consumers’ design and choosing.” That sounds right.

Well the FCC disagrees: “These arguments are unpersuasive.”

The FCC’s point is that “what matters are the capabilities offered by the service, and as we explain above, wireless messaging services feature storage, retrieval, and other information-processing capabilities.”

Hmmm. ok. I guess I’m ok with that if you are.

But let’s get to the good stuff from a TCPA perspective. Recall that a text message is a “call” for purposes of the TCPA. Well if a text isn’t even a telecommunication how can it be a call? Asks Twilio.

Yeah, FCC, how can it be a call? Asks the Czar.

The Commission answers:

the Commission’s decision merely clarified the meaning of the undefined term “call” in order to address the obligations that apply to telemarketers and other callers under the TCPA. That decision neither prohibits us from finding that wireless messaging service is an information service, nor compels us to conclude that messaging is a telecommunications service.

Ok. Well. Why not?

The Commission answers further:

The TCPA provision itself generally prohibits the use of a facsimile machine to send
unsolicited advertisements, but that does not constitute a determination that an individual’s sending of a fax is a telecommunications service, just as the application to an individual’s making “text calls” does not reflect a determination that wireless messaging is a telecommunications service. In any event, for purposes of regulatory treatment, there is a significant difference between being subject to Commission regulation and being subject to per se common carrier regulation. Only the latter requires classification as a telecommunications service. We clarify herein that SMS and MMS wireless messaging are Title I services, and thus, will not be subject to per se common carrier regulation.

Umm FCC, no disrespect intended, but I kind of feel like that doesn’t really answer the question.

But in any event, the FCC plainly believes that text messages are a “call” for purposes of the TCPA but are not a “telecommunication” for purposes of common carrier regulation.

From a policy perspective I’m fine with the conclusion the Commission reached–it makes sense to keep text messages free from spam. But we have to be honest with ourselves here, the Commission just did legal somersaults to get there. Maybe its time for Congress to take another look at the Communications Act hmmm?

In any event, now you get it!

 

Copyright © 2018 Womble Bond Dickinson (US) LLP All Rights Reserved.
This post was written by Eric Troutman of Womble Bond Dickinson (US) LLP.
Read more news about the TCPA at the National Law Review.

Federal Communications Commission Tackles the “Reassigned Number Problem”

Reassigned numbers have been at the center of the surge in litigation under the Telephone Consumer Protection Act (“TCPA”) during the last few years.  By now the story is well known to businesses that actively communicate with their customers: the customer consents to receive telemarketing and/or informational robocalls[1] at a wireless telephone number, but months or years later the customer changes his or her wireless telephone number and—unbeknownst to the business—the telephone number is reassigned to a different person.  When the recipient of the reassigned number starts receiving calls or messages from the business, a lawsuit often ensues under the TCPA because that party has not consented to receive such calls.  The FCC adopted on July 13 a Second Notice of Inquiry (“Second NOI”) that promises to address this problem in a meaningful way.  Specifically, the Second NOI focuses on the feasibility of “using numbering information to create a comprehensive resource that businesses can use to identify telephone numbers that have been reassigned from a consumer who has consented to receiving calls to a consumer who has not.”

Background on the Reassigned Number Problem

Under the current regime, the North American Numbering Plan (NANP) Administrator generally provides telephone numbers to voice service providers—including those who supply interconnected voice—in blocks of 1000.  The voice service providers recycle those numbers in and out of service, such that, after a number has been dropped, the number goes into a pool for a short period and then is brought out of the pool and reassigned to a different consumer.

The “reassigned number problem” occurs when a consumer consents to receive robocalls (telemarketing and/or informational), but then terminates service to the relevant wireless number without informing the businesses the consumer previously gave consent to make the robocalls.  Businesses that find themselves making robocalls to numbers that (unbeknownst to them) had been reassigned to a different consumer increasingly find themselves subject to lawsuits under the TCPA—this even though it has been widely acknowledged that (1) customers often switch telephone numbers without providing notice to businesses and (2) there is no public directory of reassigned wireless numbers that businesses can rely on to identify and scrub reassigned numbers.  When various industry groups and business entities asked the FCC to intervene, the FCC clarified that businesses making robocalls needed the consent of “the actual party who receives a call,” not of the intended recipient of the robocall.  FCC created a so-called “safe harbor” that afforded little protection in practice: a business could make a single call to a reassigned number without triggering liability under the TCPA, but the business would then be imputed with “constructive” knowledge that the number had been reassigned even if the single call did not yield actual confirmation that the number had been reassigned. The FCC did so even as it admitted that the tools available to identify reassigned numbers “will not in every case identify numbers that have been reassigned” and that the steps it was taking “may not solve the problem in its entirety” even “where the caller is taking ongoing steps reasonably designed to discover reassignments and to cease calls.”

The Second NOI

The Second NOI promises to more meaningfully address the reassigned number problem by suggesting the creation of a reliable, complete list of reassigned numbers that service providers would be required to update.  In pertinent part, the Second NOI addresses a number of other topics, including, but not limited to, possible reporting alternatives, compensation schemes, frequency of updates, and fees and eligibility requirements for accessing reassigned number data.  It also asks a number of logistical questions, including, but not limited to:

(1) What are the ways in which voice service providers could report the information in an accurate and timely way?

(2) Would the reporting—into a database or other platform—“substantially improve robocallers’ ability to identify reassigned numbers?”

(3) What information should voice service providers report?

(4) In what ways might the information reported raise concerns regarding the disclosure of private, proprietary, or commercially sensitive information?

(5) Should reassignment of toll-free numbers also be reported?

(6) What is the quantity of numbers reassigned and the benefits of reducing unwanted calls to these numbers?

(7) Should there be a safe harbor from TCPA violations for robocallers who use the new reassigned number resource?  What would be the advantages and disadvantages?

(8) How can the FCC incentivize robocallers to use the reassigned number resource?

In addition, the Second NOI seeks comment on whether the notification requirement should apply to all voice service providers or just providers of wireless services, and how to “balance the reporting burden placed on voice service providers against consumers’ privacy interests and robocallers’ interest in learning of reassignments.”   The item also seeks comment on which entity should be responsible for notification in circumstances when a voice service provider does not receive numbers directly from NANP, but instead obtains numbers “indirectly” from carrier partners.

The Commission claims it has the authority under Sections 227(b) and 251(e) of the Communications Act of 1934, as amended—which give the FCC control over the US portion of NANP and incorporate the TCPA—to require entities that obtain numbers from NANP to also report reassignments.  In fact, the Commission claims that doing so may further the statutory goals underlying the TCPA, which generally prohibits unwanted robocalls.

Although many details remain to be discussed and addressed by the FCC, the creation of the list that the FCC is proposing would address one of the main challenges faced by businesses that want to comply with the TCPA: how to gather reliable and complete information regarding which wireless telephone numbers have been reassigned.  The possibility of such a list working similar to that available to identify telephone numbers in the Do Not Call List is particularly promising, especially if it comes accompanied by safe harbor provisions similar to those attached to the Do Not Call List obligations in the FCC’s rules.

Comments are due August 28, 2017 and Reply Comments September 26, 2017.


[1] For purposes of this post “robocalls” refers to both calls made using an automatic telephone dialing system or using an artificial voice or pre-recorded message.

This post was contributed by Eduardo R. Guzmán  Paul C. Besozzi  and Koyulyn K. Miller of   Squire Patton Boggs (US) LLP
For more legal analysis check out the National Law Review.