Cedar Lane Technologies Inc. v. City National Rochdale, LLC

CourtDistrict Court, S.D. New York
DecidedFebruary 6, 2026
Docket1:25-cv-07845
StatusUnknown

This text of Cedar Lane Technologies Inc. v. City National Rochdale, LLC (Cedar Lane Technologies Inc. v. City National Rochdale, LLC) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Cedar Lane Technologies Inc. v. City National Rochdale, LLC, (S.D.N.Y. 2026).

Opinion

RABICOFF LAW ttc 4311 N RAVENSWOOD AVE SUITE 315 (773) 669 4590 CHICAGO, IL 60613 ISAAC @ RABILAW.COM

Hebruary 25 2026 vicki ENDORSED VIA ECF JSDC SDNY Honorable Andrew L. Carter, Jr. el ENT United States District Court ELECTRONICALLY FILED Southern District of New York DOCH, — 40 Foley Square DATE FILED: 2/6/2026 __ New York, NY 10007 RE: Cedar Lane Technologies Inc. v. City National Rochdale, LLC Case No. 1:25-cv-07845-ALC (S.D.N.Y.) Dear Judge Carter: Plaintiff Cedar Lane Technologies Inc. respectfully submits this letter in opposition to Defendant City National Rochdale, LLC’s (“CNR”) January 28, 2026 letter (Dkt. No. 22), in which CNR states its intent to file a motion to dismiss the First Amended Complaint (Dkt. No. 21). Defendant’s Proposed Motion is premature, substantively meritless and should be denied. I. Plaintiff's Amendment Was Proper and Fully Authorized Under Rule 15 and the Court’s Individual Practices Defendant’s suggestion that Plaintiff was required to signal its intent to amend in its responsive pre-motion letter (Dkt. No. 16) misreads the Court’s Individual Practices. Paragraph 2(D)(1) provides that “[d]uring a pre-motion conference to discuss a motion to dismiss, the non-moving party must advise the Court and its adversary whether it intends to file an amended pleading based on the pre-motion conference letter, and if so, when it will do so.” The operative language is clear; the obligation to advise arises “during a pre-motion conference,” not in the pre-motion letter exchange. No pre-motion conference was held in this case. In fact, the Court denied the letter motion for conference. See Dkt. No. 18. The letters exchanged (Dkt. Nos. 15 and 16) are not a substitute for a conference, and nothing in the Court’s Individual Practices imposes on the non-moving party any obligation to signal an intent to amend in the responsive letter. Moreover, Plaintiff’s amendment was filed as of right under Federal Rule of Civil Procedure 15(a)(1)(B), which permits a party to amend its pleading “within 21 days after service of a motion under Rule 12(b).”. Plaintiff filed its First Amended Complaint within twenty-one days of that filing, well within the period permitted by Rule 15(a)(1)(B). Dkt. No. 21. II. Defendant Fails to Engage with the Substance of the Amended Complaint Defendant’s letter is remarkable for what it does not contain—any substantive engagement with the FAC’s new allegations. Defendant dismisses the amended complaint’s eleven new paragraphs as “additional conclusory arguments” and the amended claim chart’s detailed factual allegations as “minimal edits adding ‘on information and belief’? paragraphs.” Dkt. No. 22 at 1.

