Syscall 7
IP Services

Expert engineeringfor IP licensing and litigation

We review source code, analyze software and hardware devices, and reverse engineer products to give counsel on either side the technical evidence a case turns on, from portfolio assessment through trial.

Contact us What we do Representative matters
We work across the full stack
Cloud & webweb apps
Cloud & web
AWS, Azure, GCPOracle OCI, IBM CloudKubernetes & containersHTTP & REST APIsWeb front end & back endDatabases & storageData pipelinesVideo streaming
Applicationapps
Application
Android apps (APK)iOS appsELF, PE, Mach-O binariesC / C++Java.NETMedia codecs & DRMML frameworks
OS & kernelcore system
OS & kernel
Linux & Android kernelsDevice driversRTOS: VxWorks, QNXWindows internalsMemory managementPower managementNetworking stacks
Firmwaredevice code
Firmware
Bootloaders & BIOSSecure bootTEE / ARM TrustZoneTrusted applicationsCellular & wireless basebandAutomotive ECUsFlash images & filesystemsBare metal
Silicon & RTLchip designs
Silicon & RTL
Verilog / VHDLSoC & GPU RTLAI acceleratorsLogic schematicsDatasheets & manualsAssembly: ARM, x86, MIPS, PowerPCGPU SASS

Our intellectual property practice turns source code, firmware, and silicon into technical evidence for patent, copyright, and trade secret matters.

Clients

Who we work with

Five kinds of clients engage us. Choose one to see the services that apply.

Disputes

Three areas of IP litigation

We support plaintiffs and defendants in patent, copyright, and trade secret disputes. The engineering is different in each.

Patent

We compare claim language with how a product works, using its source code, its firmware, or the device in operation, for infringement, non-infringement, and invalidity analysis.

Copyright

We compare codebases to analyze alleged copying, and we analyze how software protection and license controls work in anti-circumvention (DMCA) claims.

Trade secret

We compare the parties’ codebases in misappropriation disputes, and we analyze whether a claimed secret can be recovered from the shipped product by reverse engineering.

See examples of each in our work →

Expert witness & testimony

ForLitigation counsel
The question we answerWho will explain this technology to the judge or jury, and stand behind the analysis under cross-examination?

Declarations, expert reports, deposition, and trial, on both plaintiff and defense sides. The engineering has to hold up under cross-examination.

We work across U.S. district and state courts, the ITC, PTAB, and the European Unified Patent Court, and prepare the written record that supports it.

Source code review

ForLitigation counselCompanies responding to a claim
The question we answerThe other side has produced its source code. Where in it is the accused feature, and what exactly does the code do?

Structured review of produced source code in litigation. We work in the secured review environment, compare the code to the claim elements, and document what we find with citations to file, function, and line.

Our reviewers are engineers with development and reverse engineering experience in the technologies they review. That background is how we locate where a feature is implemented in an unfamiliar codebase and follow it across firmware, operating system, application, and server code. We have reviewed codebases ranging from embedded firmware to distributed systems, in patent, copyright, and trade secret matters. Every engineer on our team reads and writes production code, and a core group has extensive experience reviewing code produced in litigation. They are marked on our Team page.

Counsel and testifying experts receive material that is organized, traceable to specific files and functions, and ready to use in reports and at deposition.

Technology areas we have reviewed
Mobile firmwareARM TrustZone & secure enclavesCellular & wireless basebandOperating systems & kernelsSecure boot & bootloadersCryptography & key managementVideo & image codecsMedia DRMMobile payments & secure elementsSoC & GPU RTLAI acceleratorsMachine learning frameworksCloud architectureWeb front end & back endDatabases & storageAutomotive & vehicle busesNetworking & telecom equipmentMedical devicesIndustrial control & SCADA
Languages
Systems and applications
CC++C#JavaKotlinSwiftObjective-CGoPython
Web and data
JavaScript / TypeScriptHTML / CSSSQL
Scripting
BashPerlRuby
Hardware description (RTL)
VerilogSystemVerilogVHDL
Assembly
ARMx86MIPSPowerPCGPU (CUDA PTX and SASS)

Software and firmware reverse engineering

ForLitigation counselPatent ownersOperating companiesFunders & acquirersCompanies responding to a claim
The question we answerYou do not have the source code. What does the product do, and how can you prove it from the product itself?

