Smith Micro Software, Inc. v. Reliance Communications, LLC

CourtDistrict Court, C.D. California
DecidedJanuary 14, 2020
Docket2:19-cv-03676
StatusUnknown

This text of Smith Micro Software, Inc. v. Reliance Communications, LLC (Smith Micro Software, Inc. v. Reliance Communications, LLC) is published on Counsel Stack Legal Research, covering District Court, C.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Smith Micro Software, Inc. v. Reliance Communications, LLC, (C.D. Cal. 2020).

Opinion

O 1

3 4

7 8 United States District Court 9 Central District of California

11 SMITH MICRO SOFTWARE, INC., Case No. 2:19-cv-03676-ODW (MRWx) 12 Plaintiff, 13 v. ORDER GRANTING PLAINTIFF’S MOTION FOR ENTRY OF DEFAULT 14 RELIANCE COMMUNICATIONS, LLC, JUDGMENT [19] 15 Defendant.

16 17 I. INTRODUCTION 18 Plaintiff Smith Micro Software, Inc. (“Smith Micro”) moves for default judgment 19 against Defendant Reliance Communications, LLC (“Reliance”) in this breach of 20 contract action (“Motion”). (ECF No. 19.) For the reasons discussed below, the Court 21 GRANTS Plaintiff’s Motion.1 22 II. BACKGROUND 23 On or about January 22, 2018, Smith Micro and Reliance entered into an express 24 contract for the purchase, sale, and delivery of Smith Micro software and services. 25 (Compl. ¶¶ 2, 9–11, Ex. 1 (“Agreement”), ECF No. 1.) Specifically, the Agreement 26 provided that Smith Micro would provide integration services relating to device 27

