DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This action is in response to the amendments filed on June 17, 2026. Claims 1, 6-8, 12, 17, and 21-24 are amended; and claims 1-24 are pending and examined below.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-3, 5-9, 11, 13-24 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Seidl et al. (U.S. 2007/0112800).
With regard to claim 1, Seidl teaches a system ([abstract]), comprising:
one or more processors (Fig. 1B, 112; Fig. 9, processor 912) configured to:
parse an email ([0004] data corresponding to website use is then stored in a database, so that the data can later be analyzed; [0049] receives updates to clickflow data automatically supplied by client server(s) 124. The updates might be one or more of an email being opened);
identify a URL link in the email ([0083] in order to determine that an email has been opened, an HTML image tag which requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email. The request for the small dummy image is in the form of a modified URL, which encodes the customer, visitor, activity, as well as other data relevant to the email. In one embodiment, the HTML image tag might resemble: <IMG SRC=http://www.salesgenius.rsvp1.com/W8e283223d WIDTH="1" HEIGHT="1">);
rewrite the URL link for execution in an isolation context based at least in
part on a security policy ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks); and
a memory coupled to the one or more processors and configured to provide one
or more processors with instructions (Fig. 9, main memory 904; [0029] a machine-readable medium includes read only memory ("ROM"); random access memory ("RAM"); [0106] System 900 further comprises a random access memory (RAM), or other dynamic storage device 904 (referred to as main memory) coupled to bus 911 for storing information and instructions to be executed by processor 912).
With regard to claim 2, the limitations are addressed above and Seidl teaches wherein the email is an inbound email ([0083] In response to receiving a notification, as discussed above, a visual indicator of the notification, such as icon 610, window 612, and/or the changed appearance of an icon 606a verses 606b, may be displayed on the client GUI. Therefore, when, for example, Robin Seidl has opened an email that includes tracking information, client servers detect an update in tracking data relevant to the client GUI).
With regard to claim 3, the limitations are addressed above and Seidl teaches wherein the URL links are rewritten before the URL is provided to a mailbox for an intended recipient of the email ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links; [0045] web services 114 logic may be configured to send notifications to a client whenever a user selects a specific link, traverses a sequence of pages, etc.; [0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636).
With regard to claim 5, the limitations are addressed above and Seidl teaches wherein the one or more processors are further configured to:
replace the URL in the email with the rewritten URL link to obtain a secure email ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [claim 7] replacing data items with one or more current data items); and
provide the secure email to an inbox for an intended recipient of the email (Fig. 6A; Figs. 7A-7B; [0083] Robin Seidl has opened an email that includes tracking information, client servers detect an update in tracking data relevant to the client GUI).
With regard to claim 6, the limitations are addressed above and Seidl teaches wherein the one or more processors are further configured to:
determine whether to rewrite the URL link for execution in the isolated context based at least in part on the security policy ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks).
With regard to claim 7, the limitations are addressed above and Seidl teaches wherein:
the one or more processors are further configured to obtain an identifier for an intended recipient of the email ([0033] rewriter server may store additional items of clickflow data such as time on page, timestamps, identity of the requester, time on site etc.); and
determining whether to rewrite the URL link comprises querying the security policy ([0063] Processing logic determines the online status of a client by either querying the client device or checking the on-line status of the client in the open client cache DB; [0064] Procession logic then, in one embodiment, determines that the current data update operation is the first time the client has made such a query, (i.e., a first time client query) (processing block 306); [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks), wherein the security policy is identified based at least in part on the identifier for the intended recipient ([0064] Procession logic then, in one embodiment, determines that the current data update operation is the first time the client has made such a query, (i.e., a first time client query) (processing block 306); [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks; [0102] The complex database queries are system and/or customer defined programmatic conditions which are utilized by the realtime database architecture to supply the GUI with results based on user-defined database queries).
With regard to claim 8, the limitations are addressed above and Seidl teaches wherein the security policy ([0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks) comprise a set of one or more rules dependent on one or more characteristics associated with the email ([0083] in order to determine that an email has been opened, an HTML image tag which requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email. The request for the small dummy image is in the form of a modified URL, which encodes the customer, visitor, activity, as well as other data relevant to the email; [0097] upon selection of view email, client GUI may display the e-mail which was opened by Robin Seidl within the GUI, or be configured to launch an e-mail client program to display the email).
With regard to claim 9, the limitations are addressed above and Seidl teaches wherein the one or more characteristics comprises a characteristic for at least one of a sender of the email ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links; [0045] web services 114 logic may be configured to send notifications to a client whenever a user selects a specific link, traverses a sequence of pages, etc.; [0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636), an intended recipient of the email ([0033] rewriter server may store additional items of clickflow data such as time on page, timestamps, identity of the requester, time on site etc.), and a category associated with the URL link ([0038] In one embodiment, customer account database 106 stores, among other items, customer URLs, customer contact information, customer names, customer addresses, modified URLs, etc.; [0094] results are displayed according to categories, such as "E-Mails Opened and Clicked," "E-Mails that have Only Been Opened," "Unopened Emails," etc. 844).
With regard to claim 11, the limitations are addressed above and Seidl teaches wherein the one or more rules pertain to inspection ([0005] a customer would be required to request an update which would in turn initiate a data inspection. From the customer initiated data inspection, if there was an update to data stored in a database, the new data could be supplied; [0023] Because the data currently being displayed, and not the multiple items that may be displayed, is utilized for comparison, the amount of data needed for inspection is reduced), downloading, or data loss prevention.
With regard to claim 13, the limitations are addressed above and Seidl teaches wherein the one or more processors are further configured to obtain email header information from the email ([0066] processing logic uses a HTTP header parameter Keep Alive in order to maintain the connection).
With regard to claim 14, the limitations are addressed above and Seidl teaches wherein the URL link is rewritten specific ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160) for an intended recipient of the email ([0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636).
With regard to claim 15, the limitations are addressed above and Seidl teaches wherein rewriting the URL link comprises generating an envelope data structure ([0103] when client GUI 700 is displaying "All Contacts," an icon representing an envelop may appear on or next to a data item) comprising the URL and a set of metadata (Fig. 7A, GUI 700; [abstract] a plurality of data items displayable by a client, one or more relevant data items to be supplied to the client, the plurality of data items displayable by a client located in a first database corresponding to a tracked user's interactions with a website).
With regard to claim 16, the limitations are addressed above and Seidl teaches wherein the set of metadata comprises a context associated with the email or an intended recipient of the email ([0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636).
With regard to claim 17, the limitations are addressed above and Seidl teaches wherein the envelope is used to facilitate applying a security policy ([0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks) in connection with a clicking of the rewritten URL link embedded in the email ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160).
With regard to claim 18, the limitations are addressed above and Seidl teaches wherein:
the URL link is rewritten in connection ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160) with a first user receiving the email ([0034] Rewriter server 160 then supplies 180d the web site with the modified links to client user 155. Therefore, for subsequent requests for web content received from client user 155);
the one or more processors are further configured to:
receive, from the first user, a request to send to a second user the email ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links; [0045] web services 114 logic may be configured to send notifications to a client whenever a user selects a specific link, traverses a sequence of pages, etc.; [0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636) comprising the rewritten URL link ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160); and
in response to receiving the request, rewrite the rewritten URL link based at least in part on the second user ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0104] when a contact is selected from "All Contacts," options are displayed in window 722).
With regard to claim 19, the limitations are addressed above and Seidl teaches wherein rewriting the rewritten URL link comprises unwinding the rewriting of the URL link ([0097] When the client GUI 600 has received a notification 612, the notification may include an icon or region 614 which, when selected, close the notification and remove it from the current client GUI 600).
With regard to claim 20, the limitations are addressed above and Seidl teaches wherein the rewritten URL link is embedded in an envelope data structure embedded in the email ([0103] when client GUI 700 is displaying "All Contacts," an icon representing an envelop may appear on or next to a data item), and the unwinding the rewritten URL link based at least in part on extracting address for the URL link from the envelope data structure ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0097] When the client GUI 600 has received a notification 612, the notification may include an icon or region 614 which, when selected, close the notification and remove it from the current client GUI 600) and inserting a native link to the address for the URL link ([0032] request 180a is received by rewriter server 160 when client user 155 selects a modified link which is modified to resemble a link to website server 165, but which resolves at rewriter server 160; [0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160. Rewriter server 160 then supplies 180d the web site with the modified links to client user 155).
With regard to claim 21, the limitations are addressed above and Seidl teaches wherein the rewritten URL link is further rewritten based at least in part on a policy to be enforced with respect to the second user ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0104] when a contact is selected from "All Contacts," options are displayed in window 722).
With regard to claim 22, Seidl teaches a method ([abstract]), comprising:
parsing an email ([0004] data corresponding to website use is then stored in a database, so that the data can later be analyzed; [0049] receives updates to clickflow data automatically supplied by client server(s) 124. The updates might be one or more of an email being opened);
identifying a URL link in the email ([0083] in order to determine that an email has been opened, an HTML image tag which requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email. The request for the small dummy image is in the form of a modified URL, which encodes the customer, visitor, activity, as well as other data relevant to the email. In one embodiment, the HTML image tag might resemble: <IMG SRC=http://www.salesgenius.rsvp1.com/W8e283223d WIDTH="1" HEIGHT="1">); and
rewriting the URL link for execution in an isolation context based at least in part on a security policy ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks).
With regard to claim 23, Seidl teaches a computer program product embodied in a non-transitory computer readable medium and comprising computer instructions ([0029] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer)) for:
parsing an email ([0004] data corresponding to website use is then stored in a database, so that the data can later be analyzed; [0049] receives updates to clickflow data automatically supplied by client server(s) 124. The updates might be one or more of an email being opened);
identifying a URL link in the email ([0083] in order to determine that an email has been opened, an HTML image tag which requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email. The request for the small dummy image is in the form of a modified URL, which encodes the customer, visitor, activity, as well as other data relevant to the email. In one embodiment, the HTML image tag might resemble: <IMG SRC=http://www.salesgenius.rsvp1.com/W8e283223d WIDTH="1" HEIGHT="1">); and
rewriting the URL link for execution in an isolation context based at least in part on a security policy ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks).
With regard to claim 24, Seidl teaches a method, comprising:
receiving a request to send an email comprising one or more rewritten URL links ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links; [0045] web services 114 logic may be configured to send notifications to a client whenever a user selects a specific link, traverses a sequence of pages, etc.; [0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636);
determining a security policy to enforce with respect to a sending of the email ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks);
rewriting the one or more rewritten URL links based at least in part on the policy to be enforced with respect to the sending of the email ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160. Rewriter server 160 then supplies 180d the web site with the modified links to client user 155. Therefore, for subsequent requests for web content received from client user 155, control again returns to rewriter server 160 in order to store clickflow data in tracking database 175 and supply modified web pages to client user 155);
modify the email based on the rewriting of the one or more rewritten URL links ([0049] Thin client 126 receives updates to clickflow data automatically supplied by client server(s) 124. The updates might be one or more of an email being opened, a web site being requested, a chat session taking place, etc. The updates are received by the thin client 126 in pseudo real time while thin client 126 is open); and
causing the email to be sent ([0083] Robin Seidl has opened an email that includes tracking information, client servers detect an update in tracking data relevant to the client GUI. In one embodiment, in order to determine that an email has been opened, an HTML image tag which requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 4, 10 and 12 are rejected under 35 U.S.C. 103 as being unpatentable over Seidl et al. (U.S. 2007/0112800) in view of Bravery et al. (U.S. 2012/0180039)
With regard to claim 4, the limitations are addressed above. However, Seidl does not specifically teach:
- wherein executing the link in the isolation context comprises using a container to process content associated with the URL in a cloud security service
Bravery teaches a method for multi-tenant enabling a service including a plurality of service components [abstract]. Bravery also teaches an isolation context ([0022] Isolation requirements: in order to ensure that one tenant's access to the service does not interfere with another tenant's use of the service, the service provider associates isolation requirements with the components of the service; [0026] Shared container: a real or virtualized environment where at least one shared component lives and is granted appropriate isolation in the context of the platform; [0028] The platform-as-a-service 100 includes containers 130A, 130B, and 130C (either shared and/or isolated)) using a container to process content ([0024] Containers: virtualized environments used by components of the service that require the strongest isolation. Containers (also referred to herein as "tenant containers") have the highest level of isolation. For example, the assets related to an application developed by a developer within the context of the offered service are unique to that tenant and therefore must be isolated in a container that is associated with the particular tenant; [0026] Shared container: a real or virtualized environment where at least one shared component lives and is granted appropriate isolation in the context of the platform) associated with the URL ([0035] the containers
(isolation and/or shared) are configured to specify URL (web address) patterns that define access to one or more application resources supplied and stored by the containers; [0039] the configuration of the routing directs requests to the service components via HTTP URLs through the nested virtualization environment into the respective tenant container) in a cloud security service ([0054] Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure; [0058] the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations)). Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains to have modified the URLs or hyperlinks in an email as taught by Seidl, with the cloud computing and container to process content as taught by Bravery, to have achieved a virtualization environment including an isolation container having a rewrite server URL link.
With regard to claim 10, the limitations are addressed above and Seidl teaches wherein the characteristics for the intended recipient of the email ([0034] rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links; [0045] web services 114 logic may be configured to send notifications to a client whenever a user selects a specific link, traverses a sequence of pages, etc.; [0090] GUI 600 includes a region 626 that displays information for an individual being tracked, such as Robin Seidl, or selected recipients of a specific email "BOD Test" 636) comprises one or more of a user identifier ([0033] identity of the requester). However, Seidl does not specifically teach:
- comprises a tenant identifier
Bravery teaches a method for multi-tenant enabling a service including a plurality of service components [abstract]. Bravery also comprises a tenant identifier ([0019] Tenant: a user, group of related users, or a system that is entitled to use the service offered by the service provider through a platform; [0022] Isolation requirements: in order to ensure that one tenant's access to the service does not interfere with another tenant's use of the service; [0024]-[0025] containers are referred to as tenant containers… A shared database is used to track information about each tenant container; [0029] FIG. 2 illustrates components of a platform according to an embodiment of the invention. In order to create a tenant container in an automated fashion, a developer and/or owner of an application (i.e., "tenant-user") 202 initiates provisioning of a container via a web interface, which is contained in a management module 208). Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains to have modified the URLs or hyperlinks in an email as taught by Seidl, with the tenant identifier as taught by Bravery, to have achieved a virtualization environment including an isolation container having a rewrite server URL link.
With regard to claim 12, the limitations are addressed above and Seidl teaches wherein the one or more processors are further configured to:
obtain from the email a user identifier ([0033] identity of the requester); and
perform a security policy lookup to obtain the security policy ([0041] back end processor 112 performs a look-up to correlate a link with a person being tracked before link selection is stored in one or more of databases 106-110; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks), wherein the security policy lookup is performed based at least in part on the user identifier ([0033] identity of the requester; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks). However, Seidl does not specifically teach:
- tenant information
Bravery teaches a method for multi-tenant enabling a service including a plurality of service components [abstract]. Bravery also comprises a tenant identifier ([0019] Tenant: a user, group of related users, or a system that is entitled to use the service offered by the service provider through a platform; [0022] Isolation requirements: in order to ensure that one tenant's access to the service does not interfere with another tenant's use of the service; [0024]-[0025] containers are referred to as tenant containers… A shared database is used to track information about each tenant container; [0029] FIG. 2 illustrates components of a platform according to an embodiment of the invention. In order to create a tenant container in an automated fashion, a developer and/or owner of an application (i.e., "tenant-user") 202 initiates provisioning of a container via a web interface, which is contained in a management module 208). Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains to have modified the URLs or hyperlinks in an email as taught by Seidl, with the tenant identifier as taught by Bravery, to have achieved a virtualization environment including an isolation container having a rewrite server URL link.
Response to Arguments
Applicant's arguments filed 06-17-2026 have been fully considered but they are not persuasive. Applicant supports the remarks, by stating that the Seidl reference is fundamentally an analytics and click flow tracking tool used for marketing purposes and not a security system for protecting recipients from malicious links embedded in emails, required by the claim language. Examiner respectfully disagrees with Applicant:
The Seidl reference teaches a system for automatically supplying data items to a client from among a plurality of data items displayed by a client [abstract]. Seidl teaches that the data which corresponds to a website is stored in a database for the data to be analyzed [0004]. Seidl teaches updates which automatically supplied by client servers and that one or more of the updates can be opened [0049]. This is shown to parse an email which is given updates. Further, a URL link is identified in the email, which paragraph [0083] shows that an HTML image tag requests a small dummy image from tracking server(s) is included in the HTML bodytext of the sent email. The modified URL link is included in the HTML bodytext of the sent email. Furthermore, Seidl teaches that a server, in this case the rewriter server, can request a website from the website server, then receive the requested web site from the website server, and rewrite the uniform resource locator or the URL links and additional links to the website server ([0034] Rewriter server 160 then requests a website 180b, corresponding to link selection 180a, from website server 165. Rewriter server then receives the requested web site 180c from website server 165. In one embodiment, rewriter server 160 rewrites uniform resource locator (URL) links, as well as other links, within the received web page to resemble links to website server 165, but to again resolve at rewriter server 160; [0066] data is pushed to a client using HTTP protocol over port 80. Data is pushed by processing logic over port 80 in order to avoid the installation, configuration, and/or alteration of security software on corporate networks). The independent claims do not require that a system, particularly a security system, be in place for protection from suspicious links which are embedded in emails. As such, the Examiner asserts that the Seidl reference teaches the limitations of the claim language. Examiner recommends that Applicant support the independent claims by placing such language to show that a protection is in place for suspicious links embedded in emails.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANDREA C. LEGGETT whose telephone number is (571)270-7700. The examiner can normally be reached M-F 9am-5pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kieu Vu can be reached at 571-272-4057. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/ANDREA C LEGGETT/Primary Examiner, Art Unit 2171
Prosecution Insights