We analyze the software a product runs: mobile and desktop applications, firmware, operating system components, and trusted applications. We disassemble and decompile the code, instrument it while it runs, and document how the accused feature works.

Sometimes the code is a download away, as with an app or a firmware update file. When it is locked inside a device, our bench work gets it out: teardown, flash extraction, and console access are the means of reaching the code.

For questions about the hardware itself, we work out how a chip or SoC operates from its public documentation, such as datasheets and reference manuals, and can often prepare claim charts from that. Where a matter calls for physical chip analysis, such as decapsulation or circuit extraction, we team with specialist labs.

This is also how the technical record is built in European matters where discovery is not available or for pre-litigation analysis in the U.S.: the evidence comes from the product itself. Our eight-step workflow runs from product acquisition to an Evidence of Use document, recorded at a level counsel can follow and another expert can verify.

Diagram of a workstation using Frida over USB to hook a function in a library running on a target phone
Dynamic analysis: hooking a function in running code with Frida.

Reverse engineering workflow

Steps 2 through 4 apply when the code has to come off a device. An application or a firmware update file skips directly from Step 1, product acquisition, to Step 5, static analysis.

OUR WORKFLOW 1. Product acquisition Obtain the app, firmware, or device 2. Device teardown Take the device apart and prepare a report 3. Flash chip removal Remove the flash chip from the board 4. Flash chip dump Read out the contents of the flash chip 5. Static analysis Decompile the code to understand its logic 6. Dynamic analysis Instrument the running code to observe its behavior 7. Product testing Operate the device to identify key capabilities 8. Evidence of Use Prepare Evidence of Use documents from the analysis results
Tweezers lifting a memory chip from a circuit board
Step 3. Lifting the flash chip from the board.
Fine wires soldered to the flash bus signals on a circuit board, with a pen tip for scale
Step 4. Tapping the flash bus signals in place, pen tip for scale.
Disassembled and decompiled firmware side by side in the Ghidra reverse engineering tool
Step 5. Decompilation of the extracted code.
Logic analyzer software decoding a UART signal into a device’s boot console output
Step 6. Monitoring the boot console through a UART tap.
The eight steps in detail
Getting the code out
1
Product acquisition

We obtain the code or the product that contains it. An application or a firmware update file is downloaded from its public source. For a device, we find a seller based on price and availability and buy the product, usually two units of each model so one can be taken apart while the other is kept intact for testing in operation.

2
Device teardown

We take the device apart, identify its main circuit boards and the components of interest, typically the SoC and the flash memory chip, and document the teardown with photographs and a report.

3
Flash chip removal

We remove the flash memory chip from the circuit board with a hot-air reflow station, and re-ball BGA packages as needed so the chip can be read in a programmer socket.

4
Flash chip dump

We read out the raw contents of the flash chip, either by reading the removed chip in a programmer or by soldering fine wires to the flash bus signals and reading the chip in place on the board. We then verify the copy, known as an image, and identify its major components.

Analyzing the code
5
Static analysis

We take apart the firmware image, correct ECC and identify partitions and filesystems, decrypt and decompress as needed, then disassemble and decompile the software or firmware files of interest.

6
Dynamic analysis

We locate and monitor the boot console, root the system using public or custom techniques, and hook or instrument the programs of interest to observe how they behave while running.

7
Product testing

We operate the physical device by whatever means the analysis requires, from sending it data over its wired and wireless connections to using it by hand, to trigger and observe the behavior at issue.

8
Evidence of Use

We prepare an Evidence of Use document that steps through each claim element and sets out the evidence collected for it.

Lab testing

ForLitigation counselPatent ownersOperating companiesCompanies responding to a claim
The question we answerCan the product be recorded doing what the claim describes, in a way another expert could repeat?

We configure the accused device in real-world conditions, trigger the behavior at issue, and capture evidence of use with wired and wireless instrumentation.

Lab testing is different from the product testing in our reverse engineering workflow. That testing is exploratory: we use it to learn how a device behaves. Lab testing is done for the record: it shows the device performing the behavior at issue, in captures that are documented and that another expert can reproduce.

