<div dir="ltr"><div dir="ltr">"If the method and apparatus claims are "twins" (as is the case in most computer applications, and as you suggest " <span lang="en-IL" style="font-family:Calibri,sans-serif">the only distinction is that the system claim includes a memory and a processor</span> "), then the restriction requirement is in error, and you should traverse." - See, also, 37 CFR 1.141(b)("
Where claims to all three categories, product, process of making, and process of use, are included in a national application, a three way requirement for restriction can only be made where the process of making is distinct from the product. If the process of making and the product are not distinct, the process of using may be joined with the claims directed to the product and the process of making the product even though a showing of distinctness between the product and process of using the product can be made.
")</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Mar 28, 2025 at 7:08\u202fAM David Boundy via Patentpractice <<a href="mailto:patentpractice@oppedahl-lists.com">patentpractice@oppedahl-lists.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>If the method and apparatus claims are "twins" (as is the case in most computer applications, and as you suggest "
<span lang="en-IL" style="font-family:Calibri,sans-serif">the only distinction is that the system claim includes a memory and a processor</span>
"), then the restriction requirement is in error, and you should traverse. By separate email, I am sending you "the big email" I send out from time to time. <br></div><div><br></div><div>There's no "foreseeing" how an examiner may violate the law.</div><div><br></div><div>Start by looking at the two search classes. Almost certainly, one of them is entirely bogus. That's a staring point.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 28, 2025 at 7:02\u202fAM Allen Richter (allenr--- via Patentpractice <<a href="mailto:patentpractice@oppedahl-lists.com" target="_blank">patentpractice@oppedahl-lists.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="en-IL">
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)">Dear all,
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li style="color:rgb(64,64,64);margin-left:0cm">
<span lang="en-IL" style="font-family:Calibri,sans-serif">I </span><span lang="EN-US" style="font-family:Calibri,sans-serif">noted and
</span><span lang="en-IL" style="font-family:Calibri,sans-serif">was informed that withdrawn method claims are more likely to be rejoined based on allowable system claims, rather than the other way around. If that's accurate, does anyone know why this is
the case?</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></li></ol>
<p><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="2" type="1">
<li style="color:rgb(64,64,64);margin-left:0cm">
<span lang="en-IL" style="font-family:Calibri,sans-serif">Some examiners impose a restriction requirement on system and method claims, even though the only distinction is that the system claim includes a memory and a processor.</span><span lang="en-IL" style="font-family:Calibri,sans-serif">
</span><span lang="EN-US" style="font-family:Calibri,sans-serif"><u></u><u></u></span></li></ol>
<p><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u> <u></u></span></p>
<p><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)">Is there anything that would allow one to foresee when a restriction requirement is issued in such scenario, and when not?
<u></u><u></u></span></p>
<p><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)">Thank you all in advance for your feedback, and wishing you a nice weekend!<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)">Allen</span><span lang="EN-US" style="font-family:Calibri,sans-serif;color:rgb(64,64,64)"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)">European, Swiss & Israeli Patent Attorney</span><span lang="EN-US" style="font-size:9pt;color:rgb(0,32,96)"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9pt;color:black">RICHTER SHIMONI PATENT ATTORNEYS<u></u><u></u></span></p>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:9pt;color:rgb(0,112,192)"><a href="http://www.richterpatent.com" target="_blank">www.richterpatent.com</a></span></u><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)"><br>
4 Oppenheimer Street </span><b><span lang="EN-US" style="font-size:9pt;color:rgb(51,51,204)">|</span></b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)"> Ogen Tower B
<b>|</b> 6<sup>th</sup> Floor </span><b><span lang="EN-US" style="font-size:9pt;color:rgb(51,51,204)">|</span></b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)"> 7670104 Rehovot
</span><b><span lang="EN-US" style="font-size:9pt;color:rgb(51,51,204)">|</span></b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)"> Israel<br>
IL: +972-(0)54-527 3417 </span><b><span lang="EN-US" style="font-size:9pt;color:rgb(51,51,204)">|</span></b><b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)">
</span></b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)">+972-(0)8-68 999 61
</span><b><span lang="EN-US" style="font-size:9pt;color:rgb(51,51,204)">|</span></b><span lang="EN-US" style="font-size:9pt;color:rgb(68,84,106)"> CH: +41-(0)22-508 7033
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:8pt;color:rgb(0,32,96)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:8pt;color:rgb(0,32,96)">This e-mail as well as any attached document contains information which is confidential and that may be subject to legal privilege. If you are not the intended
recipient, you must not read, use, disseminate, distribute or copy this e-mail or its attachments. If you have received this in error, please inform us immediately by return e-mail, facsimile or by telephone and delete this e-mail. Please note that all opinions
and/or conclusions expressed herein are preliminary and merely represent our analysis of the facts</span><span dir="RTL"></span><span dir="RTL"></span><span lang="EN-US" dir="RTL" style="font-size:8pt;font-family:"Times New Roman",serif;color:rgb(0,32,96)"><span dir="RTL"></span><span dir="RTL"></span>
</span><span lang="EN-US" style="font-size:8pt;color:rgb(0,32,96)">as known and/or presented to us and are not to be viewed or relied upon</span><span dir="RTL"></span><span dir="RTL"></span><span lang="EN-US" dir="RTL" style="font-size:8pt;font-family:"Times New Roman",serif;color:rgb(0,32,96)"><span dir="RTL"></span><span dir="RTL"></span>
</span><span lang="EN-US" style="font-size:8pt;color:rgb(0,32,96)">as conclusive and/or as a prediction of the outcome of any current or future litigation or</span><span dir="RTL"></span><span dir="RTL"></span><span lang="EN-US" dir="RTL" style="font-size:8pt;font-family:"Times New Roman",serif;color:rgb(0,32,96)"><span dir="RTL"></span><span dir="RTL"></span>
</span><span lang="EN-US" style="font-size:8pt;color:rgb(0,32,96)">other controversy. While email correspondence is very practical, we remind you that emails sent to our firm are not deemed to be received until you have obtained an acknowledgement
of receipt (e.g., by return email).</span><span lang="en-IL" style="font-size:12pt;color:rgb(64,64,64)"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="en-IL"><u></u> <u></u></span></p>
</div>
</div>
-- <br>
Patentpractice mailing list<br>
<a href="mailto:Patentpractice@oppedahl-lists.com" target="_blank">Patentpractice@oppedahl-lists.com</a><br>
<a href="http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com" rel="noreferrer" target="_blank">http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com</a><br>
</div></blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><p class="MsoNormal" style="margin-top:10pt"><font size="2"><b><span><span><span><span><span><span><span></span></span></span></span></span></span></span></b></font></p><p style="margin:0px 0px 10px;color:rgb(102,127,160);font-family:"Open Sans",sans-serif,Arial;font-size:12px"><font size="2"><b><a border="0" href="https://www.iam-media.com/strategy300/individuals/david-boundy" style="color:rgb(102,127,160);text-decoration:none;outline:none;background:0px 0px transparent" target="_blank"><img alt="" height="92" width="73" src="https://ci3.googleusercontent.com/mail-sig/AIorK4wRMgBgcdZCqTw68Gg6ihENvW6_y8dGBqYvnJwiaIyu6LO5a7IJ-cljKsueIE5uxXbT6s9MN5hE2lGU"> <img alt="Cambridge Technology Law LLC" src="https://s3.amazonaws.com/keynectup/PROFILE/9b92f0cd-ecec-44c8-8932-60e8dc63709f/thumbnail.jpg?1455027242552" style="border-width: 0px; border-style: none; border-color: currentcolor; outline: 0px;" height="96" border="0" width="96"><br></a></b></font></p><font size="2"><b>
</b><p style="margin:0in 0in 0.0001pt"><a href="https://www.iam-media.com/strategy300/individuals/david-boundy" target="_blank"><span style="color:windowtext;text-decoration:none">Listed as one of the world's 300 leading intellectual property
strategists</span></a></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:windowtext;text-decoration:none">
</span><a href="http://ssrn.com/author=2936470" target="_blank">Articles at http://ssrn.com/author=2936470</a><a href="https://www.keynect.us/requestCardAccess/USA500DBOUN?" target="_blank"><span style="color:windowtext"><br></span></a></p><p style="margin:0in 0in 0.0001pt"><a href="https://www.keynect.us/requestCardAccess/USA500DBOUN?" target="_blank"><span style="color:windowtext">Click here to add me to your
contacts.</span></a></p><b>
<p style="margin:0px 0px 10px;color:rgb(102,102,102);font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span style="font-weight:700"></span></p><p style="margin:0px 0px 10px;font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span style="color:rgb(0,0,255)"><a href="https://www.iam-media.com/strategy300/individuals/david-boundy" target="_blank"><span style="font-weight:700">David Boundy</span></a></span></p><p style="margin:0px 0px 10px;color:rgb(102,102,102);font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span style="font-weight:700"></span></p><p style="margin:0px 0px 10px;color:rgb(102,102,102);font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span><span></span></span></p></b></font><p></p>
<p style="margin:0px 0px 10px;color:rgb(102,102,102);font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span><span><a href="mailto:dboundy@cambridgetechlaw.com" target="_blank">DBoundy@cambridgetechlaw.com</a> / <a href="tel:%2B1%206464729737" value="+16464729737" target="_blank">+1 646.472.9737</a></span></span></p><p style="margin:0px 0px 10px;color:rgb(102,102,102);font-family:"Open Sans",sans-serif,Arial;font-size:14px"><span><span><span style="font-weight:700">Cambridge Technology Law LLC</span></span><br>686 Massachusetts Avenue #201, Cambridge MA 02139<br><a href="http://www.CambridgeTechLaw.com" target="_blank">http://www.CambridgeTechLaw.com</a><br><a href="http://www.linkedin.com/in/DavidBoundy" target="_blank">http://www.linkedin.com/in/DavidBoundy</a><br></span></p>mailing address<div>PO Box 590638<br></div><div>Newton MA 02459<br></div></div></div><font size="1"><span style="line-height:150%;font-family:"Times New Roman""><br>This communication is
a confidential attorney-client communication intended only for the person named above or an authorized representative.<span> </span>Any
dissemination, distribution, or copying of this communication is strictly
prohibited, whether by the author or recipients.<span> </span>Any legal, business or tax information
contained in this communication, including attachments and enclosures, is not
intended as a thorough, in-depth analysis of specific issues, nor a substitute
for a formal opinion, nor is it sufficient to avoid legal or other adverse
consequences to the recipient. Unless you are the addressee (or authorized to
receive for the addressee), you may not copy, use, disclose or distribute this
communication or attribute to the Firm any information contained in this
communication. If you have received this communication in error, please advise
the sender by replying to this message or by telephone, and then promptly
delete it.</span></font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
-- <br>
Patentpractice mailing list<br>
<a href="mailto:Patentpractice@oppedahl-lists.com" target="_blank">Patentpractice@oppedahl-lists.com</a><br>
<a href="http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com" rel="noreferrer" target="_blank">http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com</a><br>
</blockquote></div></div>