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 .
Response to Amendment
Applicant's submission filed on 3/18/2026 has been entered. Claims 1-4, 6-14 and 16-22 are pending.
Response to Arguments
Applicant’s arguments with respect to claims 1, 11 and 20 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Claim Objections
Claim 22 is objected to because of the following informalities: as per claim 22, it appears an typographical error in line 2 “…a service device separate form the…”. Appropriate correction is required.
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 1-4, 6-14 and 16-20 are rejected under 35 U.S.C. 103 as being unpatentable over Seok et al. (US 2023/0421628 hereinafter Seok) in view of Tibbetts et al. (US 2024/0354496 hereinafter Tibbetts) and further in view of Karim et al. (US 2023/0060364 hereinafter Karim).
Regarding claim 1, Seok discloses a method comprising:
receiving, from a messaging client, model data (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0038]-[0047]; i.e. receiving from client devices messaging requests or API messages);
receiving, from a database, a structured template, the database comprising one or more templates that each comprise a static data element, a dynamic data element, and a channel configuration data element (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0081]-[0082]; i.e. receiving from the datastore templates comprising static data type, dynamic data type and channel specific data type);
generating a channel-specific message by applying the model data to the structured template (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0068], [0081]-[0082]; i.e. translating the messaging requests or API messages from first format to a second format that is compatible to at least the destination communication channel); and
transmitting, to a service associated with the channel configuration data element, the channel-specific message (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0068], [0081]-[0082]; i.e. sending the reformatted message to the destination communication service).
Seok does not explicitly disclose wherein the one or more templates includes a custom template generated via operations comprising: receiving a modification request, wherein the modification request includes a modification to one or more of the static data element, the dynamic data element, or the channel configuration data element of a custom template; previewing an emulated display of the custom template; generating the custom template based in part on the modification request; and storing the custom template in a template database.
However, Tibbetts discloses wherein the one or more templates includes a custom template generated via operations comprising: receiving a modification request, wherein the modification request includes a modification to one or more of the static data element, the dynamic data element, or the channel configuration data element of a custom template; generating the custom template based in part on the modification request; and storing the custom template in a template database (¶ [0066]-[0069]).
Therefore, it would have been obvious to one of ordinary skill in the art before effective filing date of the claimed invention to combine Seok and Tibbetts in order to allow accurate and efficiently tracking, approving, generating and sharing multimedia components in an electronic network (Tibbetts, ¶ [0043]).
Karim discloses previewing an emulated display of the custom template (FIG. 2-5, ¶ [0023], [0050]-[0053]).
Therefore, it would have been obvious to one of ordinary skill in the art before effective filing date of the claimed invention to combine Seok, Tibbetts and Karim in order to enable users to minimize or avoid performing multiple test for target device using different platforms to save app development time (Karim, ¶ [0026]-[0027]).
Regarding claim 2, Seok in view of Tibbetts and Karim discloses the method of claim 1, further comprising, outputting the channel-specific message to a graphical user interface (Seok, FIG. 3B & 3D).
Regarding claim 3, Seok in view of Tibbetts and Karim discloses the method of claim 1 further comprising: receiving a modification request, wherein the modification request includes a modification to one or more of the static data element, the dynamic data element, or the channel configuration data element of the one or more templates (Seok, ¶ [0027]-[0031], [0081]-[0082]); generating a custom template based in part on the modification request; and deploying the custom template in the template database (Seok, ¶ [0027]-[0031], [0081]-[0082]).
Regarding claim 4, Seok in view of Tibbetts and Karim discloses the method of claim 3, further comprising, receiving an application associated with an application owner (Seok, FIG. 3A-E, ¶ [0085], [0119]); and providing, to the application owner, client user access permissions (Seok, ¶ [0085], [0119]).
Regarding claim 6, Seok in view of Tibbetts and Karim discloses the method of claim 1, wherein the channel configuration data element includes channel-identifier data, and receiving the structured template from the database is based in part on the channel-identifier data (Seok, FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0081]-[0082]).
Regarding claim 7, Seok in view of Tibbetts and Karim discloses the method of claim 1, wherein generating the channel-specific message comprises retrieving, from the model data, target variable data, and inserting the target variable data into the dynamic data element (Seok, FIG. 3A-E, ¶ [0082],[0094]-[0095]).
Regarding claim 8, Seok in view of Tibbetts and Karim discloses the method of claim 7, wherein generating the channel-specific message further comprises: modifying the target variable data based in part on the channel configuration data element to generate modified target variable data (Seok, FIG. 3A-E, ¶ [0068],[0094]-[0095]); and inserting the modified target variable data into the dynamic data element (Seok, FIG. 3A-E, ¶ [0068],[0094]-[0095]).
Regarding claim 9, Seok in view of Tibbetts and Karim discloses the method of claim 1, wherein the structured template further includes a data formatting element (Seok, FIG. 1-2, 3A-E, ¶ [0031]-[0033], [0068]); and generating the channel-specific message includes modifying the model data based in part on the data formatting element (Seok, FIG. 1-2, 3A-E, ¶ [0031]-[0033], [0068]).
Regarding claim 10, Seok in view of Tibbetts and Karim discloses the method of claim 1, wherein the messaging client generates an API call, and the API call generates the model data (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033]).
Regarding claim 11, Seok discloses a system comprising:
one or more processors configured to (FIG. 6):
receive, from a messaging client, model data (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0038]-[0047]; i.e. receiving from client devices messaging requests or API messages);
receive, from a database a structured template, the database comprising one or more templates that each comprise a static data element, a dynamic data element, and a channel configuration data element (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0081]-[0082]; i.e. receiving from the datastore templates comprising static data type, dynamic data type and channel specific data type);
generate a channel-specific message by applying the model data to the structured template (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0068], [0081]-[0082]; i.e. translating the messaging requests or API messages from first format to a second format that is compatible to at least the destination communication channel); and
transmit, to a service associated with the channel configuration data element, the channel-specific message (FIG. 1-2, 3A-E, ¶ [0023], [0031]-[0033], [0068], [0081]-[0082]; i.e. sending the reformatted message to the destination communication service).
Seok does not explicitly disclose wherein the one or more templates includes a custom template generated via operations comprising: receiving a modification request, wherein the modification request includes a modification to one or more of the static data element, the dynamic data element, or the channel configuration data element of a custom template; previewing an emulated display of the custom template; generating the custom template based in part on the modification request; and storing the custom template in a template database.
However, Tibbetts discloses wherein the one or more templates includes a custom template generated via operations comprising: receiving a modification request, wherein the modification request includes a modification to one or more of the static data element, the dynamic data element, or the channel configuration data element of a custom template; generating the custom template based in part on the modification request; and storing the custom template in a template database (¶ [0066]-[0069]).
Therefore, it would have been obvious to one of ordinary skill in the art before effective filing date of the claimed invention to combine Seok and Tibbetts in order to allow accurate and efficiently tracking, approving, generating and sharing multimedia components in an electronic network (Tibbetts, ¶ [0043]).
Karim discloses previewing an emulated display of the custom template (FIG. 2-5, ¶ [0023], [0050]-[0053]).
Therefore, it would have been obvious to one of ordinary skill in the art before effective filing date of the claimed invention to combine Seok, Tibbetts and Karim in order to enable users to minimize or avoid performing multiple test for target device using different platforms to save app development time (Karim, ¶ [0026]-[0027]).
Regarding claim 12, see claim 2 above for the same reasons of rejections.
Regarding claim 13, see claim 3 above for the same reasons of rejections.
Regarding claim 14, see claim 4 above for the same reasons of rejections.
Regarding claim 16, see claim 6 above for the same reasons of rejections.
Regarding claim 17, see claim 7 above for the same reasons of rejections.
Regarding claim 18, see claim 8 above for the same reasons of rejections.
Regarding claim 19, see claim 9 above for the same reasons of rejections.
Regarding claim 20, see claim 1 above for the same reasons of rejections.
Regarding claim 21, Seok in view of Tibbetts and Karim discloses the non-transitory computer readable medium of claim 20, wherein previewing the emulated display comprises showing modifications to the custom template in real time (Seok, ¶ [0082],Tibetts, ¶ [0066]-[0069]; Karim, FIG. 2-5, ¶ [0023], [0050]-[0053]).
Regarding claim 22, Seok in view of Tibbetts and Karim discloses the non-transitory computer readable medium of claim 20, wherein the preview is transmitted to client user device, and the service is located on a service device separate from the client user device (Seok, ¶ [0082],Tibetts, ¶ [0066]-[0069]; Karim, FIG. 2-5, ¶ [0023], [0050]-[0053]).
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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 CHI D NGUY whose telephone number is (571)270-7311. The examiner can normally be reached Monday-Friday 9-5 ET.
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, Amir Mehrmanesh can be reached at (571)270-3351. 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.
/C.D.N/Examiner, Art Unit 2435
/AMIR MEHRMANESH/Supervisory Patent Examiner, Art Unit 2435
Prosecution Insights