A test bench with an oscilloscope, a spectrum analyzer, and a device under test
Bench capture with an oscilloscope and spectrum analyzer.
A Bluetooth protocol analyzer with two antennas
Bluetooth protocol analyzer.
An RF shielded test enclosure cabled to a wireless access point
RF-shielded enclosure for isolated wireless testing.

Infringement & validity analysis

ForLitigation counselPatent ownersOperating companiesFunders & acquirersCompanies responding to a claim
The question we answerDoes the product do what the patent claim says, or not? And was the idea already in use before the patent?

We help counsel build and vet infringement assessments before a complaint is filed, and identify which products in the market appear to practice the claims.

We do the same analysis for defendants assessing a claim against them: we compare the asserted claims with how the accused product works to develop non-infringement positions, and we analyze prior-art products and systems for invalidity.

For either side, the goal is a position that is technically sound, with its weak points identified before the other side finds them.

Portfolio due diligence & claim charts

ForPatent ownersFunders & acquirers
The question we answerIs this patent portfolio worth buying, funding, or asserting?

Before you acquire, fund, or assert a portfolio, you need to know what it is worth. We read the patents against products and technologies in the market, develop and test claim charts, and identify which claims hold up and which do not.

The result is an engineering assessment, so an investment, acquisition, or assertion decision rests on how the claims map to products that ship today.

Patent mining

ForPatent ownersOperating companiesFunders & acquirers
The question we answerWhich patents in a portfolio you already own are being used by products on the market?

The value in a large portfolio is not always visible. We review a portfolio you own to identify the claims that appear to read on products in the market today.

The output is a ranked shortlist of patents for a licensing campaign, with the technical mapping done.

Capabilities

What we analyze

Our engineers hold electrical engineering, computer engineering, and computer science degrees and analyze from RTL and low-level assembly up through the software stack to cloud and web. Every service above draws on that range.

Across the full stack
Cloud & webAWS, Azure, GCP, Oracle OCI, and IBM Cloud. Kubernetes, full-stack web, big-data and ML pipelines
ApplicationNative and managed apps, DRM, protocols, databases
OS & kernelLinux, Android, Windows, macOS, VxWorks. Drivers and kernel modules
FirmwareSecure boot, TEE / ARM TrustZone, BIOS, bootloaders, RTOS
Silicon & RTLVHDL/Verilog RTL including GPU designs, logic schematics and datasheets, low-level assembly (x86, ARM, MIPS, PowerPC, NIOS II, MicroBlaze, GPU SASS)
Target domains

Representative, not exhaustive. The common thread is any device or system with firmware or software.

Consumer electronics Mobile devices Automotive Medical devices Industrial controls & SCADA Networking & telecom Servers & cloud infrastructure AI / ML systems
Tools & methods

Static analysis

Disassembly and decompilation, partition and filesystem recovery, decryption and decompression of firmware images.

Dynamic analysis

UART and JTAG, rooting, Frida-style hooking and instrumentation, logic-analyzer and bus capture.

Hardware & lab

BGA rework and re-balling, flash programming, Wi-Fi, Bluetooth, Ethernet, USB, CAN, SPI, and I2C testing. RF and spectrum analysis.

Software development

When the analysis needs a tool, we build it, in C, Python, and assembly, from drivers and fuzzers to proof-of-concept demonstrations.

Both sides

Plaintiff and defense experience on patent, copyright, and trade secret matters.

Courts and tribunals

U.S. district and state courts, the ITC, PTAB, and the European Unified Patent Court.

On the record

Expert declarations, reports, and deposition and trial testimony.

Engineers first

Electrical engineering, computer engineering, and computer science degrees. Roots in national security software and firmware work since 2015.

Working with us

How an engagement starts

Four steps from a first message to work under way.

1

Conflict check

Send us the names of the parties and a sentence about the technology. We check for conflicts before any substantive discussion.

2

Introductory call

You speak with an engineer who would work on the matter, about the technology and the questions you need answered.

3

Confidentiality

We sign a nondisclosure agreement, or the undertaking under the protective order, before we receive confidential material.

4

Scope and engagement

We propose the scope of work and who will do it. Work begins once an engagement letter is signed.

Have a matter where the evidence is inside the device?

Tell us about the patents and the products. We’ll tell you what the engineering can show.

Contact us info@syscall7.com