28 1 After carefully considering the papers filed in support of the Motion, the Court deemed the matter appropriate for decision without oral argument. Fed. R. Civ. P. 78; C.D. Cal. L.R. 7-15. 1 management software for mobile devices that Smith Micro would deliver to Reliance, 2 which software Reliance would then resell to its mobile carrier customers. (Compl. 3 ¶ 9.) Reliance agreed to purchase a minimum of 500,000 licenses to the Software. 4 (Compl. ¶ 11.) Smith Micro delivered to Reliance a Device Management Client (the 5 software) and performed integration services pursuant to the Agreement. (Compl. 6 ¶ 10.) Smith Micro met all schedule milestones and estimated delivery dates set forth 7 in the Agreement and fully performed its obligations under the Agreement. (Compl. 8 ¶¶ 12, 13.) 9 The Agreement provides that all invoice amounts are due and payable within 10 thirty days of the invoice. (Compl. ¶ 14.) On February 5, 2018, Smith Micro invoiced 11 Reliance for $24,000 in relation to Milestone One as defined in the Agreement. 12 (Compl. 15, Ex. 2 (“February Invoice”).) On June 30, 2018, Smith Micro invoiced 13 Reliance for $110,000 in relation to Reliance’s minimum purchase commitment of 14 500,000 licenses and a 20% license fee for the first year of software support, as provided 15 in the Agreement. (Compl. ¶ 17, Ex. 3 (“First June Invoice”).) Also on June 30, 2018, 16 Smith Micro invoiced Reliance for $24,000 in relation to Milestone Three as defined in 17 the Agreement. (Compl. ¶ 19, Ex. 4 (“Second June Invoice”).) Reliance did not object 18 to these invoices but also did not submit any related payments, despite Smith Micro’s 19 numerous requests. (Compl. ¶¶ 16, 18, 20.) The Agreement provides for a one and a 20 half percent (1.5%) late payment charge per month for all past due amounts. (Compl. 21 ¶ 21 (discussing Agreement § 4.1).) 22 The Agreement includes a choice of law provision applying California law. 23 (Compl. ¶ 7 n.1 (quoting Agreement § 17.7).) The parties also consented to “the 24 personal and exclusive jurisdiction of the federal and state courts of Orange County, 25 California.” (Compl. ¶ 7 (quoting Agreement § 17.7).) The “Choice of Law and 26 Jurisdiction” provision “governs all claims arising out of or related to this Agreement.” 27 (Agreement § 17.7.) 28 1 On April 30, 2019, Smith Micro initiated this action against Reliance, bringing 2 claims for (1) breach of contract, (2) account stated, (3) unjust enrichment, and (4) 3 common count for goods and merchandise sold and delivered. (Compl. ¶¶ 8–44.) 4 Through the Complaint, Smith Micro seeks $158,000 plus 1.5% late fee interest, 5 pursuant to the unpaid invoices under the Agreement. (Compl. at 8.) Reliance has not 6 appeared in this action despite being served with the Complaint on May 8, 2019. 7 (Mot. 6; Proof of Service, ECF No. 9.) Upon Smith Micro’s request, the Clerk entered 8 default against Reliance on July 2, 2019. (Default, ECF No. 17.) 9 Smith Micro now moves for entry of default judgment against Reliance pursuant 10 to Federal Rule of Civil Procedure 55(b)(2) and seeks $158,000 plus late fees and costs. 11 (Mot. 4.) 12 III. LEGAL STANDARD 13 Federal Rule of Civil Procedure (“FRCP”) 55(b) authorizes a district court to 14 grant a default judgment after the Clerk enters default under Rule 55(a). Fed. R. Civ. 15 P. 55(b). Before a court can enter a default judgment against a defendant, the plaintiff 16 must satisfy the procedural requirements set forth in FRCP 54(c) and 55, as well as 17 Local Rules 55-1 and 55-2. Fed. R. Civ. P. 54(c), 55; C.D. Cal. L.R. 55-1, 55-2. Local 18 Rule 55-1 requires that the movant submit a declaration establishing: (1) when and 19 against which party default was entered; (2) identification of the pleading to which 20 default was entered; (3) whether the defaulting party is a minor, incompetent person, or 21 active service member; (4) that the Servicemembers Civil Relief Act, 50 U.S.C. § 3931, 22 does not apply; and that (5) the defaulting party was properly served with notice, if 23 required under Rule 55(b)(2). C.D. Cal. L.R. 55-1. 24 If these procedural requirements are satisfied, a district court has discretion to 25 enter default judgment. Aldabe v. Aldabe, 616 F.2d 1089, 1092 (9th Cir. 1980). “[A] 26 defendant’s default does not automatically entitle the plaintiff to a court-ordered 27 judgment.” PepsiCo, Inc., v. Cal. Sec. Cans, 238 F. Supp. 2d 1172, 1174 (C.D. Cal 28 1 2002). In exercising discretion, a court must consider several factors (the “Eitel 2 Factors”): 3 (1) the possibility of prejudice to the plaintiff, (2) the merits of plaintiff’s 4 substantive claim, (3) the sufficiency of the complaint, (4) the sum of money at stake in the action; (5) the possibility of a dispute concerning 5 material facts; (6) whether the default was due to excusable neglect, and 6 (7) the strong policy underlying the [FRCP] favoring decisions on the merits. 7 8 Eitel v. McCool, 782 F.2d 1470, 1471–72 (9th Cir. 1986). Generally, after the Clerk 9 enters default, the defendant’s liability is conclusively established, and the well-pleaded 10 factual allegations in the complaint are accepted as true, except those pertaining to 11 damages. TeleVideo Sys., Inc. v. Heidenthal, 826 F.2d 915, 917–18 (9th Cir. 1987) (per 12 curiam) (quoting Geddes v. United Fin. Grp., 559 F.2d 557, 560 (9th Cir. 1977)). 13 IV. DISCUSSION 14 Smith Micro has complied with the relevant procedural requirements for entry of 15 default judgment against Reliance and has established that the Eitel factors favor entry 16 of default judgment on certain of its claims. 17 A. Procedural Requirements 18 Smith Micro has complied with the relevant procedural requirements for entry of 19 default judgment against Reliance by submitting a declaration which states: (1) the 20 Clerk entered default against Reliance on July 2, 2019; (2) the default was entered on 21 the Complaint appearing at ECF No.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Alvera M. Aldabe v. Charles D. Aldabe
616 F.2d 1089 (Ninth Circuit, 1980)
Jose Luis Pena v. Seguros La Comercial, S.A.
770 F.2d 811 (Ninth Circuit, 1985)
Gary R. Eitel v. William D. McCool
782 F.2d 1470 (Ninth Circuit, 1986)
S.O.S., Inc. v. Payday, Inc.
886 F.2d 1081 (Ninth Circuit, 1989)
Oasis West Realty v. Goldman
250 P.3d 1115 (California Supreme Court, 2011)
Trafton v. Youngblood
442 P.2d 648 (California Supreme Court, 1968)
Nick v. Department of Motor Vehicles
12 Cal. App. 4th 1407 (California Court of Appeal, 1993)
Utility Audit Co. v. City of Los Angeles
5 Cal. Rptr. 3d 520 (California Court of Appeal, 2003)
Durell v. Sharp Healthcare
183 Cal. App. 4th 1350 (California Court of Appeal, 2010)
Pepsico, Inc. v. California Security Cans
238 F. Supp. 2d 1172 (C.D. California, 2002)
Landstar Ranger, Inc. v. PARTH ENTERPRISES, INC.
725 F. Supp. 2d 916 (C.D. California, 2010)
Skye Astiana v. the Hain Celestial Group
783 F.3d 753 (Ninth Circuit, 2015)
Miller v. Thomas
15 P. 55 (California Supreme Court, 1887)
Vogel v. Rite Aid Corp.
992 F. Supp. 2d 998 (C.D. California, 2014)
Stieg v. Commissioner of Patents
238 F. Supp. 19 (District of Columbia, 1965)
Cohen v. Leone
18 F.R.D. 494 (E.D. Pennsylvania, 1955)

Cite This Page — Counsel Stack

Bluebook (online)
Smith Micro Software, Inc. v. Reliance Communications, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/smith-micro-software-inc-v-reliance-communications-llc-cacd-2020.