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
1. This case is in response to the application field on May 5, 2025. Claims 21-42 are pending. Claims 21-42 represent METHODS AND SYSTEMS FOR SERVICE POLICY ORCHESTRATION IN A COMMUNICATION NETWORK.
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.
19/198,853
12,294,496
12,081,505
21. A method for updating an event repository in a communication network, the method comprising: at a service policy orchestration factory (SPOF), in response to receiving a service event object and a corresponding unique service instance ID from a service policy execution factory (SPEF): selecting one or more operator domains and/or updates; selecting a mapping table for operator specific events; creating one or more event broker rule objects; updating the event repository with the service event object; and sending the service event object to one or more operator access domains (OADs).
1. A method of updating an event repository in a communication network, the method comprising: at a service policy execution factory (SPEF): initiating an orchestration of a distributed event policy, wherein the initiating comprises: selecting a service event object with an associated unique service instance identifier (ID) and an associated unique service event identifier (ID), wherein the service event object is a distributed version of a prior service event object; defining one or more service requirements, wherein the one or more service requirements comprise or relate to at least one of a type of an event, a criticality, a lifetime and one or more generic service execution rules; updating the service event object to include the one or more service requirements; and sending the service event object and the unique service instance ID to a service policy orchestration factory (SPOF) for performing one or more actions relating to the orchestration of the distributed event policy; and in response to receiving an SPOF feedback message from the service policy orchestration factory (SPOF) that indicates a successful updating of the event repository: confirming receipt of the SPOF feedback message to the service policy orchestration factory (SPOF); and terminating the orchestration of the distributed event policy.
1. A method comprising: uniquely associating a durable long-code telephone number with a client of a messaging platform; receiving, via the messaging platform, a plurality of incoming messages directed to the client via the durable long-code telephone number; identifying a plurality of users of the messaging platform based on user data associated with the plurality of incoming messages; determining one or more attributes of the plurality of users; identifying, based on the one or more attributes, a first subset of the plurality of users and a second subset of the plurality of users; associating a first message with the first subset of the plurality of users; transmitting, via one or more messaging services associated with the messaging platform, the first message to each user of the first subset of the plurality of users; determining a performance metric of the first message among the first subset of the plurality of users; generating, based on the first message and the performance metric, a second message; and transmitting, via the one or more messaging services, the second message to each user of the second subset of the plurality of users, wherein: the second subset of the plurality of users comprises a first user and the first subset of the plurality of users does not comprise the first user.
12,003,375
11,671,326
13,36,526
1. A method of updating an event repository in a communication network, the method comprising: at a service policy execution factory (SPEF): initiating an orchestration of a distributed event policy, wherein the initiating comprises: selecting a service event object with an associated unique service instance identifier (ID) and an associated unique service event identifier (ID), wherein the service event object is a distributed version of a prior service event object; defining one or more service requirements, wherein the one or more service requirements comprise or relate to at least one of a type of an event, a criticality, a lifetime and one or more generic service execution rules; updating the service event object to include the one or more service requirements; and sending the service event object and the unique service instance ID to a service policy orchestration factory (SPOF) for performing one or more actions relating to the orchestration of the distributed event policy; and in response to receiving an SPOF feedback message from the service policy orchestration factory (SPOF) that indicates a successful updating of the event repository: confirming receipt of the SPOF feedback message to the service policy orchestration factory (SPOF); and terminating the orchestration of the distributed event policy.
1. A method of orchestrating a service policy in a communication network, the method comprising: receiving first service event related data, wherein the first service event related data comprises data that defines an update of a current service execution policy; selecting an operator access domain linked to the first service event related data for executing a service linked to the service policy; sending to the operator access domain the first service event related data and an operator specific service identifier linked to a respective operator access domain; receiving first feedback data set from the operator access domain; and processing the first feedback data set.
1. A method of orchestrating a service policy in a communication network, the method comprising: receiving a service instance object and a first service event object, wherein: the service instance object defines service execution requirements, and the first service event object defines an update of a current service execution policy; updating a service repository associated with the communication network, with the first service event object and the service instance object; selecting, based on a first mapping table, at least one operator access domain linked to the first service event object for executing a service linked to the service policy; sending the first service event object and an operator specific service identifier linked to a respective operator access domain to the selected at least one operator access domain to allow the at least one operator access domain to update its service repository; receiving a first feedback data set from the at least one operator access domain, the first feedback data set comprising an operator domain identifier per operator access domain indicating a successful orchestration; and updating a second mapping table with the received operator domain identifier.
2. Claims 21-42 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20, 1-20, 1-20, 1-26 and 1-14 of U.S. Patent No.(s) 12,294,496, 12,081,505, 12,003,375, 11,671,326 and 11,336,526, respectively, to Jost. Although the claims at issue are not identical, they are not patentably distinct from each other because a comparison between the set of claims shows that the instant claims 1-20 are anticipated by claims 1-20, 1-20, 1-20, 1-26 and 1-14 of patent(s) ‘496, ‘505, ‘375, ‘326 and ‘526, respectively.
Conclusion
3. Any inquiry concerning this communication or earlier communications from the examiner should be directed to EL HADJI SALL whose telephone number is (571)272-4010. The examiner can normally be reached Monday-Friday 8:00-8:30 (flexible).
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, Ario Etienne can be reached on 5712724001. 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.
/EL HADJI M SALL/Primary Examiner, Art Unit 2457
Prosecution Insights