DETAILED ACTION
This Office Action is in response to the application 18/898,434 filed on September 26th, 2024.
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 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.
Claims 1-20 are pending and herein considered.
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 .
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP §§ 706.02(l)(1) - 706.02(l)(3) for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claim 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-19 of U.S. Patent No. 12,125,028.
Instant Application 18/898,434
U.S. Patent No. 12,125,028
Claim 1:
A system for configuring access tokens with Uniform Resource Locator (URL) parameters to authorize web-browser-initiated network operations, the system comprising:
one or more memory devices storing instructions; and
one or more processors executing computer program instructions that, when executed, cause operations comprising:
detecting, based on a monitoring of web browsing interactions, a user input associated with a first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token at a web browsing application, based on user account information associated with a user, wherein the access token is associated with (i) an authentication credential and (ii) one or more network operation parameters;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters related to the request to access the resources associated with the first website;
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first URL domain network operation parameter associated with the first website, wherein subsequent use of the access token is restricted to websites associated with the first URL domain network operation parameter;
receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website, the second network operation parameters comprising a respective second network operation parameter that does not correspond to the first URL domain network operation parameter; and
in response to the respective second network operation parameter of the second network operation parameters not corresponding to the first URL domain network operation parameter, denying the second authorization request.
Claim 3:
A method comprising:
generating an access token based on user specific information associated with a user to access one or more resources, wherein the access token is associated with one or more network operation parameters;
receiving an authorization request to authorize a first network operation associated with accessing resources associated with a first website, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters, the first network operation being successfully authorized based on the authorization request;
in response to the successful authorization of the first network operation based on the authorization request, binding the access token to a first identifier parameter associated with the first website;
receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website, the second network operation parameters comprising a respective second network operation parameter that corresponds to the first identifier parameter; and
in response to the respective second network operation parameter of the second network operation parameters corresponding to the first identifier parameter, approving the second authorization request.
Claim 12:
One or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors, cause operations comprising:
generating an access token associated with (i) one or more token parameters and (ii) user specific information associated with a user;
receiving an authorization request to authorize a first network operation associated with a first website, wherein the authorization request comprises the access token; and
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first identifier associated with the first website, wherein, in connection with the binding, subsequent use of the access token is restricted to websites associated with the first identifier.
Claim 1:
A system for configuring access tokens with Uniform Resource Locator (URL) parameters to authorize web-browser-initiated network operations, the system comprising:
one or more memory devices storing instructions; and
one or more processors executing computer program instructions that, when executed, cause operations comprising:
monitoring web browsing interactions with a web browsing application on a user device associated with a user accessing a first website;
detecting, based on the monitoring of the web browsing interactions, a user input at a data exchange gateway associated with the first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token at the web browsing application, based on user account information associated with the user, wherein the access token is associated with (i) an authentication credential and (ii) one or more network operation parameters;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters related to the request to access the resources associated with the first website;
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first URL domain network operation parameter associated with the first website, wherein subsequent use of the access token is restricted to websites associated with the first URL domain network operation parameter;
receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website, the second network operation parameters comprising a respective second network operation parameter that does not match the first URL domain network operation parameter; and
in response to a lack of a match between the respective second network operation parameter of the second network operation parameters and the first URL domain network operation parameter, denying the second authorization request, wherein the respective second network operation parameter lacks the match to the first URL domain network operation parameter.
Claim 3:
A method comprising:
detecting a user input from a user at a data exchange gateway associated with a first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token based on user specific information associated with the user, wherein the access token is associated with one or more network operation parameters;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters, the first network operation being successfully authorized based on the authorization request;
in response to the successful authorization of the first network operation based on the authorization request, binding the access token to a first URL identifier parameter associated with the first website;
receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website, the second network operation parameters comprising a respective second network operation parameter that matches the first URL identifier parameter; and
in response to a matching between the respective second network operation parameter of the second network operation parameters and the first URL identifier parameter, approving the second authorization request, wherein the respective second network operation parameter matches the first URL identifier parameter.
Claim 12:
One or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors, cause operations comprising:
detecting a user input from a user at a first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token, wherein the access token is associated with one or more token parameters, wherein generating the access token further comprises receiving the user input from the user, wherein the user input indicates an intent to generate the access token, comparing a first identifier associated with the first website to a set of predetermined identifiers, and generating the access token in response to the first identifier failing to match at least one of the predetermined identifiers of the set of predetermined identifiers;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises the access token; and
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first website identifier associated with the first website, wherein, in connection with the binding, subsequent use of the access token is restricted to websites associated with the first website identifier.
Claim 1 is rejected on the ground of nonstatutory double patenting as being unpatentable over claim 1 of U.S. Patent No. 11,757,896.
Instant Application 18/898,434
U.S. Patent No. 11,757,896
Claim 1:
A system for configuring access tokens with Uniform Resource Locator (URL) parameters to authorize web-browser-initiated network operations, the system comprising:
one or more memory devices storing instructions; and
one or more processors executing computer program instructions that, when executed, cause operations comprising:
detecting, based on a monitoring of web browsing interactions, a user input associated with a first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token at a web browsing application, based on user account information associated with a user, wherein the access token is associated with (i) an authentication credential and (ii) one or more network operation parameters;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters related to the request to access the resources associated with the first website;
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first URL domain network operation parameter associated with the first website, wherein subsequent use of the access token is restricted to websites associated with the first URL domain network operation parameter;
receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website, the second network operation parameters comprising a respective second network operation parameter that does not correspond to the first URL domain network operation parameter; and
in response to the respective second network operation parameter of the second network operation parameters not corresponding to the first URL domain network operation parameter, denying the second authorization request.
Claim 1:
A system for configuring access tokens with Uniform Resource Locator (URL) parameters to authorize web-browser-initiated network operations, the system comprising:
one or more memory devices storing instructions; and
one or more processors executing computer program instructions that, when executed, cause operations comprising: monitoring web browsing interactions with a web browsing application on a user device associated with a user accessing a first website;
detecting, based on the monitoring of the web browsing interactions, a user input at a data exchange gateway associated with the first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website;
in response to the detected user input, generating an access token at the web browsing application, based on user account information associated with the user, wherein the access token is associated with (i) an authentication credential and (ii) one or more network operation parameters;
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters related to the request to access the resources associated with the first website;
in response to a successful authorization of the first network operation based on the authorization request, binding the access token to a first URL domain network operation parameter associated with the first website, wherein subsequent use of the access token is restricted to websites associated with the first URL domain network operation parameter;
detecting, based on the monitoring, a second user input at a second data exchange gateway associated with a second website to perform a second network operation, wherein the second network operation is associated with a request to access second resources associated with the second website;
receiving a second authorization request to authorize the second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to the request to access the second resources associated with the second website;
comparing the second network operation parameters associated with the second network operation to the first URL domain network operation parameter associated with the access token; and
in response to the comparison failing to indicate a match between a respective second network operation parameter of the second network operation parameters with the first URL domain network operation parameter, invalidating the authorization request.
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.
(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.
Claim 12 is rejected under 35 U.S.C. 102(a)(1) as being anticipated by Helander et al. (Helander), U.S. Pub. Number 2011/0154130.
Regarding claim 12; Helander discloses one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors, cause operations comprising:
generating an access token associated with (i) one or more token parameters and (ii) user specific information associated with a user (pars. 0056 & 0062; figs. 5 & 6; the control logic 205 can be a means to generate a token based on the secure user identifier and a random element (e.g., a time stamp); the service API 113 generates a token to associate the developer key, user information, and/or initiated session; the token includes random element (e.g., based on a time stamp or other selected information) to facilitate generation of unique tokens.);
receiving an authorization request to authorize a first network operation associated with a first website, wherein the authorization request comprises the access token (pars. 0059 & 0062; fig. 6; the service portal 201 provides the authentication information to an account manager 203 that has access to a database including the authentication credentials for the user, other user information, and what services the user has access to; the web browser 109 receives an instruction to create another iframe to the callback resource identifier with the token included.); and
in response to a successful authorization of the first network operation based on the authorization request (par. 0059; fig. 6; based on the authentication credentials, the account manager 203 generates a secure user identifier (e.g., a hash of the user authentication information and a key (e.g., based on a time stamp).), binding the access token to a first identifier associated with the first website, wherein, in connection with the binding, subsequent use of the access token is restricted to websites associated with the first identifier (par. 0060; fig. 6; the web browser 109 initiates the creation of an inline iframe using a developer key, then sets up XSS; the XSS in the browser 109 for API use may be the inline frame associated with the domain of the service API 113; the web browser sends a request to initiate, with the developer key, a communication channel with the service API 113; the request may be a web URL executed by the web browser in the iframe, the web URL including the developer key.).
Claim Rejections - 35 USC § 103
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 1-11 and 13-20 are rejected under 35 U.S.C 103 as being unpatentable over Helander et al. (Helander), U.S. Pub. Number 2011/0154130, in view of Effing, U.S. Pub. Number US 2021/0352072.
Regarding claim 1; Helander discloses a system (par. 0065; fig. 7; a computer system 700.) for configuring access tokens with Uniform Resource Locator (URL) parameters to authorize web-browser-initiated network operations, the system comprising:
one or more memory devices storing instructions (par. 0068; fig. 7; a memory 704.); and
one or more processors (par. 0066; fig. 7; one or more processors 702.) executing computer program instructions (par. 0067; fig. 7; the computer program code is a set of instructions or statements providing instructions.) that, when executed, cause operations comprising:
detecting, based on a monitoring of web browsing interactions, a user input associated with a first website to perform a first network operation, wherein the first network operation is associated with a request to access resources associated with the first website (pars. 0026 & 0059; fig. 6; the web browser utilizes to receive input via the UE 101; the web browser 109 provides authentication information to the service portal 201 associated with the user; the authentication information includes a user name and password the user has with the web services platform 111.);
in response to the detected user input, generating an access token at a web browsing application, based on user account information associated with a user, wherein the access token is associated with (i) an authentication credential and (ii) one or more network operation parameters (pars. 0056 & 0062; figs. 5 & 6; the control logic 205 can be a means to generate a token based on the secure user identifier and a random element (e.g., a time stamp); the service API 113 generates a token to associate the developer key, user information, and/or initiated session; the token includes random element (e.g., based on a time stamp or other selected information) to facilitate generation of unique tokens.);
receiving an authorization request to authorize the first network operation, wherein the authorization request comprises (i) the access token and (ii) first network operation parameters related to the request to access the resources associated with the first website (pars. 0059 & 0062; fig. 6; the service portal 201 provides the authentication information to an account manager 203 that has access to a database including the authentication credentials for the user, other user information, and what services the user has access to; the web browser 109 receives an instruction to create another iframe to the callback resource identifier with the token included.);
in response to a successful authorization of the first network operation based on the authorization request (par. 0059; fig. 6; based on the authentication credentials, the account manager 203 generates a secure user identifier (e.g., a hash of the user authentication information and a key (e.g., based on a time stamp).), binding the access token to a first URL domain network operation parameter associated with the first website (par. 0060; fig. 6; the web browser 109 initiates the creation of an inline iframe using a developer key, then sets up XSS; the XSS in the browser 109 for API use may be the inline frame associated with the domain of the service API 113; the web browser sends a request to initiate, with the developer key, a communication channel with the service API 113; the request may be a web URL executed by the web browser in the iframe, the web URL including the developer key.), wherein subsequent use of the access token is restricted to websites associated with the first URL domain network operation parameter (par. 0062; fig. 6; the resource identifier include a [root domain], a bridge, and fragment data to provide the communication information; for instance, the resource identifier may be [root domain]/bridge/#{JSONDATA}; the JSONDATA includes the service data, the token, and other content that may be transferred from the domain of the service API 113 to the domain of the web page (the first domain); the JSONDATA may be split into smaller fragments and sent in multiple data transfers; this can be useful in data transfers because web browsers may have restrictions to the length of URLs.);
the second network operation parameters comprising a respective second network operation parameter that does not correspond to the first URL domain network operation parameter; and in response to the respective second network operation parameter of the second network operation parameters not corresponding to the first URL domain network operation parameter, denying the second authorization request (par. 0049; fig. 4; the received service data including an authentication token generated by the web services platform 111.).
Helander fails to explicitly disclose receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website.
However, in the same field of endeavor, Effing discloses web access control method comprising receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website (Effing: pars. 0056 & 0059; the subsequent browser ID access can be checked against this timestamp and rejected if expired; QR-reader apps send an HTTP request and open a separate browser when scanning a web URL; as the first request already registers a browser ID using the QR-reader app identification, the subsequent browser request might be unduly rejected.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teaching of Effing into the method and apparatus of Helander comprising receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises (i) the access token and (ii) second network operation parameters related to second resources associated with a second website to ensure that the content is accessed by the allowed number of users without requiring the introduction and sharing of passwords, nor the supervision of an administrator of the web (Effing: par. 0001).
Regarding claim 2; Helander and Effing disclose the system of claim 1, Helander further discloses the operations comprising: receiving a third authorization request to authorize a third network operation, wherein the third authorization request comprises (i) the access token and (ii) third network operation parameters related to third resources associated with a third website; and in response to a respective third network operation parameter of the third network operation parameters corresponding to the first URL domain network operation parameter, approving the third authorization request (Helander: pars. 0059 & 0062; fig. 6; the service portal 201 provides the authentication information to an account manager 203 that has access to a database including the authentication credentials for the user, other user information, and what services the user has access to; the web browser 109 receives an instruction to create another iframe to the callback resource identifier with the token included.).
Regarding claim 3; Claim 3 is directed to a method which has similar scope as claim 1. Therefore, claim 3 remains un-patentable for the same reasons.
Regarding claim 4; Claim 4 is directed to the method of claim 3 which has similar scope as claim 2. Therefore, claim 4 remains un-patentable for the same reasons.
Regarding claim 5; Helander and Effing disclose the method of claim 4, wherein Helander further discloses the denying of the third authorization request prevents access to the third resources associated with the third website (Helander: par. 0044; the [hacker root] website is unable to access the authentication key and utilize more services from the web services platform 111.).
Regarding claim 6; Helander and Effing disclose the method of claim 3, wherein Helander further discloses generating the access token further comprises: receiving a user input from the user, wherein the user input indicates an intent to generate the access token; comparing a first website identifier associated with the first website to a set of predetermined website identifiers, the comparison indicating that the first website identifier fails to match at least one of the predetermined website identifiers of the set of predetermined website identifiers; and generating the access token in response to the first website identifier failing to match the at least one of the predetermined website identifiers of the set of predetermined website identifiers (Helander: pars. 0026 & 0059; fig. 6; the web browser utilizes to receive input via the UE 101; the web browser 109 provides authentication information to the service portal 201 associated with the user; the authentication information includes a user name and password the user has with the web services platform 111.).
Regarding claim 7; Helander and Effing disclose the method of claim 3, Helander further discloses comprising: receiving a user input from the user, wherein the user input indicates an intent to use a previously generated token; determining that a first website identifier associated with the first website matches at least one network operation parameter of a previously generated access token; and in response to the first website identifier matching the at least one network operation parameter of the previously generated access token, using the previously generated access token to authorize the first network operation (Helander: pars. 0056 & 0062; figs. 5 & 6; the control logic 205 can be a means to generate a token based on the secure user identifier and a random element (e.g., a time stamp); the service API 113 generates a token to associate the developer key, user information, and/or initiated session; the token includes random element (e.g., based on a time stamp or other selected information) to facilitate generation of unique tokens.).
Regarding claim 8; Helander and Effing disclose the method of claim 3, Helander further discloses comprising: subsequent to the access token being bound to the first identifier parameter, storing the access token bound to the first identifier parameter in a database (Helander: par. 0046; the sign-on information is stored in memory associated with the web browser.).
Regarding claim 9; Helander and Effing disclose the method of claim 3, wherein Effing further discloses the binding restricts subsequent use of the access token to websites associated with the first identifier parameter (Effing: par. 0058; a failure per IP address rate limiter, to protect against brute force attacks.).
Regarding claim 10; Helander and Effing disclose the method of claim 3, wherein Effing further discloses the first identifier is a URL identifier (Effing: par. 0058; a failure per IP address rate limiter, to protect against brute force attacks.).
Regarding claim 11; Helander and Effing disclose the method of claim 3, wherein Helander further discloses the first identifier is a merchant identifier (Helander: par. 0031; a user identifier.).
Regarding claim 13; Helander discloses media of claim 12.
Helander fails to explicitly disclose receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises the access token; and in response to a second network operation parameter associated with the second network operation failing to correspond to the first identifier associated with the access token, denying the second authorization request.
However, in the same field of endeavor, Effing discloses web access control method comprising receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises the access token; and in response to a second network operation parameter associated with the second network operation failing to correspond to the first identifier associated with the access token, denying the second authorization request (Effing: pars. 0056 & 0059; the subsequent browser ID access can be checked against this timestamp and rejected if expired; QR-reader apps send an HTTP request and open a separate browser when scanning a web URL; as the first request already registers a browser ID using the QR-reader app identification, the subsequent browser request might be unduly rejected.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teaching of Effing into the method and apparatus of Helander comprising receiving a second authorization request to authorize a second network operation, wherein the second authorization request comprises the access token; and in response to a second network operation parameter associated with the second network operation failing to correspond to the first identifier associated with the access token, denying the second authorization request to ensure that the content is accessed by the allowed number of users without requiring the introduction and sharing of passwords, nor the supervision of an administrator of the web (Effing: par. 0001).
Regarding claim 14; Claim 14 is directed to the media of claim 13 which has similar scope as claim 5. Therefore, claim 14 remains un-patentable for the same reasons.
Regarding claim 15; Claim 15 is directed to the media of claim 13 which has similar scope as claim 2. Therefore, claim 15 remains un-patentable for the same reasons.
Regarding claim 16; Claim 16 is directed to the media of claim 15 which has similar scope as claim 6. Therefore, claim 16 remains un-patentable for the same reasons.
Regarding claim 17; Claim 17 is directed to the media of claim 12 which has similar scope as claim 7. Therefore, claim 17 remains un-patentable for the same reasons.
Regarding claim 18; Claim 18 is directed to the media of claim 12 which has similar scope as claim 8. Therefore, claim 18 remains un-patentable for the same reasons.
Regarding claim 19; Claim 19 is directed to the media of claim 12 which has similar scope as claim 9. Therefore, claim 19 remains un-patentable for the same reasons.
Regarding claim 20; Claim 20 is directed to the media of claim 12 which has similar scope as claim 10. Therefore, claim 20 remains un-patentable for the same reasons.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KHOI V LE whose telephone number is (571)270-5087. The examiner can normally be reached 9:00 AM - 5:00 PM EST.
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, Shewaye Gelagay can be reached on 571-272-4219. 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.
/KHOI V LE/
Primary Examiner, Art Unit 2436