Prosecution Insights
Last updated: October 27, 2026
Application No. 19/233,474

Network Slice Authentication Method and Communications Apparatus

Non-Final OA §DP
Filed
Jun 10, 2025
Priority
Nov 05, 2018 — CN 201811307957.5 +3 more
Examiner
JEUDY, JOSNEL
Art Unit
2438
Tech Center
2400 — Computer Networks
Assignee
Huawei Technologies Co., Ltd.
OA Round
1 (Non-Final)
84%
Grant Probability
Favorable
1-2
OA Rounds
1y 4m
Est. Remaining
68%
With Interview

Examiner Intelligence

Grants 84% — above average
84%
Career Allowance Rate
677 granted / 807 resolved
+25.9% vs TC avg
Minimal -16% lift
Without
With
+-16.0%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
19 currently pending
Career history
829
Total Applications
across all art units

Statute-Specific Performance

§101
19.4%
-20.6% vs TC avg
§103
50.4%
+10.4% vs TC avg
§102
7.2%
-32.8% vs TC avg
§112
9.2%
-30.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 807 resolved cases

Office Action

§DP
DETAILED ACTION 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 . 1.This action is responsive to the communication filed on July 07, 2025. At this time, claims 1- 20 are pending and addressed below. 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 (i.e., changing from AIA to pre-AIA ) 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. Examiner’s Note Examiner urges applicant to submit the foreign priority documents. Double Patenting 2. 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 obviousness-type 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 Omum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and 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 a nonstatutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b). Claims 1-2, 9, 13 and 14 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1-2, 4, 11 and 13 of US Patent number 12355884 B2. The conflicting claims are not identical, they are not patentably distinct from each other because the current application contains claims that are broader in scope than the claims of the patent number 12355884 B2 and are anticipated by the claims 1-2, 4, 11 and 13. This is a Non-provisional double patenting rejection. Claims Comparison Table Application Number 19/233,474 Patent Number US 12355884 B2 1. A service authorization method comprising: sending, by a client and to a first server, a first request requesting an access token and comprising first slice information, wherein the first slice information comprises a network slice instance identifier list or a single network slice selection assistance information list, and wherein the client is a network function in a core network; and receiving, by the client and from the first server, a first response message comprising the access token, wherein the access token comprises the first slice information. 1. A service authorization method comprising: receiving, by a first server, a first request from a client that is a network element for performing a network function in a core network deployed using a service-based architecture, wherein the first request requests an access token, and wherein the first request comprises first slice information, and wherein the first slice information comprises a network slice instance (NSI) identifier (ID) list or a single network slice selection assistance information (S-NSSAI) list; performing, by the first server, authentication on the client; sending, by the first server, a first response message to the client when the client is authenticated, wherein the first response message comprises the access token, and wherein the access token comprises the first slice information; receiving, by a second server, a second request from the client, wherein the second request requests a function service, and wherein the second request comprises the access token; verifying, by the second server, the first slice information to obtain a verification result; and replying, by the second server, to the client based on the verification result. 2. The service authorization method of claim 1, wherein the access token further comprises an expected service name and type, an identifier of the client, or a type of the client. 2. The service authorization method of claim 1, wherein the access token further comprises an expected service name and type, a client identifier, and a client type. 9. An apparatus comprising at least one memory configured to store instructions; and at least ones processor coupled to the at least one memory and configured to execute the instructions to cause the apparatus to: send, to a first server, a first request requesting an access token and comprising first slice information, wherein the first slice information comprises a network slice instance identifier list or a single network slice selection assistance information list, and wherein the apparatus is a network function in a core network; and receive, from the first server, a first response message comprising the access token, wherein the access token comprises the first slice information. 4. A service authorization system comprising: a first server configured to: receive, from a client that is a network element for performing a network function in a core network deployed using a service-based architecture, a first request requesting an access token, wherein the first request comprises first slice information, and wherein the first slice information comprises a network slice instance (NSI) identifier (ID) list or a single network slice selection assistance information (S-NSSAI) list; perform authentication on the client; and send a first response message to the client when the client is authenticated, wherein the first response message comprises the access token, and wherein the access token comprises the first slice information; a second server in communication with the first server and configured to: receive, from the client, a second request requesting a function service, wherein the second request comprises the access token; verify the first slice information to obtain a verification result; and reply to the client based on the verification result; and a hardware processor configured to implement the first server or the second server. 13. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause an apparatus to: send to a first server, a first request requesting an access token and comprising first slice information, wherein the first slice information comprises a network slice instance identifier list or a single network slice selection assistance information list, and wherein the apparatus is a network function in a core network; and receive, from the first server, a first response message comprising the access token, wherein the access token comprises the first slice information. 11. A server comprising: a receiver configured to receive a request from a client that is a network element for performing a network function in a core network deployed using a service-based architecture, wherein the request requests an access token, wherein the request comprises slice information, and wherein the slice information comprises a network slice instance (NSI) identifier (ID) list or a single network slice selection assistance information (S-NSSAI) list; a processor coupled to the receiver and configured to authenticate the client; and a transmitter coupled to the processor and configured to send a response message to the client when the client is authenticated, wherein the response message comprises the access token, and wherein the access token comprises the slice information. 14. A system comprising: a client that is a network function in a core network and is configured to: send a first request requesting an access token, and comprising first slice information, wherein the first slice information comprises a network slice instance identifier list or a single network slice selection assistance information list; and receive a first response message comprising the access token, wherein the access token comprises the first slice information; and a first server configured to: receive the first request; perform authentication on the client; and send, to the client, the first response message when the authentication is successful. 13. A server comprising: a receiver configured to receive a request from a client that is a network element for performing a network function in a core network deployed using a service-based architecture, wherein the request requests a function service, wherein the request comprises an access token, wherein the access token comprises first slice information, and wherein the first slice information comprises a network slice instance (NSI) identifier (ID) list or a single network slice selection assistance information (S-NSSAI) list; a processor coupled to the receiver and configured to verify the first slice information to obtain a verification result; and a transmitter coupled to the processor and configured to reply to the client based on the verification result. Allowable Subject Matter The following is a statement of reasons for the indication of allowable subject matter: Ramanujan, US 10715327 B1 (IDS Submitted) does not disclose sending, by a client and to a first server, a first request requesting an access token and comprising first slice information, wherein the first slice information comprises a network slice instance identifier list or a single network slice selection assistance information list, and wherein the client is a network function in a core network; and receiving, by the client and from the first server, a first response message comprising the access token, wherein the access token comprises the first slice information. As similarly recited in independent claims 9, 13, 14. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Zhu, Lily, US20240205728, title “Systems and methods for management of network slice access.” Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOSNEL JEUDY whose telephone number is (571)270-7476. The examiner can normally be reached M-F 10:00-8: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, Arani T Taghi can be reached at (571)272-3787. 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. Date: 9/28/2026 /JOSNEL JEUDY/Primary Examiner, Art Unit 2438
Read full office action

Prosecution Timeline

Jun 10, 2025
Application Filed
Oct 01, 2026
Non-Final Rejection mailed — §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12764545
SMART DEVICE ACCESS CONTROLLER AND METHODS
2y 9m to grant Granted Oct 13, 2026
Patent 12756726
SYSTEMS AND METHODS FOR DETECTING ANOMALOUS BEHAVIOR
4y 4m to grant Granted Oct 06, 2026
Patent 12748856
ATTACK SCENARIO GENERATION APPARATUS, ATTACK SCENARIO GENERATION METHOD, AND COMPUTER READABLE MEDIUM
2y 8m to grant Granted Sep 29, 2026
Patent 12737477
TRIGGERING A SECURITY ACTION BASED ON AN AI-GENERATED CODE PACKAGE RECOMMENDATION
2y 5m to grant Granted Sep 15, 2026
Patent 12724878
GENERATING INSTRUMENTATION FOR DATA INTEGRITY OF FUNCTION CALLS
2y 9m to grant Granted Sep 01, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
84%
Grant Probability
68%
With Interview (-16.0%)
2y 9m (~1y 4m remaining)
Median Time to Grant
Low
PTA Risk
Based on 807 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

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

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month