A. The Amended Complaint’s Direct Infringement Allegations Are Detailed and Sufficient The FAC and its incorporated Claim Chart now allege, on information and belief, detailed facts establishing that CNR directly performs each step of the method claimed in Claim 20—or, in the alternative, that any steps performed by third parties are attributable to CNR. For example, the Amended Claim Chart alleges that CNR (1) associates its clients with identifiers (account numbers, usernames) in its own computer systems; (2) acquires and stores trade history information associated with those identifiers in its own databases; (3) generates profiles of its clients containing information—including retail investor classification—that indicates whether transactions will generate a profit; and (4) generates different offers (Retail Orders versus non-Retail Orders) to different clients based on those profiles, and submits those offers to exchanges for processing. See Dkt. No. 21-2 at 1, 4, 7, 10, 19. Defendant’s initial pre-motion letter (Dkt. No. 15) complained that Plaintiff failed to identify hardware or processors. The amended Claim Chart now specifically alleges, on information and belief, that CNR’s web-based client portals are served by backend computing infrastructure including servers with hardware processors; that CNR operates or contracts for data center infrastructure containing computer servers with processors executing the order execution and management system software; and that CNR’s web-based securities trading platform could not function without processors implemented in hardware. See Dkt. No. 21-2 at 4. Defendant’s January 28 letter does not address these allegations at all. Defendant’s initial letter also complained of a missing connection between the “profile” limitation and Defendant’s activities. The amended Claim Chart now alleges in detail that CNR’s system generates and maintains client account profiles that include the client’s classification as a “retail investor” or institutional/non-retail investor; that this classification is based on trading history and account characteristics; and that when a client’s profile indicates the client is a retail investor, this directly indicates that trading transactions executed on behalf of that client will generate a profit, which the original Claim Chart already identified. See Dkt. No. 21-2 at 10. Again, Defendant’s letter is silent on these allegations. Defendant’s initial letter raised a divided-infringement argument under Akamai Techs., Inc. v. Limelight Networks, Inc., 797 F.3d 1020 (Fed. Cir. 2015) (en banc), contending that the patent contemplates multiple entities and that Plaintiff failed to allege CNR performs each step. The amended Claim Chart addresses this head-on, alleging both that CNR directly performs each step of the claimed method—including during internal testing—and, alternatively, that to the extent any steps are performed by exchanges or other entities, CNR directs or controls the manner or timing of such performance, or conditions participation in an activity or receipt of a benefit upon performance of such steps, such that those steps are attributable to CNR. See Dkt. No. 21-4 at 10. Allegations of internal testing are routinely found sufficient at the pleading stage. See Aperture Net LLC v. Opengear, Inc., No. 20-CV-03613-SVK, 2020 WL 11401699, at *3 (N.D. Cal. Dec. 10, 2020) (sufficient where plaintiff alleged defendant “practiced all of the steps . . . through internal testing, quality assurance, research and development, and troubleshooting”); Encoditech LLC v. Qardio, Inc., No. CV 18-2059 (MN), 2019 WL 2526725, at *6 (D. Del. June 19, 2019) (allegation that defendant “performed all of the steps . . . by its internal testing” sufficient); Dodots Licensing Sols. LLC v. Lenovo Holding Co., Inc., No. CV 18-098 (MN), 2018 WL 6629709, at *3 (D. Del. Dec. 19, 2018) (“It is not implausible that Defendants perform internal testing . . . that results in performance of all the steps in claim 1, and Plaintiff would have no insight into Defendants’ internal activities at the pleading stage.”). Moreover, Defendant’s divided-infringement argument improperly attempts to import a limitation from the specification—the “takers” and “providers” distinction—into Claim 20. These allegations more than satisfy the pleading standard. Plaintiff is not required to “prove [its] case at the pleading stage.” Bot M8 LLC v. Sony Corp. of Am., 4 F.4th 1342, 1346 (Fed. Cir. 2021). Rather, a plaintiff need only give the alleged infringer fair notice of infringement, and “the Federal Rules of Civil Procedure do not require a plaintiff to plead facts establishing that each element of an asserted claim is met.” Id. at 1352; see Disc Disease Sols. Inc. v. VGH Sols., Inc.,

Related

Berkheimer v. Hp Inc.
881 F.3d 1360 (Federal Circuit, 2018)
Disc Disease Solutions Inc. v. Vgh Solutions, Inc.
888 F.3d 1256 (Federal Circuit, 2018)
Bot M8 LLC v. Sony Corporation of America
4 F.4th 1342 (Federal Circuit, 2021)
Weisner v. Google LLC
51 F.4th 1073 (Federal Circuit, 2022)
Akamai Technologies, Inc. v. Limelight Networks, Inc.
797 F.3d 1020 (Federal Circuit, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Cedar Lane Technologies Inc. v. City National Rochdale, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/cedar-lane-technologies-inc-v-city-national-rochdale-llc-nysd-2026.