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
Response to Arguments
Applicant's arguments filed 2/23/2026 have been fully considered, and are persuasive. The previously relied upon prior art combination fails to show the location data communication and responsiveness features now recited in claims 1, 3, 5, and 7. However, after further search and consideration, an update grounds of rejection further in view of Campbell (Campbell, C. "Using Cellular Intelligence Capabilities to Maximize Performance in 5G and LTE Wireless WAN Deployments Network Management". https://cradlepoint.com/resources/blog/how-to-use-insights-to-maximize-cellular-performance-in-lte-and-5g-wireless-wan-deployments/. pgs. 1-4. May. (Year: 2022)) and Dannebro (US-20210099943-A1) is presently presented.
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 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, 2, 5, and 6 are rejected under 35 U.S.C. 103 as being unpatentable over Kao (Kao, Ling-Chih, and Wanjiun Liao. "Multi-access intelligent A+: Ensuring service continuity and consistency in private 5G heterogeneous networks." IEEE Communications Standards Magazine 6.2: 85-90. (Year: 2022)) in view of Mathison (US-20230093193-A1), Campbell (Campbell, C. "Using Cellular Intelligence Capabilities to Maximize Performance in 5G and LTE Wireless WAN Deployments Network Management". https://cradlepoint.com/resources/blog/how-to-use-insights-to-maximize-cellular-performance-in-lte-and-5g-wireless-wan-deployments/. pgs. 1-4. May. (Year: 2022)) and Dannebro (US-20210099943-A1).
Regarding claim 1, Kao shows a system for Multi-access Edge Computing (MEC) in a 5G network, the system comprising: a network device (e.g., a MIA+ installation “inline” between, e.g., an enterprise network and a 5G core network, as discussed on pg. 86, right column and illustrated in Fig. 2) configured to communicate over at least a 5G network (Fig. 2 showing the MIA+ communicating with the 5G core network) wherein the network device comprises a set of instructions to implement an enterprise policy for MEC over 5G network infrastructure (pg. 85, Abstract and pg. 85, right column, discussing how MIA+ is an improved implementation of MEC, Fig. 2, illustrating MIA+ connectivity to an “Enterprise Data Center” and pg. 86, right column, discussing installation at an enterprise facility to provide the users with “consistent service” across the enterprise network (e.g., over WiFi) and across 4G/5G networks (further discussion provided on pg. 87, right column and pg. 88, left column); a data center system (Fig. 2, “Enterprise Data Center”) in communication with at least the 5G network (Fig. 2, via the MIA+ implementation) wherein the data center includes a set of instructions to cause the data center to respond to the network device implementing the enterprise policy for MEC by mapping the enterprise policy for MEC to the 5G network infrastructure (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi a 5G network); and a service account system that includes a set of instructions to provide a service account control plane configured to enable a user to configure the enterprise policy for MEC (pg. 86, right column, bottom, - pg. 87, left column, top - discussing a GUI (implicitly implemented/provided via a computer system) enabling a user (such as an “enterprise administrator”) to configure and adjust allocations such as bandwidth and otherwise implement particular “intelligent network access management”; these service management control steps (and those discussed on pg. 88, right column) are considered within the broadest reasonable interpretation of “control plane” related functionality, and given these steps result in “service consistency” (e.g., pg. 88, left column) they are considered within the scope of the claimed “service” system). Kao does not show where the above functionality (i.e., the respective devices and systems) is implemented with respective processors. Mathison shows implementation of a variety of systems with processors, including the processors executing sets of instructions ([58,60,75,71,101]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of Kao with the hardware and software implementation of Mathison in order to fully implement the design and functionality suggested by Kao using existing and readily available system hardware and designs (such as CPUs executing software). The above combination does not show: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location for an endpoint device accessing the 5G network, and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing the 5G network and steer the endpoint device traffic. Campbell shows: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location (pg. 2 lines 8-33) for an endpoint device (pg. 2 lines 12-14 discussing a “consolidated view of SIMs”, pg. 2 lines 19-21 discussing “visibility and control over SIMs”, pg. 2 lines 28-30 discussing to view in “proximity to their Cradlepoint cellular modem”, and pg. 3 lines 5-10 discussing “clients and applications”) accessing the 5G network (pg. 3 lines 24-27), and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing (pg. 2 lines 27-34) the 5G network (pg. 3 lines 24-27) and steer the endpoint device traffic (pg. 3 lines 8-12, see “applying policies” and “steer traffic”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of the above combination with the location awareness of Campbell in order to ensure an accurate location is determined, enabling simplified deployments and more efficient troubleshooting (pg. 3 lines 13-22, pg. 2 lines 64-70). The above combination does not show steering the traffic to geographically nearby resources. Dannebro suggests steering the traffic to geographically nearby resources (Abstract, [7,15]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the proximity based steering of Dannebro in order to improve service delivery efficiency and reduce operational latency (Dannebro, [7]).
Regarding claim 2, the above combination further shows wherein the mapping of the enterprise policy for MEC to 5G network infrastructure network (Kao, Fig. 2 showing the MIA+ implementing policy to achieve the service consistency discussed on pg. 86, right column, bottom and pg. 88, left column) comprises informing the Non-3GPP Interworking Function (N3IWF) of the enterprise policy for MEC (Kao, pg. 88, left column, discussing where the MIA+ implementation (which is a type of improved MEC node, as discussed on pg. 85 and also in the noted area of pg. 88 of Kao) utilizes connectivity to the N3IWF to provide “service consistency” across the “enterprise area” serviced via WiFi as well as across the 4G and 5G networks via the policy sharing facilitated by the N3IWF as discussed on pg. 88, left column, top (Kao, discussing maintaining port and IP address information as necessary pg. 86, left column bottom, discussing “consistent service” in terms of bandwidth and location). Regarding claim 5, Kao shows method for Multi-access Edge Computing (MEC) in a 5G network, the method comprising: configuring a network device (e.g., a MIA+ installation “inline” between, e.g., an enterprise network and a 5G core network, as discussed on pg. 86, right column and illustrated in Fig. 2) to communicate over at least a 5G network (Fig. 2 showing the MIA+ communicating with the 5G core network) wherein the network device comprises a set of instructions to cause the device to implement an enterprise policy for MEC over 5G network infrastructure (pg. 85, Abstract and pg. 85, right column, discussing how MIA+ is an improved implementation of MEC, Fig. 2, illustrating MIA+ connectivity to an “Enterprise Data Center” and pg. 86, right column, discussing installation at an enterprise facility to provide the users with “consistent service” across the enterprise network (e.g., over WiFi) and across 4G/5G networks (further discussion provided on pg. 87, right column and pg. 88, left column); communicating from a data center (Fig. 2, “Enterprise Data Center”) in communication with at least the 5G network (Fig. 2, via the MIA+ implementation) wherein the data center includes a set of instructions to cause the data center to respond to the network device implementing the enterprise policy for MEC by mapping the enterprise policy for MEC to the 5G network infrastructure (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi a 5G network); and
configuring a service account systems that includes a set of instructions to provide a service account control plane to enable a user to configure the enterprise policy for MEC (pg. 86, right column, bottom, - pg. 87, left column, top - discussing a GUI (implicitly implemented/provided via a computer system) enabling a user (such as an “enterprise administrator”) to configure and adjust allocations such as bandwidth and otherwise implement particular “intelligent network access management”; these service management control steps (and those discussed on pg. 88, right column) are considered within the broadest reasonable interpretation of “control plane” related functionality, and given these steps result in “service consistency” (e.g., pg. 88, left column) they are considered within the scope of the claimed “service” system).
Kao does not show where the above functionality (i.e., the respective devices and systems) is implemented with respective processors. Mathison shows implementation of a variety of systems with processors, including the processors executing sets of instructions ([58,60,75,71,101]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of Kao with the hardware and software implementation of Mathison in order to fully implement the design and functionality suggested by Kao using existing and readily available system hardware and designs (such as CPUs executing software). The above combination does not show: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location for an endpoint device accessing the 5G network, and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing the 5G network and steer the endpoint device traffic. Campbell shows: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location (pg. 2 lines 8-33) for an endpoint device (pg. 2 lines 12-14 discussing a “consolidated view of SIMs”, pg. 2 lines 19-21 discussing “visibility and control over SIMs”, pg. 2 lines 28-30 discussing to view in “proximity to their Cradlepoint cellular modem”, and pg. 3 lines 5-10 discussing “clients and applications”) accessing the 5G network (pg. 3 lines 24-27), and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing (pg. 2 lines 27-34) the 5G network (pg. 3 lines 24-27) and steer the endpoint device traffic (pg. 3 lines 8-12, see “applying policies” and “steer traffic”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of the above combination with the location awareness of Campbell in order to ensure an accurate location is determined, enabling simplified deployments and more efficient troubleshooting (pg. 3 lines 13-22, pg. 2 lines 64-70). The above combination does not show steering the traffic to geographically nearby resources. Dannebro suggests steering the traffic to geographically nearby resources (Abstract, [7,15]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the proximity based steering of Dannebro in order to improve service delivery efficiency and reduce operational latency (Dannebro, [7]).
Regarding claim 6, the above combination further shows wherein the mapping of the enterprise policy for MEC to 5G network infrastructure network (Kao, Fig. 2 showing the MIA+ implementing policy to achieve the service consistency discussed on pg. 86, right column, bottom and pg. 88, left column) comprises informing the Non-3GPP Interworking Function (N3IWF) of the enterprise policy for MEC (Kao, pg. 88, left column, discussing where the MIA+ implementation (which is a type of improved MEC node, as discussed on pg. 85 and also in the noted area of pg. 88 of Kao) utilizes connectivity to the N3IWF to provide “service consistency” across the “enterprise area” serviced via WiFi as well as across the 4G and 5G networks via the policy sharing facilitated by the N3IWF as discussed on pg. 88, left column, top (Kao, discussing maintaining port and IP address information as necessary pg. 86, left column bottom, discussing “consistent service” in terms of bandwidth and location).
Claims 3, 4, 7, and 8 are rejected under 35 U.S.C. 103 as being unpatentable over Kao in view of Mathison, further in view of Lubenski (US-20170070436-A1), Campbell, and Dannebro.
Regarding claim 3, Kao shows a system for Multi-access Edge Computing (MEC) in a 5G network, the system comprising: a service account gateway (e.g., a MIA+ installation “inline” between, e.g., an enterprise network and a 5G core network, as discussed on pg. 86, right column and illustrated in Fig. 2; the network-to-network connectivity between the enterprise and 3GPP networks via the MIA+ place it within the broadest reasonable interpretation of a “gateway”), configured to include a set of instructions to provide a service account control plane (pg. 86, right column, bottom, - pg. 87, left column, top - discussing a GUI (implicitly implemented/provided via a computer system) configured to enable a user (such as an “enterprise administrator”; see pg. 86, left column, bottom, last line) to configure at least one MEC policy (e.g., adjust allocations such as bandwidth and otherwise implement particular “intelligent network access management”; these service management control steps (and those discussed on pg. 88, right column) are considered within the broadest reasonable interpretation of “control plane” related functionality, and given these steps result in “service consistency” (e.g., pg. 88, left column) they are considered within the scope of the claimed “service” system), and a set of instructions to provide the at least one enterprise MEC policy to a network device (pg. 86, right column, bottom, discussing providing a GUI to configure and implement desired policies via the MIA+ implementation, where the polices are provisioned to user devices that may, as discussed on pg. 88, left column, move between enterprise WiFi and 3GPP cellular coverage); the network device configured to communicate over at least a 5G network wherein the network device comprises a set of instructions to cause the device to map the at least one enterprise MEC policy to a 5G network infrastructure (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi a 5G network); and a data center (Fig. 2, “Enterprise Data Center”) in communication with at least the 5G network (Fig. 2, via the MIA+ implementation) wherein the data center includes a set of instructions to cause the data center to maintain the at least one enterprise MEC policy (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi and a 5G network).
Kao does not show where the above functionality (i.e., the respective devices and systems) is implemented with respective processors. Mathison shows implementation of a variety of systems with processors, including the processors executing sets of instructions ([58,60,75,71,101]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of Kao with the hardware and software implementation of Mathison in order to fully implement the design and functionality suggested by Kao using existing and readily available system hardware and designs (such as CPUs executing software).
The above combination does not show policy provisioning and implementation utilizing push delivery. Lubenski shows policy provisioning and implementation utilizing push delivery ([27] discussing an MEC gateway pushing down policies to ensure their implementation). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the push-based data delivery of Lubenski in order to provide more control to the MEC gateway to update and otherwise control the policies utilized in the system in order to better ensure the enterprise administrator is more fully in control over the services and experience provided to their system users.
The above combination does not show: to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing the 5G network and steer the endpoint device traffic, and
to collect and communicate data indicating a cell tower location and global positioning system (GPS) location for an endpoint device accessing the 5G network, and Campbell shows: to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing (pg. 2 lines 27-34) the 5G network (pg. 3 lines 24-27) and steer the endpoint device traffic (pg. 3 lines 8-12, see “applying policies” and “steer traffic”) and to collect and communicate data indicating a cell tower location and global positioning system (GPS) location (pg. 2 lines 8-33) for an endpoint device (pg. 2 lines 12-14 discussing a “consolidated view of SIMs”, pg. 2 lines 19-21 discussing “visibility and control over SIMs”, pg. 2 lines 28-30 discussing to view in “proximity to their Cradlepoint cellular modem”, and pg. 3 lines 5-10 discussing “clients and applications”) accessing the 5G network (pg. 3 lines 24-27). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of the above combination with the location awareness of Campbell in order to ensure an accurate location is determined, enabling simplified deployments and more efficient troubleshooting (pg. 3 lines 13-22, pg. 2 lines 64-70). The above combination does not show steering the traffic to geographically nearby resources. Dannebro suggests steering the traffic to geographically nearby resources (Abstract, [7,15]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the proximity based steering of Dannebro in order to improve service delivery efficiency and reduce operational latency (Dannebro, [7]).
Regarding claim 4, the above combination further shows wherein the mapping of the enterprise MEC policy to 5G network infrastructure network (Kao, Fig. 2 showing the MIA+ implementing policy to achieve the service consistency discussed on pg. 86, right column, bottom and pg. 88, left column) comprises informing the Non-3GPP Interworking Function (N3IWF) of the enterprise MEC policy (Kao, pg. 88, left column, discussing where the MIA+ implementation (which is a type of improved MEC node, as discussed on pg. 85 and also in the noted area of pg. 88 of Kao) utilizes connectivity to the N3IWF to provide “service consistency” across the “enterprise area” serviced via WiFi as well as across the 4G and 5G networks via the policy sharing facilitated by the N3IWF as discussed on pg. 88, left column, top (Kao, discussing maintaining port and IP address information as necessary pg. 86, left column bottom, discussing “consistent service” in terms of bandwidth and location). Regarding claim 7, Kao shows a method for Multi-access Edge Computing (MEC) in a 5G network, the method comprising: configuring a service account gateway (e.g., a MIA+ installation “inline” between, e.g., an enterprise network and a 5G core network, as discussed on pg. 86, right column and illustrated in Fig. 2; the network-to-network connectivity between the enterprise and 3GPP networks via the MIA+ place it within the broadest reasonable interpretation of a “gateway”), to include a set of instructions to provide a service account control plane configured (pg. 86, right column, bottom, - pg. 87, left column, top - discussing a GUI (implicitly implemented/provided via a computer system) to enable a user (such as an “enterprise administrator”; see pg. 86, left column, bottom, last line) to configure at least one MEC policy (e.g., adjust allocations such as bandwidth and otherwise implement particular “intelligent network access management”; these service management control steps (and those discussed on pg. 88, right column) are considered within the broadest reasonable interpretation of “control plane” related functionality, and given these steps result in “service consistency” (e.g., pg. 88, left column) they are considered within the scope of the claimed “service” system), and a set of instructions to provide the at least one enterprise MEC policy to a network device (pg. 86, right column, bottom, discussing providing a GUI to configure and implement desired policies via the MIA+ implementation, where the polices are provisioned to user devices that may, as discussed on pg. 88, left column, move between enterprise WiFi and 3GPP cellular coverage); configuring the network device to communicate over at least a 5G network wherein the network device comprises a set of instructions to cause the device to map the at least one enterprise MEC policy to a 5G network infrastructure (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi a 5G network); and communicating from a data center (Fig. 2, “Enterprise Data Center”), with at least the 5G network (Fig. 2, via the MIA+ implementation) wherein the data center includes a set of instructions to cause the data center processor to maintain the at least one enterprise MEC policy (pg. 87, right column – pg. 88, left column discussing an enterprise policy that is applied consistently as a device moves across networks, such as between enterprise WiFi and a 5G network).
Kao does not show where the above functionality (i.e., the respective devices and systems) is implemented with respective processors. Mathison shows implementation of a variety of systems with processors, including the processors executing sets of instructions ([58,60,75,71,101]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of Kao with the hardware and software implementation of Mathison in order to fully implement the design and functionality suggested by Kao using existing and readily available system hardware and designs (such as CPUs executing software).
The above combination does not show policy provisioning and implementation utilizing push delivery. Lubenski shows policy provisioning and implementation utilizing push delivery ([27] discussing an MEC gateway pushing down policies to ensure their implementation). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the push-based data delivery of Lubenski in order to provide more control to the MEC gateway to update and otherwise control the policies utilized in the system in order to better ensure the enterprise administrator is more fully in control over the services and experience provided to their system users.
The above combination does not show: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location for an endpoint device accessing the 5G network, and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing the 5G network and steer the endpoint device traffic. Campbell shows: to collect and communicate data indicating a cell tower location and global positioning system (GPS) location (pg. 2 lines 8-33) for an endpoint device (pg. 2 lines 12-14 discussing a “consolidated view of SIMs”, pg. 2 lines 19-21 discussing “visibility and control over SIMs”, pg. 2 lines 28-30 discussing to view in “proximity to their Cradlepoint cellular modem”, and pg. 3 lines 5-10 discussing “clients and applications”) accessing the 5G network (pg. 3 lines 24-27), and to receive the communicated data indicating a cell tower location and GPS location for the endpoint device accessing (pg. 2 lines 27-34) the 5G network (pg. 3 lines 24-27) and steer the endpoint device traffic (pg. 3 lines 8-12, see “applying policies” and “steer traffic”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the infrastructure design and functionality of the above combination with the location awareness of Campbell in order to ensure an accurate location is determined, enabling simplified deployments and more efficient troubleshooting (pg. 3 lines 13-22, pg. 2 lines 64-70). The above combination does not show steering the traffic to geographically nearby resources. Dannebro suggests steering the traffic to geographically nearby resources (Abstract, [7,15]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to modify the above combination with the proximity based steering of Dannebro in order to improve service delivery efficiency and reduce operational latency (Dannebro, [7]).
Regarding claim 8, the above combination further shows wherein the mapping of the enterprise MEC policy to 5G network infrastructure network (Kao, Fig. 2 showing the MIA+ implementing policy to achieve the service consistency discussed on pg. 86, right column, bottom and pg. 88, left column) comprises informing the Non-3GPP Interworking Function (N3IWF) of the enterprise MEC policy (Kao, pg. 88, left column, discussing where the MIA+ implementation (which is a type of improved MEC node, as discussed on pg. 85 and also in the noted area of pg. 88 of Kao) utilizes connectivity to the N3IWF to provide “service consistency” across the “enterprise area” serviced via WiFi as well as across the 4G and 5G networks via the policy sharing facilitated by the N3IWF as discussed on pg. 88, left column, top (Kao, discussing maintaining port and IP address information as necessary pg. 86, left column bottom, discussing “consistent service” in terms of bandwidth and location).
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 JOHN M MACILWINEN whose telephone number is (571)272-9686. The examiner can normally be reached Monday - Friday, 9:00 - 5:00.
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, Glenton B Burgess can be reached at (571) 272 - 3949. 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 MACILWINEN
Primary Examiner
Art Unit 2442
/JOHN M MACILWINEN/Primary Examiner, Art Unit 2454