Office Action Predictor
Last updated: April 16, 2026
Application No. 18/027,979

NETWORK NODE, TERMINAL DEVICE, AND METHODS THEREIN FOR EDGE APPLICATIONS

Final Rejection §103§112
Filed
Mar 23, 2023
Examiner
JOO, JOSHUA
Art Unit
2445
Tech Center
2400 — Computer Networks
Assignee
Telefonaktiebolaget Lm Ericsson (PUBL)
OA Round
6 (Final)
78%
Grant Probability
Favorable
7-8
OA Rounds
3y 1m
To Grant
98%
With Interview

Examiner Intelligence

Grants 78% — above average
78%
Career Allow Rate
763 granted / 976 resolved
+20.2% vs TC avg
Strong +20% interview lift
Without
With
+20.2%
Interview Lift
resolved cases with interview
Typical timeline
3y 1m
Avg Prosecution
25 currently pending
Career history
1001
Total Applications
across all art units

Statute-Specific Performance

§101
10.5%
-29.5% vs TC avg
§103
39.2%
-0.8% vs TC avg
§102
13.5%
-26.5% vs TC avg
§112
28.5%
-11.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 976 resolved cases

Office Action

§103 §112
Detailed Action The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . This Office action is in response to Applicant’s amendment submitted on December 8, 2025. Claims 24-25, 29, 33-38 are pending in the application. Response to Arguments/Remarks Claim Rejections - 35 USC § 112 Claims 22-23, 31-32 were rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor, regards as the invention. Claims 22-23, 31-32 have been cancelled. Accordingly, the rejections have been withdrawn. Claim Rejections - 35 USC § 103 Claims 22-25, 27-28, 31-34 were rejected under 35 U.S.C. 103 as being unpatentable over Gupta et al. US Patent Publication No. 2022/0369218 in view of Kim et al. US Patent Publication No. 2023/0362784, Foreign Priority to June 2020. The amendments to claims 24, 33, and 34 have overcome the rejections. Therefore, the prior rejection has been withdrawn, and new grounds of rejection are made in this Office action. The new grounds of rejection are necessitated by Applicant's amendment, and accordingly, this Office action is made Final. Claim Rejections - 35 USC § 103 The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action. Claims 24-25, 29, 33-38 are rejected under 35 U.S.C. 103 as being unpatentable over Yao et al US Patent Publication No. 2023/0008647, Foreign Priority to March 2020, (“Yao”) in view of Gupta et al. US Patent Publication No. 2022/0369218 (“Gupta”) and Kim et al. US Patent Publication No. 2023/0362784, Foreign Priority to June 2020 (“Kim”). Regarding claim 24, Yao teaches a method in a network node implementing an Edge Configuration Server, ECS, comprising: receiving, from a core network node, a notification of a user plane path management event associated with application traffic, wherein the notification comprises a target DNAI for the application traffic (para. [0083] core network element 101 is a network element that implements a session management function (session management function, SMF). para. [0097] user plane management event notification carries a changed DNAI. para. [0272] SMF detects that the user plane management event occurs and notifies the central AF of the event. para. [0262] central AF is an ECS); determining which EES and EAS with a DNAI matching the target DNAI (para. [0229] EES… responsible for managing, performing registration… each EAS deployed in the EDN. para. [0230] edge configuration server (edge configuration server, ECS) is a global management network element that maintains information of each EDN such as a service range and an EES address. para. [0273] central AF selects connection information of one or more edge networks (EHEs or EDNs), or selects connection information of network elements (EESs or EASs). para. [0274] in response to a notification message including one or more DNAI identifiers, the ECS determines that an edge network corresponding to the DNAI identifier. ECS determines the first network element); and transmitting, to an Edge Enabler Client a service provisioning notification containing information on the EES and the EAS with the DNAI matching the target DNAI (para. [0095] after receiving a DNAI identifier, the control network element determines that an edge network corresponding to the DNAI identifier. para. [0231] functions of the EEC include: retrieving EDN information by using EDGE-4, enabling the UE to register with the EES. para. [0273] ECS sends connection information of configured EDNs to the UE. connection information of the edge network (EHE or EDN) includes but is not limited to: EES address information, and EAS (list) information and EAS address information in the EDN.). Yao does not teach receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES. Gupta teaches receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES (para. [0037] receiving, by an edge configuration server (ECS), information of at least one edge application server (EAS) provided by a source edge enabler server (EES). para. [0051] EAS information profile comprises a list of service areas served by the EAS. para. [0071] service area of the EAS (112) or the service area of the EES (114) can be defined as… list of data network access identifiers (DNAIs) associated with the EDN which is hosting the EAS. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile.). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Gupta’s disclosure of receiving, from the EES, an EES registration request or an EES registration update. One of ordinary skill in the art would have been motivated to do so because Yao discloses that the ECS maintains information of EDNs and provides the information in response to requests. It would have been beneficial for the ECS to be updated and store information regarding the EES and EAS for management and servicing of requests. Yao discloses determining an EES and an EAS with a DNAI matching the target DNAI. Yao suggests determining an EES with a registered EAS based on DNAI matching a target DNAI as Yao discloses that the ECS determines a EES matching the DNAI and the EAS is registered with the EES (see para. [0229]). However, it is not expressly disclosed by Yao. Kim discloses determining which EES has a registered EAS with a DNAI matching one of the one or more DNAIs (para. [0134] in order to interact with the ECS 30, the target DNAI provided from the 3GPP network 40 may be transmitted to the ECS 30. ECS 30 may select the target EES based on the target DNAI). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Kim’s disclosure. One of ordinary skill in the art would have been motivated to do so because the ECS is a central control element that selects edge networks and edge elements, and it would have been beneficial to determine the EES for enabling discovery and access to the correct EAS by the UE. Regarding claim 33, Yao teaches a network node, comprising a communication interface, a processor and a memory, the memory comprising instructions executable by the processor whereby the network node is operative to, when implementing an Edge Configuration Server, ECS: receive, from a core network node, a notification of a user plane path management event associated with application traffic, wherein the notification comprises a target DNAI for the application traffic (para. [0083] core network element 101 is a network element that implements a session management function (session management function, SMF). para. [0097] user plane management event notification carries a changed DNAI. para. [0272] SMF detects that the user plane management event occurs and notifies the central AF of the event. para. [0262] central AF is an ECS); determining which EES and EAS with a DNAI matching the target DNAI (para. [0229] EES… responsible for managing, performing registration… each EAS deployed in the EDN. para. [0230] edge configuration server (edge configuration server, ECS) is a global management network element that maintains information of each EDN such as a service range and an EES address. para. [0273] central AF selects connection information of one or more edge networks (EHEs or EDNs), or selects connection information of network elements (EESs or EASs). para. [0274] in response to a notification message including one or more DNAI identifiers, the ECS determines that an edge network corresponding to the DNAI identifier. ECS determines the first network element); and transmit, to an Edge Enabler Client a service provisioning notification containing information on the EES and the EAS with the DNAI matching the target DNAI (para. [0095] after receiving a DNAI identifier, the control network element determines that an edge network corresponding to the DNAI identifier. para. [0273] ECS sends connection information of configured EDNs to the UE. connection information of the edge network (EHE or EDN) includes but is not limited to: EES address information, and EAS (list) information and EAS address information in the EDN.). Yao does not teach receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES. Gupta teaches receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES (para. [0037] receiving, by an edge configuration server (ECS), information of at least one edge application server (EAS) provided by a source edge enabler server (EES). para. [0051] EAS information profile comprises a list of service areas served by the EAS. para. [0071] service area of the EAS (112) or the service area of the EES (114) can be defined as… list of data network access identifiers (DNAIs) associated with the EDN which is hosting the EAS. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile.). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Gupta’s disclosure of receiving, from the EES, an EES registration request or an EES registration update. One of ordinary skill in the art would have been motivated to do so because Yao discloses that the ECS maintains information of EDNs and provides the information in response to requests. It would have been beneficial for the ECS to be updated and store information regarding the EES and EAS for management and servicing of requests. Yao discloses determining an EES and an EAS with a DNAI matching the target DNAI. Yao suggests determining an EES with a registered EAS based on DNAI matching a target DNAI as Yao discloses that the ECS determines a EES matching the DNAI and the EAS is registered with the EES (see para. [0229]). However, it is not expressly disclosed by Yao. Kim discloses determining which EES has a registered EAS with a DNAI matching one of the one or more DNAIs (para. [0134] in order to interact with the ECS 30, the target DNAI provided from the 3GPP network 40 may be transmitted to the ECS 30. ECS 30 may select the target EES based on the target DNAI). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Kim’s disclosure. One of ordinary skill in the art would have been motivated to do so because the ECS is a central control element that selects edge networks and edge elements, and it would have been beneficial to determine the EES for enabling discovery and access to the correct EAS by the UE. Regarding claim 34, Yao teaches a non-transitory computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of a network node, configure the network node to, when implementing an Edge Configuration Server, ECS: receiving, from a core network node, a notification of a user plane path management event associated with application traffic, wherein the notification comprises a target DNAI for the application traffic (para. [0083] core network element 101 is a network element that implements a session management function (session management function, SMF). para. [0097] user plane management event notification carries a changed DNAI. para. [0272] SMF detects that the user plane management event occurs and notifies the central AF of the event. para. [0262] central AF is an ECS); determining which EES and EAS with a DNAI matching the target DNAI (para. [0229] EES… responsible for managing, performing registration… each EAS deployed in the EDN. para. [0230] edge configuration server (edge configuration server, ECS) is a global management network element that maintains information of each EDN such as a service range and an EES address. para. [0273] central AF selects connection information of one or more edge networks (EHEs or EDNs), or selects connection information of network elements (EESs or EASs). para. [0274] in response to a notification message including one or more DNAI identifiers, the ECS determines that an edge network corresponding to the DNAI identifier. ECS determines the first network element); and transmitting, to an Edge Enabler Client a service provisioning notification containing information on the EES and the EAS with the DNAI matching the target DNAI (para. [0095] after receiving a DNAI identifier, the control network element determines that an edge network corresponding to the DNAI identifier. para. [0273] ECS sends connection information of configured EDNs to the UE. connection information of the edge network (EHE or EDN) includes but is not limited to: EES address information, and EAS (list) information and EAS address information in the EDN.). Yao does not teach receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES. Gupta teaches receiving, from an Edge Enabler Server, EES, an EES registration request or an EES registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES (para. [0037] receiving, by an edge configuration server (ECS), information of at least one edge application server (EAS) provided by a source edge enabler server (EES). para. [0051] EAS information profile comprises a list of service areas served by the EAS. para. [0071] service area of the EAS (112) or the service area of the EES (114) can be defined as… list of data network access identifiers (DNAIs) associated with the EDN which is hosting the EAS. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile.). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Gupta’s disclosure of receiving, from the EES, an EES registration request or an EES registration update. One of ordinary skill in the art would have been motivated to do so because Yao discloses that the ECS maintains information of EDNs and provides the information in response to requests. It would have been beneficial for the ECS to be updated and store information regarding the EES and EAS for management and servicing of requests. Yao discloses determining an EES and an EAS with a DNAI matching the target DNAI. Yao suggests determining an EES with a registered EAS based on DNAI matching a target DNAI as Yao discloses that the ECS determines a EES matching the DNAI and the EAS is registered with the EES (see para. [0229]). However, it is not expressly disclosed by Yao. Kim discloses determining which EES has a registered EAS with a DNAI matching one of the one or more DNAIs (para. [0134] in order to interact with the ECS 30, the target DNAI provided from the 3GPP network 40 may be transmitted to the ECS 30. ECS 30 may select the target EES based on the target DNAI). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to have modified Yao with Kim’s disclosure. One of ordinary skill in the art would have been motivated to do so because the ECS is a central control element that selects edge networks and edge elements, and it would have been beneficial to determine the EES for enabling discovery and access to the correct EAS by the UE. Regarding claim 25, Yao in view of Gupta and Kim teach the method of claim 24, wherein the one or more DNAIs are included in an EES profile or an EAS profile in the registration request or the registration update request (Gupta discloses provides information in an EAS profile in the registration request. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile). Regarding claim 29, Yao in view of Gupta and Kim teach the method of claim 24, wherein the notification of the user plane path management event comprises a DNAI change (Yao: para. [0097] core network element generates first information. the first information is a user plane management event notification, and the user plane management event notification carries a changed DNAI). Regarding claim 35, Yao in view of Gupta and Kim teach the network node of claim 33, wherein the one or more DNAIs are included in an EES profile or an EAS profile in the registration request or the registration update request (Gupta discloses provides information in an EAS profile in the registration request. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile. Kim is relied upon to teach providing a DNAI). Regarding claim 36, Yao in view of Gupta and Kim teach the network node of claim 33, wherein the notification of the user plane path management event comprises a DNAI change (Yao: para. [0097] core network element generates first information. the first information is a user plane management event notification, and the user plane management event notification carries a changed DNAI). Regarding claim 37, Yao in view of Gupta and Kim teach the non-transitory computer-readable storage medium of claim 34, wherein the one or more DNAIs are included in an EES profile or an EAS profile in the registration request or the registration update request (Gupta discloses provides information in an EAS profile in the registration request. para. [0055] EES1… sends a registration request to the ECS. registration request contains EAS information profile). Regarding claim 38, Yao in view of Gupta and Kim teach the non-transitory computer-readable storage medium of claim 34, wherein the notification of the user plane path management event comprises a DNAI change (Yao: para. [0097] core network element generates first information. the first information is a user plane management event notification, and the user plane management event notification carries a changed DNAI). 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 Joshua Joo whose telephone number is 571 272-3966. The examiner can normally be reached on Monday-Friday 7am-3pm 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, Oscar Louie can be reached on 571 270-1684. 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. /JOSHUA JOO/Primary Examiner, Art Unit 2445
Read full office action

