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 .
DETAILED ACTION
Notice of Pre-AIA or AIA Status
Claims 21-41 are pending in this application. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 3/26/2025 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
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 § 2146 et seq. 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.
Claims 21-41 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1 and 12 of U.S. Patent No. 12,124,526. Although the claims at issue are not identical, they are not patentably distinct from each other because one of ordinary skill in the art would have known that all of the limitations in the current application are disclosed in patent 12,124,526 which includes extra features in the claim limitation.
With respect to claim 21, Patent ‘526 discloses A method comprising: receiving, by a server system, a request from a computing device, wherein the request
comprises an identifier of content (claim 1);
finding, by the server system and based on the identifier of content, a set of two or more routing policies that have been associated with the content (claim 1);
composing, by the server system, a target uniform resource identifier using at least one of the routing policies to determine how to parse the identifier of content and based on one or more attributes comprising at least one variable evaluated at the time of the composing (claim 1); and
redirecting, by the server system, the computing device to the target uniform resource identifier (claim 1).
With respect to claim 41, Patent ‘526 discloses a system comprising:
a client computing device (claim 12); and
one or more server computers operable to interact with the client computing device, the one or more computers comprising a non-transitory computer-readable medium tangibly encoding a computer program operable to cause the server one or more computers to perform operations comprising receiving a request from the client computing device, wherein the request comprises an identifier of content (claim 12),
finding, based on the identifier of content, a set of two or more routing policies that have been associated with the content (claim 12),
composing a target uniform resource identifier using at least one of the routing policies to determine how to parse the identifier of content and based on one or more attributes comprising at least one variable evaluated at the time of the composing (claim 12), and
redirecting the client computing device to the target uniform resource identifier (claim 12).
With respect to claims 22-40, they are dependent off claim 21 and therefore are rejected for the same reasons above.
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 21 and 23-41 are rejected under 35 U.S.C. 103 as being unpatentable over Trifa (US 2014/0181256) and in view of Grant (US 2015/0170072).
Re Claim 21, Trifa discloses a method comprising:
finding, by the server system and based on the identifier of content, a set of two or more routing policies that have been associated with the content ([0075], rules database stores rules for each one of the short URL, where each rule points to a different target URL.);
composing, by the server system, a target uniform resource identifier using at least one of the routing policies to determine how to parse the identifier of content and based on one or more attributes comprising at least one variable evaluated at the time of the composing ([0078]-[0081], Short URL includes an ID in which the target URI now includes the ID from the Short URL.); and
redirecting, by the server system, the computing device to the target uniform resource identifier ([0078]-[0081], the redirector front-end will check the addition of additional parameters with the HTTP request and return a unique target URL.).
Trifa does not disclose, however Grant discloses receiving, by a server system, a request from a computing device, wherein the request comprises an identifier of content ([0214]-[0218],the URL request is redirected via DNS redirect server. The server receives the redirected request and selectively rewrites URL using a rewrite engine). Trifa and Grant are analogous art because they both disclose URL redirects.
It would have been obvious for one of ordinary skill in the art before the date the current invention was effectively filed to have modified the teachings of Trifa’s URL redirect with Grant’s server that provides a rewrite engine for URL redirect. One of ordinary skill in the art would have been motivated to incorporate the teachings with one another in order to have a rewrite engine for rewriting URLs for a URL redirect.
Re Claim 23, Trifa discloses wherein the at least one of the routing policies includes a specification for how to parse the identifier of content, the at least one variable specifies at least one piece of the identifier of content, and the composing comprises adding the at least one piece of the identifier of content to the target uniform resource identifier ([0081]-[0083], the redirector will extract the location from the request using where header and other such as who.).
Re Claim 24, Trifa discloses retrieving metadata that is associated with the content; and adding at least a portion of the metadata to the target uniform resource identifier ([0078]-[0081], Short URL includes an ID in which the target URI now includes the ID from the Short URL.).
Re Claim 25, Trifa discloses wherein the retrieving comprises calling an application programming interface of a product tracking system ([0060], [0095], Unique-object address identifier to be attached to a physical product. internal admin application which can used only by the manufacturer to track and trace the location of a product and its status).
Re Claim 26, Trifa discloses wherein the one or more attributes include at least one attribute that is not included in the request, and the composing comprises:
retrieving the at least one attribute ([0049], application request the user to share the location, etc.);
validating the at least one attribute ([0049], user can authorize the application to access their location and share GPS coordinates); and
using the at least one attribute to compose the target uniform resource identifier ([0083]-[0084], map the current GPS coordinates of the mobile device into the actual string used to describe locations in the redirection table and return a unique target URL).
Re Claim 27, Trifa discloses wherein the metadata comprises lot information, expiration date, current product state, born on information, recall information, or a combination thereof ([0055], specific information such as date of manufacture).
Re Claim 28, Trifa discloses wherein the retrieving comprises using a product serial number extracted from the request when calling the application programming interface of the product tracking system ([0055], unique serial number).
Re Claim 29, Trifa discloses wherein the set of two or more routing policies are from multiple routing policies that map codes to locations of relevant information, and the method comprises changing mappings of the codes to the locations ([0080]-[0081], table 1, utilizes the location for different rules for the short URL).
Re Claim 30, Trifa discloses wherein each of the multiple routing policies includes a template that defines a structure of a target uniform resource identifier to be composed based on static and variable content ([0007], [0080]-[0081], location-dependent information is done with the same application template. table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.).
Re Claim 31, Trifa discloses, comprising using a decision tree to derive the at least one of the routing policies in accordance with criteria elements used in constructing target uniform resource identifiers ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.).
Re Claim 32, Trifa discloses wherein the criteria elements used in constructing target uniform resource identifiers determine which display elements or web components within a destination webpage are to be shown to or be hidden from a user based on presence or absence of particular criteria 0080]-[0081], location-dependent information is done with the same application template. table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc. and shown in the target URI).
Re Claim 33, Trifa discloses wherein the criteria elements used across the set of two or more routing policies are not mutually exclusive ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.).
Re Claim 34, Trifa discloses wherein the identifier of content comprises an encrypted code, and the composing comprises determining a destination web page based on successful decryption of the encrypted code ([0033], various techniques to encode and decode data with the redirection identifier.).
Re Claim 35, Trifa discloses wherein the encrypted code is generated at each interaction with a product connection point ([0046], [0050], [0063], user application uses bar code, code and/or QR codes and NFC tags encode a unique identifier of various types of information.).
Re Claim 36, Trifa discloses comprising tracking event data for the identifier of content, the event data comprising interactions of the server system with the identifier of content and related information for each of the interactions ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.).
Re Claim 37, Trifa discloses wherein the related information comprises one or more attributes, parameters or elements related to a connection point for the interaction, the computing device that generated the request, a digital destination of redirection of the computing device, or a combination thereof ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc. [0083]-[0084], map the current GPS coordinates of the mobile device into the actual string used to describe locations in the redirection table and return a unique target URL).
Re Claim 38, Trifa discloses presenting a user interface to receive definitions of multiple routing policies, including the set of two or more routing policies, used by the server system, wherein the user interface enables specification of how to compose a target resource identifier for each of the multiple routing policies using one or more variables that reference static content, dynamic content, another variable, or a combination thereof ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc. [0083]-[0084], map the current GPS coordinates of the mobile device into the actual string used to describe locations in the redirection table and return a unique target URL); and
processing a simulated inbound request in accordance with the multiple routing policies ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc. [0083]-[0084], map the current GPS coordinates of the mobile device into the actual string used to describe locations in the redirection table and return a unique target URL); and
displaying a generated resource identifier, which has been composed by the processing, in the user interface for confirmation of the definitions of the multiple routing policies ([0050]-[0051], location of web apps for example further incorporate when the user signs in the redirector application using a third party identity provider such as facebook, twitter, etc everytime the user will access the redirector server).
Re Claim 39, Trifa discloses wherein the finding comprises sending a product identifier, which is the identifier of content or is retrieved using the identifier of content, to a data store that uses product identifiers as keys to identify routing policies, and the method comprises eliminating one or more routing policies from the set of two or more routing policies based on an evaluation of context information associated with the request policies ([0080]-[0081], table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc. Uses the information and returns a target URI.).
Re Claim 40, Trifa discloses wherein the composing comprises: copying non-variable components specified by a template into the target uniform resource identifier ([0007], [0080]-[0081], location-dependent information is done with the same application template. table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.);
evaluating variable components specified by the template, including determining properties of a computing environment of the server system ([0007], [0080]-[0081], location-dependent information is done with the same application template. table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.); and
adding one or more results of the evaluating into the target uniform resource identifier at one or more positions specified by the template ([0007], [0080]-[0081], location-dependent information is done with the same application template. table 1, utilizes short URL and other content that is a variable such as the ID, user, location, time, etc.).
Re Claim 41, it is similar to claim 21 and therefore is rejected for the same reason above.
Claims 22 is rejected under 35 U.S.C. 103 as being unpatentable over Trifa and in view of Grant and in view of Payne (US 9,002,864).
Re Claim 22, Trifa and Grant does not disclose, however Payne discloses wherein identifier of content is associated with a product, and the request uses a non-standard format for encoding the identifier of content (col. 6, lines 35-40, the request is a non-standard URL prefix). Trifa, Grant and Payne are analogous art because they disclose URL representation.
It would have been obvious for one of ordinary skill in the art before the date the current invention was effectively filed to have modified the teachings of Trifa and Grant’s URL redirect format with Payne’s formatting to include non-standard URL. One of ordinary skill in the art would have been motivated to incorporate the teachings with one another in order to have a more versatile system by being able to utilize URLs of a non-standard format.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HO T SHIU whose telephone number is (571)270-3810. The examiner can normally be reached Mon-Fri (9:00am - 5:00pm).
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, Nicholas Taylor can be reached at 571-272-3089. 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.
/HO T SHIU/Examiner, Art Unit 2443
HO T. SHIU
Examiner
Art Unit 2443
/NICHOLAS R TAYLOR/Supervisory Patent Examiner, Art Unit 2443
Prosecution Insights