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
This Office Action corresponds to application 18/130,277 which was filed on 4/3/2023.
Response to Amendment
In the reply filed 3/11/2026, Claims 1, 6, 8, 13, 15, and 19 have been amended. No new claims have been added or cancelled. Accordingly, claims 1-2, 4-6, 8-9, 11-13, 15-16, 18-19, and 21-23 stand pending.
The 35 USC 112 rejections have been withdrawn in light of the amendments.
Response to Arguments
Applicant's arguments filed 3/11/2026 have been fully considered but are moot in view of new grounds of rejection.
The applicant argues that the cited references do not teach “wherein each of the plurality of management data source services publishes event messages representing event data to a corresponding source pipeline of a plurality of source pipelines …”. The examiner respectfully disagrees. Gupta teaches, in figures 1 and paragraphs 38, 40-41, and 49, a plurality of pipelines between the cloud services and data distribution system, receiving a plurality of event data by the data distribution system from the data sources via the pipelines, and event data that comprises update messages for the cloud-delivered services, e.g., changes to device data in the databases, which may also comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information. Hyun also teaches, in figures 1 and 8 and paragraphs 60-61 and 141, registration events that identify data sources and data sinks to set up pipelines for and transmitting data from the data sources to data sinks, which means changes to the device data in the corresponding databases would be transmitted. Lastly, Kulkarni also teaches, in figures 1 and 2 and column 16 line 65 – column 17 line 25, the data management system is a multi-tenant system, e.g., a plurality of enterprises, and using tenant identifiers to identify data associated with different tenants that may be stored on different devices, which is interepted to mean tenant data is associated with device data since each tenant may use their own devices. Therefore, the examiner is not persuaded.
The applicant argues that Gupta does not teach an orchestrator service that subscribes to multiple source pipelines corresponding to different data source services. The examiner respectfully disagrees. Gupta teaches, in figures 1 and 3 and paragraphs 27, 34, 38, 40-41, 44, and 49, rule data that indicates one or more data objects and corresponding target services that correspond to an event. The rule data that specifies a particular target service, among a plurality of target services, for data objects is interpreted as being registered/subscribed to a particular network-service-specific replication pipeline for that target service. Hyun also teaches, in figures 1 and 8 and paragraphs 13, 60-61, 116, and 141, transmitting data from data sources to data sinks with a particular network-service-specific pipeline and when combined with Gupta would be for the transmission of data to the target services. Therefore, the examiner is not persuaded.
The applicant also argues that Gupta does teach identifying a subset of event messages using both a tenant identifier and an entity identifier registered for a particular replication pipeline. The examiner respectfully disagrees. Gupta teaches, in figures 1 and 3 and paragraphs 34, 38, 40-41, 44, and 49, replicating data objects associated with the entity identifier and tenant identifier, e.g., update messages for the cloud-delivered services which may comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information. Gupta teaches rule data that uses event data to indicate the data objects and the target service to send the replicated data, which means the replicated subset of event data is identified using at least one tenant identifier, e.g., target service, and at least one entity identifier, type of data objects. It is also noted that under broadest reasonable interpretation a subset of items may include all the items in the original set. Hyun also teaches, in figures 1 and 8 and paragraphs 13, 60-61, 116, and 141, transmitting data from data sources to data sinks which are associated with entity and tenant identifiers. Therefore, the examiner is not persuaded.
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.
Claim(s) 1-2, 4-6, 8-9, 11-13, 15-16, and 18-19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Gupta (US2024/0176764, previously presented in ‘892) in view of Hyun et al. (US2022/0232070, previously presented in ‘892), hereinafter Hyun, and Kulkarni et al. (US12,131,233, previously presented in ‘892), hereinafter Kulkarni.
Regarding Claim 1:
Gupta teaches:
A method, comprising: identifying, by an orchestrator service of a management computing environment, a plurality of management data source services, wherein a particular management data source service maintains a corresponding database storing device data for client devices enrolled with the management computing environment, wherein each of the client devices is associated with at least one of a plurality of enterprises that utilize the management computing environment to manage the client devices (Gupta, figures 1, 3, and 6, [0012-0015, 0044, 0049, 0059], note cloud-delivered services; note the data distribution system identifying a source and target cloud-delivered service for data objects from an event; note each data source service maintains a corresponding database storing device data; note user computing devices of the consumers of the services, which may be enterprises; note the data services may also have various customers, e.g., enterprises) and wherein each of the plurality of management data source services publishes event messages representing event data to a corresponding source pipeline of a plurality of source pipelines, the event data representing changes to the device data in the corresponding database (Gupta, figures 1 and 3, abstract, [0038, 0040-0041, 0049], note plurality of pipelines between the cloud services and data distribution system; note receiving a plurality of event data by the data distribution system, e.g., published event messages from the cloud services; note the event data comprises update messages for the cloud-delivered services, e.g., changes to device data in the databases, which may comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information);
receiving, by the orchestrator service from the plurality of source pipelines, the event data for a plurality of entity identifiers and a plurality of tenant identifiers (Gupta, figures 1 and 3, abstract, [0038, 0040-0041, 0049], note receiving a plurality of event data by the data distribution system; note the event data comprises update messages for the cloud-delivered services which may comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information), wherein the event data has a data structure that is compliant with a public schema agreed upon between the management computing environment and the plurality of network services (Gupta, figures 1 and 3, [0034, 0044, 0050, 0090], note applying one or more transformations rules to the data objects to send the event data to the target service, this is interpreted as a public schema agreed upon between the computing environment and network services since the computing environment is transforming the data before sending to the services; note receiving feedback data to update rule data and training data, which is also interpreted as a public schema agreed upon between the computing environment and the services; note the use and manipulation of various publicly available media standards, e.g., public schema data structures); and
replicating, by the orchestrator service, a subset of the event data associated with the entity identifier and the tenant identifier into the particular network-service-specific replication pipeline (Gupta, figures 1 and 3, [0027, 0034-0036, 0038, 0040-0041, 0044, 0049], note receiving a plurality of event data by the data distribution system; note the event data comprises update messages for the cloud-delivered services which may comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information; note the data distribution system replicating the data objects and send them to the target cloud-delivered services, e.g., network-service-specific replication pipeline; note the rule data uses event data to indicate the data objects and the target service to send the replicated data, which means the replicated subset of event data is identified using at least one tenant identifier, e.g., target service, and at least one entity identifier, type of data objects. The rule data that specifies a particular target service for data objects is interpreted as being registered for the particular replication pipeline),
wherein the orchestrator service subscribes to the plurality of source pipelines corresponding to the plurality of management data source services to receive the event messages generated by the plurality of management data source services (Gupta, figures 1 and 3, [0027, 0034-0036, 0038, 0040-0041, 0044, 0049], note receiving a plurality of event data by the data distribution system; note the integration adapter is subscribed to a plurality of cloud services, which is interpreted as a plurality of source pipelines corresponding to data source services to receive event messages; note the data distribution system replicating the data objects and send them to the target cloud-delivered services, e.g., network-service-specific replication pipeline; note the rule data that specifies a particular target service for data objects is interpreted as being registered/subscribed for the particular replication pipeline),
wherein the orchestrator service identifies, from the received event messages, a subset of event messages that include both the tenant identifier and the entity identifier registered for the particular network-service-specific replication pipeline (Gupta, figures 1 and 3, [0027, 0034-0036, 0038, 0040-0041, 0044, 0049], note receiving a plurality of event data by the data distribution system; note the rule data uses event data to indicate the data objects and the target service to send the replicated data, which means the replicated subset of event data is identified using at least one tenant identifier, e.g., target service, and at least one entity identifier, type of data objects; note that under broadest reasonable interpretation a subset of items may include all the items in the original set. The rule data that specifies a particular target service for data objects is interpreted as being registered for the particular replication pipeline),
wherein the orchestrator service replicates only the identified subset of the event messages from the plurality of source pipelines into the particular network-service-specific replication pipeline (Gupta, figures 1 and 3, [0027, 0034-0036, 0038, 0040-0041, 0044, 0049], note receiving a plurality of event data by the data distribution system; note the rule data uses event data to indicate the data objects and the target service to send the replicated data, which means the replicated subset of event data is identified using at least one tenant identifier, e.g., target service, and at least one entity identifier, type of data objects; note that under broadest reasonable interpretation a subset of items may include all the items in the original set. The rule data that specifies a particular target service for data objects is interpreted as being registered for the particular replication pipeline; note sending the replicated data to the target service via the network-service-specific pipeline), and
wherein the network service receives the subset of the event data through the particular network-service-specific replication pipeline, and the replicated subset of the event data is identified using the tenant identifier and the entity identifier registered for the particular network-service-specific replication pipeline (Gupta, figures 1 and 3, [0027, 0034-0036, 0038, 0040-0041, 0044, 0049], note receiving a plurality of event data by the data distribution system; note the event data comprises update messages for the cloud-delivered services which may comprise or be associated with entity and tenant identifiers such as source information, target information, and type of event information; note the data distribution system replicating the data objects and send them to the target cloud-delivered services; note the rule data is uses event data to indicate the data objects and the target service to send the replicated data, which means the replicated subset of event data is identified using at least one tenant identifier, e.g., target service, and at least one entity identifier, type of data objects. The rule data that specifies a particular target service for data objects is interpreted as being registered for the particular replication pipeline), wherein the network service provides one or more services for the client devices of the enterprise associated with the tenant identifier by using the event data in the particular network-service-specific replication pipeline (Gupta, figures 1 and 3, [0012-0013, 0015], note the cloud services provide services for the client devices of the enterprise. When combined with Kulkarni the client devices would be associated with a tenant identifier as shown below).
While Gupta teaches replicating data to various cloud services, Gupta doesn’t specifically teach receiving a registration request from a network service of a plurality of network services to receive the event data, wherein the registration request includes a tenant identifier that identifies an enterprise of the plurality of enterprises and an entity identifier that identifies a type of the event data registered as being of interest to the network service; generating, by the orchestrator service, a plurality of network-service-specific replication pipelines for a corresponding plurality of network services, wherein a particular replication pipeline is registered in association with at least one tenant identifier and at least one entity identifier. However, Hyun is in the same field of endeavor, data management, and Hyun teaches:
identifying, by an orchestrator service of a management computing environment, a plurality of management data source services, wherein a particular management data source service maintains a corresponding database and wherein each of the plurality of management data source services publishes event messages representing event data to a corresponding source pipeline of a plurality of source pipelines, the event data representing changes to the device data in the corresponding database (Hyun, figures 1, 4, and 8, [0013, 0060-0061, 0141], note detecting a new registration event of new data sinks, which is interpreted as identifying a plurality of data sources; note event data may comprise device data; note transmitting data from a data source to a data sink which means changes to the device data in the corresponding databases would be transmitted. When combined with the previously cited reference this would be for identifying the cloud services as taught by Gupta);
receiving a registration request from a network service of a plurality of network services to receive the event data, wherein the registration request includes a tenant identifier that identifies an enterprise of the plurality of enterprises and an entity identifier that identifies a type of the event data registered as being of interest to the network service (Hyun, figures 1, 4, and 8, [0013, 0060-0061, 0116, 0141], note registration events, which are interpreted as registration requests; note detecting and registering data sinks and generating pipelines for the data sinks in response to the registration; note registering a data sink includes information about the data sink such as credential information and owner information, e.g., tenant identifier that identifies an enterprise, and type of data sink and source, e.g., entity identifier. When combined with the previous references this would be for the pipelines used by the cloud services and data distribution system as taught by Gupta);
generating, by the orchestrator service, a plurality of network-service-specific replication pipelines for a corresponding plurality of network services, wherein a particular network-service-specific replication pipeline is generated in response to receiving the registration request from the network service and is registered in association with the tenant identifier and the entity identifier (Hyun, figures 1, 4, and 8, [0013, 0060-0061, 0116, 0141], note registration events; note registering a data sink includes information about the data sink such as credential information, e.g., at least one tenant identifier, and type of data sink, e.g., at least one entity identifier; note generating a pipeline for the data sink; note the type of data sink, e.g., entity identifier, registered is interpreted to mean it is of interest to a network service since it was registered. When combined with the previous references this would be for the pipelines used by the cloud services and event data as taught by Gupta);
receiving, by the orchestrator service from the plurality of source pipelines, the event data for a plurality of entity identifiers and a plurality of tenant identifiers (Hyun, figures 1, 4, and 8, [0013, 0060-0061, 0116, 0141], note transmitting data from a data source to a data sink which means event data for a plurality of entity and tenant identifiers would be transmitted).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
While Gupta as modified teaches replicating data to various cloud services, Gupta as modified doesn’t specifically teach a plurality of enterprises. However, Kulkarni is in the same field of endeavor, data management, and Kulkarni teaches:
storing device data for client devices enrolled with the management computing environment, wherein each of the client devices is associated with at least one of a plurality of enterprises that utilize the management computing environment to manage the client devices, the event data representing changes to the device data in the corresponding database (Kulkarni, figures 1 and 2, column 16 line 65 – column 17 line 25, note the data management system is a multi-tenant system, e.g., a plurality of enterprises; note using tenant identifiers to identify data associated with different tenants that may be stored on different devices, which is interepted to mean tenant data comprises device data since each tenant may use their own devices. When combined with the previously cited references this would be for the system as taught by Gupta and Hyun);
wherein the event data has a data structure that is compliant with a public schema agreed upon between the management computing environment and the plurality of network services (Kulkarni, column 45 line 41 – column 46 line 5, note using standardized formats such as publicly available open-source formats. When combined with Gupta this would be for the transformation rules used by Gupta).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Kulkarni because all references are directed towards data management and because Kulkarni would expand upon the teachings of the previously cited references in data distribution which would improve the efficiency and usability of the system by enabling communications between diverse systems or networks or applications for multiple tenants.
Regarding Claim 2:
Gupta as modified shows the method as disclosed above;
Gupta as modified further teaches:
wherein the corresponding plurality of network services are external to the management computing environment (Gupta, [0012], note the use of network services such as the internet) (Hyun, figure 1, [0013, 0061, 0116, 0141], note the pipeline control service is external to the data source and sink. When combined with the previous references this would be for the pipelines used by the cloud services and event data as taught by Gupta).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
Regarding Claim 4:
Gupta as modified shows the method as disclosed above;
Gupta as modified further teaches:
receiving, by the orchestrator service, a plurality of source registration requests for the plurality of management data source services, wherein the source pipelines are generated in response to the source registration requests (Hyun, [0013, 0061, 0116, 0141], note detecting and registering data sinks and generating pipelines for the data sinks in response to the registration. When combined with the previous references this would be for the pipelines used by the cloud services and data distribution system as taught by Gupta).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
Regarding Claim 5:
Gupta as modified shows the method as disclosed above;
Gupta as modified further teaches:
wherein the plurality of management data source services are internal to the management computing environment (Gupta, figure 1, note the cloud services are managed by the data distribution system which is interpreted to mean the management of data source services are internal to the management computing environment) (Hyun, figure 1, [0013, 0061, 0116, 0141], note the pipeline control service is external to the data source and sink. When combined with the previous references this would be for the pipelines used by the cloud services and event data as taught by Gupta).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
Regarding Claim 6:
Gupta as modified shows the method as disclosed above;
Gupta as modified further teaches:
wherein the particular network-service-specific replication pipeline uses a messaging platform to provide the subset of the event data to the particular network service (Hyun, figure 1, [0013, 0061, 0116, 0141], note message queue used by the pipelines. When combined with the previous references this would be for the pipelines used by the cloud services and event data as taught by Gupta).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
Claim 8 discloses substantially the same limitations as claim 1 respectively, except claim 8 is directed to a non-transitory computer-readable medium while claim 1 is directed to a method. Therefore claim 8 is rejected under the same rationale set forth for claim 1.
Claim 9 discloses substantially the same limitations as claim 2 respectively, except claim 9 is directed to a non-transitory computer-readable medium while claim 2 is directed to a method. Therefore claim 9 is rejected under the same rationale set forth for claim 2.
Claim 11 discloses substantially the same limitations as claim 4 respectively, except claim 11 is directed to a non-transitory computer-readable medium while claim 4 is directed to a method. Therefore claim 11 is rejected under the same rationale set forth for claim 4.
Claim 12 discloses substantially the same limitations as claim 5 respectively, except claim 12 is directed to a non-transitory computer-readable medium while claim 5 is directed to a method. Therefore claim 12 is rejected under the same rationale set forth for claim 5.
Claim 13 discloses substantially the same limitations as claim 6 respectively, except claim 13 is directed to a non-transitory computer-readable medium while claim 6 is directed to a method. Therefore claim 13 is rejected under the same rationale set forth for claim 6.
Claim 15 discloses substantially the same limitations as claim 1 respectively, except claim 15 is directed to a system comprising at least one computing device (Gupta, figure 8), while claim 1 is directed to a method. Therefore claim 15 is rejected under the same rationale set forth for claim 1.
Claim 16 discloses substantially the same limitations as claim 2 respectively, except claim 16 is directed to a system comprising at least one computing device (Gupta, figure 8), while claim 2 is directed to a method. Therefore claim 16 is rejected under the same rationale set forth for claim 2.
Claim 18 discloses substantially the same limitations as claim 5 respectively, except claim 18 is directed to a system comprising at least one computing device (Gupta, figure 8), while claim 5 is directed to a method. Therefore claim 18 is rejected under the same rationale set forth for claim 5.
Claim 19 discloses substantially the same limitations as claim 6 respectively, except claim 19 is directed to a system comprising at least one computing device (Gupta, figure 8), while claim 6 is directed to a method. Therefore claim 19 is rejected under the same rationale set forth for claim 6.
Claim Rejections - 35 USC § 103
Claim(s) 21-23 is/are rejected under 35 U.S.C. 103 as being unpatentable over Gupta in view of Hyun, Kulkarni, and Quan et al. (US20140136481), hereinafter Quan.
Regarding Claim 21:
Gupta as modified shows the method as disclosed above;
Gupta as modified further teaches:
wherein the event data in the plurality of source pipelines comprises a plurality of database update messages generated in response to device data received by a management service from the client devices enrolled for management with the management service, wherein each of the client devices includes a management agent installed thereon, wherein the management agent on each of the client devices periodically reports the device data to the management service (Gupta, abstract, figures 1 and 3, [0032-0034, 0038], note a plurality of pipelines; note the cloud services generate events which cause the integration adapter and determination engine to determine data objects response to the event and requests those data objects and send them to the target services, which is interpreted as event data in the plurality of source pipelines comprising database update messages in response to device data received by the integration adapter, e.g., management service) (Hyun, figures 1, 4, and 8, [0016, 0055, 0069, 0141], note message queues/data broker which comprises a plurality of update messages that are in response to device data received by a management service, e.g., registration events; note pipeline control server and scheduling module; note the scheduling information may include a time batch-based schedule allowing the pipelines to operation at time intervals, which is interpreted as a management agent periodically reporting device data since the device data is needed to operation the pipelines to transmit data form the sources to the sinks).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Hyun because all references are directed towards data management and because Hyun would expand upon the teachings of the previously cited references in data distribution which would improve the network cost and performance by efficiently managing the data brokers and data pipelines (Hyun, [0006, 0071]).
While Gupta as modified teaches transmitting data for event data via pipelines, Gupta as modified doesn’t specifically teach wherein each of the client devices includes a management agent installed thereon; However, Quan is in the same field of endeavor, data management, and Quan teaches:
wherein each of the client devices includes a management agent installed thereon, wherein the management agent on each of the client devices periodically reports the device data to the management service (Quan, figures 1-4, claim 1, [0033], note state synchronization module which may periodically report state data, e.g., device data. When combined with the previously cited references this would be to the management service as taught by Gupta and Hyun).
It would have been obvious to one of ordinary skill in the art before the effective date of filing to modify the cited references to incorporate the teachings of Quan because all references are directed towards data management and because Quan would expand upon the teachings of the previously cited references in data distribution which would improve the security and availability of the data by periodically analyzing the device state.
Claim 22 discloses substantially the same limitations as claim 21 respectively, except claim 22 is directed to a non-transitory computer-readable medium while claim 21 is directed to a method. Therefore claim 22 is rejected under the same rationale set forth for claim 21.
Claim 23 discloses substantially the same limitations as claim 21 respectively, except claim 23 is directed to a system comprising at least one computing device (Gupta, figure 8), while claim 21 is directed to a method. Therefore claim 23 is rejected under the same rationale set forth for claim 21.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Fan et al. (US2021/0303585) teaches determining pipelines to send data from sources to target services.
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 JOHN J MORRIS whose telephone number is (571)272-3314. The examiner can normally be reached M-F 6:00-2: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, James Trujillo can be reached at 571-272-3677. 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.
/JOHN J MORRIS/Examiner, Art Unit 2151 5/26/2026
/James Trujillo/Supervisory Patent Examiner, Art Unit 2151
Prosecution Insights