Sanitized case study 08
BeiDou Terminal Self-Organizing Network Without a Command Device
Second OA clarity cleanup led to grant
The inventive contribution was recognizing that a command-device dependency could be broken.
FIELD: Satellite communication / ad hoc networkingSTAGE: SANITIZED TECHNICAL REVIEWRESULT: Second OA clarity cleanup led to grant
Review boundary
Satellite communication / ad hoc networking
This is a sanitized technical-prosecution note prepared for peer-agency due diligence. Full file histories, claim amendments, cited references, and client documents are shared only after NDA and conflict clearance.
EXAMINER LOGIC
How the rejection framed the case
The first OA relied on a self-organizing positioning/navigation communication terminal and treated group management and status notification as routine. In the second OA, the examiner shifted to clarity objections and indicated that correction could lead to allowance.
FIP RECONSTRUCTION
How the response rebuilt the case
The key was not merely clarity cleanup. The first response had already neutralized the inventive-step objection by identifying the real distinction: the no-command-device mode itself. Traditional BeiDou communication assumed command-device dependency; recognizing and breaking that hidden constraint was the technical contribution. The second response then cleaned up six clarity defects without reopening unnecessary battles.
OUTCOME
What changed procedurally
Grant followed the second response. The case demonstrates that discovering an unrecognized technical problem can itself support inventive-step reasoning.
Deep technical note
Detailed English-only prosecution analysis.
This section expands the case beyond the homepage summary so foreign counsel can assess the reasoning pattern, not just the outcome.
Diagnostic read
- The examiner treated group management and communication-status operations as routine networking functions.
- That view missed the hidden constraint in the field: traditional BeiDou communication assumed command-device involvement.
- The technical contribution lay in recognizing the problem and applying self-organizing network logic to a satellite communication context.
Response architecture
- Move the discussion from routine member-management operations to the no-command-device architecture itself.
- Explain why the cited reference solved a different problem: combining local-network and satellite communication functions, not removing command-device dependency.
- When the examiner shifted to clarity issues, clean up the formal defects without reopening unnecessary substantive disputes.
Due-diligence takeaways
- Discovering an unrecognized technical problem can support inventive-step reasoning.
- Cross-field transfer is not obvious simply because each field is separately known.
- A shift from inventive-step objections to clarity objections can signal that the substantive barrier has moved.
What a peer firm can test
For a live matter, we normally ask for the relevant patent office or jurisdiction, prosecution stage, core rejection issue, principal cited references, current deadline, and a neutral technical summary. Client names and unpublished full documents can wait until NDA and conflict clearance are complete.
The first review focuses on whether the examiner has mis-modeled the technical problem, overstated a motivation to combine, relied on unsupported common knowledge, or missed an allowance route available through disciplined claim amendment.