Prosecution Timeline

Mar 23, 2023
Application Filed
Feb 22, 2024
Non-Final Rejection — §103, §112
May 23, 2024
Response Filed
Jun 14, 2024
Final Rejection — §103, §112
Aug 13, 2024
Response after Non-Final Action
Aug 20, 2024
Response after Non-Final Action
Sep 20, 2024
Request for Continued Examination
Oct 03, 2024
Response after Non-Final Action
Nov 15, 2024
Non-Final Rejection — §103, §112
Feb 13, 2025
Response Filed
Mar 07, 2025
Final Rejection — §103, §112
May 08, 2025
Response after Non-Final Action
Jun 12, 2025
Request for Continued Examination
Jun 16, 2025
Response after Non-Final Action
Sep 04, 2025
Non-Final Rejection — §103, §112
Dec 08, 2025
Response Filed
Feb 11, 2026
Final Rejection — §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12603875
CONNECTION ESTABLISHMENT USING SHARED CERTIFICATE IN GLOBAL SERVER LOAD BALANCING (GSLB) ENVIRONMENT
2y 5m to grant Granted Apr 14, 2026
Patent 12587590
SERVER APPARATUS, MANAGEMENT PROGRAM AND MANAGEMENT SYSTEM
2y 5m to grant Granted Mar 24, 2026
Patent 12580871
RESOURCE DEPLETION DETECTION AND NOTIFICATION IN AN ENTERPRISE FABRIC NETWORK
2y 5m to grant Granted Mar 17, 2026
Patent 12572647
CONNECTING ADVERSARIAL ATTACKS TO NEURAL NETWORK TOPOGRAPHY
2y 5m to grant Granted Mar 10, 2026
Patent 12572475
COMPACT REPRESENTATION OF TRANSITION SEQUENCES FOR SINGLE-STATE STORAGE
2y 5m to grant Granted Mar 10, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

7-8
Expected OA Rounds
78%
Grant Probability
98%
With Interview (+20.2%)
3y 1m
Median Time to Grant
High
PTA Risk
Based on 976 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in for Full Analysis

Enter your email to receive a magic link. No password needed.

Free tier: 3 strategy analyses per month