CTNF 18/963,173 CTNF 78950 DETAILED ACTION Notice of Pre-AIA or AIA Status The present application, 18/963,173, was filed on 11/27/2024 , and does not claim foreign priority or domestic benefit to any other application. The effective filing date is after the AIA date of March 16, 2013, and so the application is being examined under the “first inventor to file” provisions of the AIA. 07-06 AIA 15-10-15 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. Status of the Application This Non-Final Office Action is in response to Applicant’s communication of 11/27/2024. Claims 1-20 are pending, of which claims 1,13, and 17 are independent. In the most recent amendment, independent claims 13 and 17 have been amended to recite features of independent claim 1 . Also, dependent claim 16 has been amended for consistency. All pending claims have been examined on the merits. Information Disclosure Statement The Information Disclosure Statement (IDS) submitted on 07/09/20253 has been considered. Response to Arguments Re: Restriction Requirement Applicant’s amendments of independent claims 13 and 17 to recite features of independent claim 1 . The Examiner interprets that the amended independent claims are sufficiently similar to justify withdrawing the restriction requirement. Allowable Subject Matter 12-151-08 AIA 07-43 12-51-08 Claim s 10-12 and 18-20 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. The cited DiMaria and Mowatt references fail to teach the features of dependent claims 10-12 and 18-20. Claim Rejections - 35 USC § 103 07-20-aia AIA 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. 07-23-aia AIA The factual inquiries set forth in Graham v. John Deere Co. , 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. 07-21-aia AIA Claim s 1-9 and 13-17 are rejected under 35 U.S.C. 103 as being unpatentable over US 2023/0291837 A1 to DiMaria et al. (“DiMaria”. Eff. Filed on Nov. 15, 2022. Published on Sept. 14, 2023) in view of US 2013/0144755 A1 to Mowatt et al. (“Mowatt”. Filed on Dec. 1, 2011. Published on Jun. 6, 2013) . In regards to claim 1, 1. (Original) A system for scheduling a callback comprising: one or more non-transitory computer readable media storing instructions thereon that, when executed by one or more processors, cause the one or more processors to: (See DiMaria , para. [0136]: “Because such information and program instructions may be employed to implement one or more systems or methods described herein, at least some network device embodiments may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein. Examples of such nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks[.]”) … receive information relating to a service request associated with the callback to be scheduled; receive a selection of the URL from the user device; (See DiMaria , para. [0111]: “The mobile device may perform the third-party callback by opening an application on the user mobile device and sending a third-party callback request to a third-party server 1430. The callback action associated with a third-party callback trigger may comprise routing information indicating where to direct the user during the callback (e.g., a URL, an IP address of a third-party server, phone number, routing number, extension number, contact information of an individual, etc.) . In this way, a mobile device user's need to request third-party services conveniently and accurately is facilitated .”) (See DiMaria , para. [0113]: “In some implementations, a callback trigger may be associated with an electronic document. The electronic document may be associated with a third-party and configured by an individual associated therewith. Electronic document callback trigger events may instruct callback integration engine 1410 to perform a callback action during consumption of the electronic document by the mobile device user. For example, a mortgage broker may require the user to read and sign a document as part of the mortgage process and apply an event trigger to the document, wherein when the user signs the document a callback is automatically executed by callback integration engine 1410 which connects the user and the mortgage broker .”) determine, from a plurality of queues, a first queue from which to retrieve a plurality of timeslots to schedule the callback based on the information relating to the service request by: determining a characteristic of the service request using the information; and determining the first queue from among the plurality of queues by determining the first queue is associated with agents designated to respond to the service request based on the characteristic of the service request; (See DiMaria , para. [0084]: “According to embodiments, the text message sent to the mobile device 101 may contain different information depending on whether the contact center is providing an appropriate time for the mobile device user to place a subsequent inbound call to the contact center or an appropriate time when the contact center can place an outbound call to the mobile device user. For example, if the text message is providing the mobile device user with an appropriate time for a subsequent call to the contact center then the message may inform the calling party to call back the contact center immediately or within some short period of time while the wait time is low or may provide the mobile device user with a time window for when the user should call back the contact center. For instance, if the contact center is monitoring forecasted inbound call volume instead of current average wait time for calls placed in a queue waiting for available agents, then the contact center may determine that the forecasted inbound call volume between 1:30 p.m. and 2:15 p.m. is below a threshold amount . Thus, the contact center may send the mobile device user a text message informing the user to place a subsequent call to the contact center between the hours of 1:30 p.m. and 2:15 p.m .”) retrieve the plurality of timeslots from the determined queue, the plurality of timeslots associated with an agent of the plurality of agents associated with the determined queue; transmit, to the user device, the plurality of timeslots; receive, from the user device, a selection of a timeslot; and schedule the callback at the selected timeslot. (See DiMaria , para. [0068]: “Callback integration engine 201 may present an additional prompt to setup a callback 402, either through OS-based software integration with the callback integration engine operating at the OS layer 220, or as a base-level firmware feature that is natively recognized and exposed by the OS while the callback integration engine 201 operates at the firmware level 320. This added option 402 may be used to automatically request or schedule a callback , for example by providing a message to the caller requesting they call back at a predetermined time (for example, based on known availability from a user's on-device calendar), or by engaging with a callback cloud 110 to automatically arrange a callback that connects both participants .”) (See DiMaria , para. [0107]: “The triggering event for each of the one or more callback triggers may be further defined by one or more additional criteria. The additional criteria can include , but is not limited to, time or date criteria , user-based criteria, location based criteria , schedule based criteria , contextual and/or environmental criteria, and/or any combination thereof. In this way, the callback triggers can be customized to end users, locations, times , context, etc. For instance, a callback trigger may be defined as the occurrence of a defined user action at a defined trigger point during a defined time of day or on a data within a range of dates.”) However, under a conservative interpretation of DiMaria , it could be argued that DiMaria does not explicitly teach the features below, which are taught by Mowatt : generate a URL to schedule the callback, the URL unique to a user and the callback and allowing the user to schedule the callback independent of a registration of the user with the system, generating the URL comprising: generating a security token to permit the user to schedule the callback; and embedding the security token within the URL; provide the URL with the embedded security token to a user device; (See Mowatt , para. [0031]: “In addition, after the payment for the license has been processed, or the free trial license has been granted, a token for the license may be sent back to the purchaser device 116 through the storefront 120 within the client platform 104, as indicated by the arrow 132. In embodiments, the token may be referred to as an “entitlement token.” The marketplace service 102 may store the entitlement token in the entitlement storage database 128 or in a cloud-based store called an “entitlement store” (not shown), or both. The token may include a key ID that may be used to create a digital signature . The token may also include information relating to the date of the purchaser's last log-in to the marketplace service 102 and an expiration date for the token, such as, for example, thirty days after the token is issued. In some embodiments, the signature that is created using the key ID may be a hash-based message authentication code (HMAC) . In some embodiments, the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token .”) (See Mowatt , para. [0032]: “ After the token has been generated within the marketplace service 102, the purchaser device 116 may be redirected to the storefront 120 within the client platform 104 by a callback URL having the embedded token . The callback URL may be passed to the client platform 104 from an application download repository service 133 within the marketplace service 102. In some embodiments, the token may be embedded within the URL . Once the purchaser's browser receives the token, as well as a product code for the application, the token and the product code may be read from the URL by the storefront 120 and then persisted locally in a centralized license storage database 134.”) It would have been obvious to a person having ordinary skill in the art (PHOSITA), before the effective filing date of the claimed invention, to include in the “System and method for mobile device active callback integration utlizing callback triggers”, as taught by DiMaria above, with embedding a token within a URL, as further taught by Mowatt above, because Mowatt teaches that “the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token.” (See Mowatt , para. [0031]). In regards to claim 2, 2. (Original) The system of claim 1, wherein the instructions further cause the one or more processors to: present, to the user via the user device, based on the received plurality of timeslots and an availability of the user, a subset of the plurality of timeslots. (See DiMaria , para. [0084]: “According to embodiments, the text message sent to the mobile device 101 may contain different information depending on whether the contact center is providing an appropriate time for the mobile device user to place a subsequent inbound call to the contact center or an appropriate time when the contact center can place an outbound call to the mobile device user. For example, if the text message is providing the mobile device user with an appropriate time for a subsequent call to the contact center then the message may inform the calling party to call back the contact center immediately or within some short period of time while the wait time is low or may provide the mobile device user with a time window for when the user should call back the contact center. For instance, if the contact center is monitoring forecasted inbound call volume instead of current average wait time for calls placed in a queue waiting for available agents, then the contact center may determine that the forecasted inbound call volume between 1:30 p.m. and 2:15 p.m. is below a threshold amount . Thus, the contact center may send the mobile device user a text message informing the user to place a subsequent call to the contact center between the hours of 1:30 p.m. and 2:15 p.m .”) (See DiMaria , para. [0107]: “The triggering event for each of the one or more callback triggers may be further defined by one or more additional criteria. The additional criteria can include , but is not limited to, time or date criteria , user-based criteria, location based criteria , schedule based criteria , contextual and/or environmental criteria, and/or any combination thereof. In this way, the callback triggers can be customized to end users, locations, times , context, etc. For instance, a callback trigger may be defined as the occurrence of a defined user action at a defined trigger point during a defined time of day or on a data within a range of dates.”) In regards to claim 3, 3. (Original) The system of claim 1, wherein the information relating to the service request includes a location of at least one of the user or an event associated with the service request. (See DiMaria , para. [0107]: “The triggering event for each of the one or more callback triggers may be further defined by one or more additional criteria. The additional criteria can include , but is not limited to, time or date criteria, user-based criteria, location based criteria , schedule based criteria, contextual and/or environmental criteria, and/or any combination thereof. In this way, the callback triggers can be customized to end users, locations , times, context, etc. For instance, a callback trigger may be defined as the occurrence of a defined user action at a defined trigger point during a defined time of day or on a data within a range of dates.”) In regards to claim 4, 4. (Original) The system of claim 1, wherein generating the security token comprises: extracting one or more parameters from the URL, the one or more parameters associated with an identifier of the user associated with the URL, and wherein the security token is generated using the one or more extracted parameters. (See Mowatt , para. [0031]: “In addition, after the payment for the license has been processed, or the free trial license has been granted, a token for the license may be sent back to the purchaser device 116 through the storefront 120 within the client platform 104, as indicated by the arrow 132. In embodiments, the token may be referred to as an “entitlement token.” The marketplace service 102 may store the entitlement token in the entitlement storage database 128 or in a cloud-based store called an “entitlement store” (not shown), or both. The token may include a key ID that may be used to create a digital signature . The token may also include information relating to the date of the purchaser's last log-in to the marketplace service 102 and an expiration date for the token, such as, for example, thirty days after the token is issued. In some embodiments, the signature that is created using the key ID may be a hash-based message authentication code (HMAC) . In some embodiments, the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token .”) (See Mowatt , para. [0032]: “ After the token has been generated within the marketplace service 102, the purchaser device 116 may be redirected to the storefront 120 within the client platform 104 by a callback URL having the embedded token . The callback URL may be passed to the client platform 104 from an application download repository service 133 within the marketplace service 102. In some embodiments, the token may be embedded within the URL . Once the purchaser's browser receives the token, as well as a product code for the application, the token and the product code may be read from the URL by the storefront 120 and then persisted locally in a centralized license storage database 134.”) In regards to claim 5, 5. (Original) The system of claim 4, generating the URL further comprising: hashing the URL to hide the one or more parameters and the security token within the URL. (See Mowatt , para. [0031]: “In addition, after the payment for the license has been processed, or the free trial license has been granted, a token for the license may be sent back to the purchaser device 116 through the storefront 120 within the client platform 104, as indicated by the arrow 132. In embodiments, the token may be referred to as an “entitlement token.” The marketplace service 102 may store the entitlement token in the entitlement storage database 128 or in a cloud-based store called an “entitlement store” (not shown), or both. The token may include a key ID that may be used to create a digital signature . The token may also include information relating to the date of the purchaser's last log-in to the marketplace service 102 and an expiration date for the token, such as, for example, thirty days after the token is issued. In some embodiments, the signature that is created using the key ID may be a hash-based message authentication code (HMAC) . In some embodiments, the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token.”) In regards to claim 6, 6. (Original) The system of claim 5, wherein the instructions further cause the one or more processors to access, using public key cryptology, a data field, the data field comprising the identifier of the user associated with the URL. (See Mowatt , para. [0031]: “In addition, after the payment for the license has been processed, or the free trial license has been granted, a token for the license may be sent back to the purchaser device 116 through the storefront 120 within the client platform 104, as indicated by the arrow 132. In embodiments, the token may be referred to as an “entitlement token.” The marketplace service 102 may store the entitlement token in the entitlement storage database 128 or in a cloud-based store called an “entitlement store” (not shown), or both. The token may include a key ID that may be used to create a digital signature . The token may also include information relating to the date of the purchaser's last log-in to the marketplace service 102 and an expiration date for the token, such as, for example, thirty days after the token is issued. In some embodiments, the signature that is created using the key ID may be a hash-based message authentication code (HMAC) . In some embodiments, the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token .”) In regards to claim 7, 7. (Original) The system of claim 1, wherein the instructions further cause the one or more processors to transmit a phone number of the user to the agent to initiate the callback at the selected timeslot. (See DiMaria , para. [0012]: “In an effort to reduce customer exacerbation caused by having to maintain a connection while on-hold in queue, secondary queue systems have been developed. A typical secondary queue system obtains a telephone number at which the calling client can be reached when a service representative is available (i.e., a call back number) . The client disconnects, and then, at the proper time, a call back system establishes a connection to the client utilizing the call back number and couples the client to an available representative without waiting on-hold in queue . One exemplary system is disclosed in U.S. Pat. No. 6,563,921 to Williams et al. which is commonly assigned with the present application.”) In regards to claim 8, 8. (Original) The system of claim 1, wherein the instructions further cause the one or more processors to: validate an authentication of the user using the security token embedded in the URL. (See DiMaria , para. [0098]: “In some implementations, remote device 1420 may receive, retrieve, or otherwise obtain authentication data associated with a user or the user's mobile device. In some implementations, the authentication data may be stored on mobile device 1400, in third-party server 1430, in an authentication server, and/or in callback cloud 110 in a user profile.”) (See Mowatt , para. [0031]: “In addition, after the payment for the license has been processed, or the free trial license has been granted, a token for the license may be sent back to the purchaser device 116 through the storefront 120 within the client platform 104, as indicated by the arrow 132. In embodiments, the token may be referred to as an “entitlement token.” The marketplace service 102 may store the entitlement token in the entitlement storage database 128 or in a cloud-based store called an “entitlement store” (not shown), or both. The token may include a key ID that may be used to create a digital signature . The token may also include information relating to the date of the purchaser's last log-in to the marketplace service 102 and an expiration date for the token, such as, for example, thirty days after the token is issued. In some embodiments, the signature that is created using the key ID may be a hash-based message authentication code (HMAC) . In some embodiments, the token may also contain encrypted information that can be decrypted by a particular Web service, such as the third party service 106, or a separate key provided to the developer of the token .”) In regards to claim 9, 9. (Original) The system of claim 8, wherein validating an authentication of the user using the security token is performed prior to providing the user with options for timeslots, (See DiMaria , para. [0070]: “Callbacks may be scheduled according to a variety of criteria, including (but not limited to) user availability as determined from preconfigured settings or known context (for example, calendar or email information such as invitation responses or verbal commitments in messages that may not have been separately entered into a calendar), user activity based on device information such as network or sensor data (such as if the device is paired to a car audio system, indicating the user is driving, or if there is significant accelerometer data that might indicate the user is in the middle of an exercise activity). Callbacks may then be scheduled to occur when the user is available or no longer indisposed, and may also incorporate availability on the part of the caller by (for example) providing them with a selection of callback options to from which to select a specific callback time .”) and wherein retrieving the plurality of timeslots from the determined queue is performed responsive to authenticating the user. (See DiMaria , para. [0098]: “In some implementations, remote device 1420 may receive, retrieve, or otherwise obtain authentication data associated with a user or the user's mobile device. In some implementations, the authentication data may be stored on mobile device 1400, in third-party server 1430, in an authentication server, and/or in callback cloud 110 in a user profile.”) In regards to independent claim 13, it is rejected on the same grounds as independent claim 1. In regards to claim 14, it is rejected on the same grounds as independent claim 1. In regards to claim 15, 15. (Original) The method of claim 13, wherein the URL allows the user to schedule the callback independent of a registration status of the user. In regards to claim 16, it is rejected on the same grounds as claim 6. In regards to claim 17, it is rejected on the same grounds as independent claim 1. Conclusion Applicants are invited to contact the Office to schedule an in-person interview to discuss and resolve the issues set forth in this Office Action. Although an interview is not required, the Office believes that an interview can be of use to resolve any issues related to a patent application in an efficient and prompt manner. 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. Any inquiry concerning this communication or earlier communications should be directed to Examiner Ayal Sharon, whose telephone number is (571) 272-5614, and fax number is (571) 273-1794. The Examiner can normally be reached from Monday to Friday between 9 AM and 6 PM. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, SPE Christine Behncke can be reached at (571) 272-8103 or at christine.behncke@uspto.gov. The fax 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. Sincerely, /Ayal I. Sharon/ Examiner, Art Unit 3695 May 25, 2026 Application/Control Number: 18/963,173 Page 2 Art Unit: 3695 Application/Control Number: 18/963,173 Page 3 Art Unit: 3695 Application/Control Number: 18/963,173 Page 4 Art Unit: 3695 Application/Control Number: 18/963,173 Page 5 Art Unit: 3695 Application/Control Number: 18/963,173 Page 7 Art Unit: 3695
Prosecution Insights