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 .
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.
Claims 1-3, 5-7, 11, 15, 17-18, 20-21, 23-25, 28, 33, 36-38 are rejected in the Instant Application. Claims 4, 8-10, 12-14, 16, 19, 22, 26-27, 29-32, 34-35, 39-49 were cancelled by preliminary amendment.
Priority
Examiner acknowledges Applicant’s claim to priority benefits of PCT/CN2021/129111 filed 11/5/2021.
Information Disclosure Statement
The information disclosure statement(s) (IDS) submitted on 4/29/2024, 2/27/2026 is/are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement(s) is/are being considered if signed and initialed by the Examiner.
Claim Rejections
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 36-38 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Event (“Event Exposure service Operation of Network Slice Status,” Huawei et al., 3GPP TSG-WG SA2 Meeting #144E, April 12-16, 2021).
With respect to Claim 36, Event teaches a method for reporting slice state information of multiple network slice admission control functions (NSACFs), performed by an application function (AF) or an application service provider (ASP), comprising: sending a first network slice state subscription request to a first NSACF, wherein the first network slice state subscription request comprises a network slice; (pg. 10, Section 4.15.3.2.X.1; AF uses NEF to subscribe to number of registered UEs of S-NSSAI. The NEF subscribes to events from the primary NSACF. If the primary NSACF is not collocated with secondary NSACFs, the primary NSACF invokes Nnsacf_EventExposure_StatusSubscribe to subscribe via the NEF to all the secondary NSACFs for the S-NSSAI. Pg. 11, Section 5.2.21.Y.1; Nnsacf_EventExposure provides event subscription by a consumer NF which can be a NSACF. The NSSAI is slice state identifier. Consequently, the Nnsacf_EventExposure request is a subscription to slice state information that is sent by a NSACF to multile NSACFs corresponding to the network slice.)
and receiving network slice state response information sent by the first NSACF. (pgs. 10-11, Section 4.15.3.2.x.1; When the condition of the event notification trigger is met, the NSACF notifies the event and the NEF reports event data.)
With respect to Claim 37, Event teaches the method of claim 36, and Event also teaches wherein the first slice state subscription request comprises at least one of a subscription event, subscription event filtering information, and subscription event reporting mode information, or an immediate reporting identifier, wherein the immediate reporting identifier is configured to instruct the first NSACF to immediately send the network slice state response information upon receiving the first network slice state subscription request. (pgs. 10-11, Section 4.15.3.2.x.1 and Section 5.2.21.Y.2; Subscription with event ID.)
With respect to Claim 38, Event teaches the method of claim 37, and Event also teaches wherein the subscription event comprises at least one of: a number of terminals registered on the network slice; a number of packet data unit (PDU) sessions established on the network slice; a ratio of the number of terminals registered on the network slice to a maximum allowable number of registered terminals; a ratio of the number of PDU sessions established on the network slice to a maximum allowable number of established PDU sessions; the number of terminals registered on the network slice, and the ratio of the number of terminals registered on the network slice to the maximum allowable number of registered terminals; or the number of PDU sessions established on the network slice, and the ratio of the number of PDU sessions established on the network slice to the maximum allowable number of established PDU sessions; or wherein the subscription event filtering information comprises at least one of: single network slice selection assistance information (S-NSSAI) of the network slice; a registration area (RA) of the network slice; a combination of the S-NSSAI of the network slice and a data network name (DNN); or an area of interest (IoA) of the network slice; or wherein the subscription event reporting mode information comprises at least one of: a threshold for triggering reporting; or a periodic time interval for triggering the reporting. (pgs. 10-11, Section 4.15.3.2.x.1 and Section 5.2.21.Y.1; Subscription with current number of registered UEs.)
Claim Rejections - 35 USC § 103
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 of this title, 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-3, 5-7, 11, 15, 17-18, 20-21, 23-25, 28, and 33 are rejected under 35 U.S.C. 103 as being unpatentable over Event (“Event Exposure service Operation of Network Slice Status,” Huawei et al., 3GPP TSG-WG SA2 Meeting #144E, April 12-16, 2021) in view of 3GPP (“3GPP TS 23.502 V17.0.0,” 3GPP Global Initiative, March, 2021).
With respect to Claim 1, Event teaches a method for reporting slice state information of multiple network slice admission control functions (NSACFs), performed by a first NSACF, comprising: subscribing to slice state information of a network slice from multiple NSACFs corresponding to the network slice (pg. 10, Section 4.15.3.2.X.1; AF uses NEF to subscribe to number of registered UEs of S-NSSAI. The NEF subscribes to events from the primary NSACF. If the primary NSACF is not collocated with secondary NSACFs, the primary NSACF invokes Nnsacf_EventExposure_StatusSubscribe to subscribe via the NEF to all the secondary NSACFs for the S-NSSAI. Pg. 11, Section 5.2.21.Y.1; Nnsacf_EventExposure provides event subscription by a consumer NF which can be a NSACF. The NSSAI is slice state information. Consequently, the Nnsacf_EventExposure request is a subscription to slice state information that is sent by a NSACF to multile NSACFs corresponding to the network slice.)
and obtaining, through the NEF, the slice state information of the network slice reported by the multiple NSACFs. (pgs. 10-11, Section 4.15.3.2.x.1; When the condition of the event notification trigger is met, the NSACF notifies the event. Pg. 11, Section 5.2.21.Y.1; Subscription may be sent to NSACF.)
But Event does not explicitly teach NSACF subscription through a network exposure function (NEF).
3GPP, however, does teach through a network exposure function (NEF); obtaining, through the NEF; (Event does not explicitly indicate that Nnsacf_EventExposure results in subscriptions and responses through the NEF because Event merely states “the primary NSACF invokes NNsacf[] to all the secondary NSACFs…” Examiner asserts that Event renders this obvious on its own. Event already discloses an event subscription request being sent to the NEF which results in the NSACF sending data to the subscriber through the NEF, see pg. 10, Section 4.15.3.2.X.1; AF uses Nnef_EventExposure to send a request to the NEF which results in receiving event data from NSACF. Event further identifies that NSACFs can be consumers of subscriptions, see pg. 11. Section 5.2.21.Y.1; NSACF can be consumer of Nnsacf_EventExposure. Therefore, it would have been obvious to one of ordinary skill to have a primary NSACF subscribe through NEF to the secondary NSACFs to allow the NEF to deliver the information to the primary NSACF in the same manner it delivers it to the AF. Regardless, Examiner notes that Event is seeking to modify Section 4.15 of 23.502 v17. Examiner therefore cites that document. See 3GPP, pg. 309, Section. 4.15.2; Monitoring for external exposure is done via NEF. See also pgs. 152-153; An AF may contact directly or via the NEF. NEF ensures authorization control.)
It would have been obvious to one of ordinary skill prior to the effective filing date to combine the method of Event with the subscription and obtaining through the NEF in order to ensure authorization control for external consumers.
With respect to Claim 2, modified Event teaches the method of claim 1, and Event also teaches further comprising: receiving a first network slice state subscription request sent by an application function (AF) or an application service provider (ASP), wherein the first network slice state subscription request comprises an identifier of the network slice. (pg. 10, Section 4.15.3.2.X.1 and Fig. 4.15.3.2.X.1-1; AF sends Nnef_EventExposure_Subscribe/Unsubscribe Request to NEF which forwards to NSACF. The request includes Event Filter which includes S-NSSAI information which is an identifier of the network slice.)
With respect to Claim 3, modified Event teaches the method of claim 1, and Event also teaches wherein subscribing to the slice state information of the network slice from the multiple NSACFs corresponding to the network slice through the NEF comprises: sending a second network slice state subscription request to the NEF, wherein the second network slice state subscription request is configured for the NEF to send the second network slice state subscription request to the multiple NSACFs corresponding to the network slice or for the NEF to send the second network slice state subscription request to a second NSACF in the multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice. (pg. 10, Section 4.15.3.2.X.1; Request to subscribe to events sent to NEF and forwarded to NSACF for S-NSSAI. For the request going through the NEF see 3GPP, pg. 309, Section. 4.15.2; Monitoring for external exposure is done via NEF. See also pgs. 152-153; An AF may contact directly or via the NEF. NEF ensures authorization control.)
With respect to Claim 5, modified Event teaches the method of claim 2, and Event also teaches further comprising: generating network slice state response information based on the slice state information of the network slice in the multiple NSACFs; and sending the network slice state response information to the AF or ASP. (pgs. 10-11, Section 4.15.3.2.x.1; When the condition of the event notification trigger is met, the NSACF notifies the event to the AF.)
With respect to Claim 6, modified Event teaches the method of claim 5, and Event also teaches wherein the first slice state subscription request comprises at least one of a subscription event, subscription event filtering information, subscription event reporting mode information, or an immediate reporting identifier, wherein the immediate reporting identifier is configured to instruct the first NSACF to immediately send the network slice state response information upon receiving the first network slice state subscription request. (pgs. 10-11, Section 4.15.3.2.x.1 and Section 5.2.21.Y.2; Subscription with event ID.)
With respect to Claim 7, modified Event teaches the method of claim 6, and Event also teaches wherein the subscription event comprises at least one of: a number of terminals registered on the network slice; a number of packet data unit (PDU) sessions established on the network slice; a ratio of the number of terminals registered on the network slice to a maximum allowable number of registered terminals; a ratio of the number of PDU sessions established on the network slice to a maximum allowable number of established PDU sessions; the number of terminals registered on the network slice, and the ratio of the number of terminals registered on the network slice to the maximum allowable number of registered terminals; or the number of PDU sessions established on the network slice, and the ratio of the number of PDU sessions established on the network slice to the maximum allowable number of established PDU sessions; or wherein the subscription event filtering information comprises at least one of: single network slice selection assistance information (S-NSSAI) of the network slice; a registration area (RA) of the network slice; a combination of the S-NSSAI of the network slice and a data network name (DNN); or an area of interest (IoA) of the network slice; or wherein the subscription event reporting mode information comprises at least one of: a threshold for triggering reporting; or a periodic time interval for triggering the reporting. (pgs. 10-11, Section 4.15.3.2.x.1 and Section 5.2.21.Y.1; Subscription with current number of registered UEs.)
With respect to Claim 11, modified Event teaches the method of claim 5, and 3GPP also teaches wherein generating the network slice state response information based on the slice state information of the network slice in the multiple NSACFs comprising: aggregating the state information of the network slice in the multiple NSACFs to generate the slice state response information. (Examiner asserts aggregating data is obvious because it is simple combination of data for predictable results, see MPEP 2143(I)(A). It would have been obvious to one of ordinary skill prior to the effective filing date to aggregate the data to report the state of the slice. Further, see pgs. 307-308; aggregation of UE data before reporting it.)
The same motivation to combine as the independent claim applies here.
With respect to Claim 15, modified Event teaches the method of claim 6, and Event also teaches further comprising: filtering the network slice state response information based on the subscription event filtering information, or determining whether a reporting condition is met based on the subscription event reporting mode information; and when the reporting condition is met, reporting the network slice state response information. (pgs. 10-11, Section 4.15.3.2.x.1; Request includes event filter and event reporting information. Notification of event is based on trigger being met. Pg. 3; event reporting mode.)
With respect to Claim 17, modified Event teaches the method of claim 2, and Event also teaches wherein receiving the first slice state subscription request sent by the AF or ASP comprises: receiving the first slice state subscription request sent by the AF or ASP through the NEF, (pg. 10, Section 4.15.3.2.X.1 and Fig. 4.15.3.2.X.1-1; AF sends Nnef_EventExposure_Subscribe/Unsubscribe Request to NEF which forwards to NSACF. The request includes Event Filter which includes S-NSSAI information which is an identifier of the network slice.)
wherein the AF or ASP is an untrusted AF or ASP. (pg. 10, Section 4.15.3.2.X.1; System checks whether AF is authorized for subscription, which suggests at least some AFs are untrusted. See also 3GPP, Section 4.12.)
With respect to Claim 18, modified Event teaches the method of claim 17, and Event also teaches wherein the first NSACF is selected by the NEF, or wherein the first NSACF is selected by the NEF through a network repository function (NRF), or the first NSACF is selected by the NEF through a local configuration. (pg. 10, Section 4.15.3.2.X.1; NEF queries NRF to find primary NSACF.)
With respect to Claim 20, Event teaches a method for reporting slice state information of multiple network slice admission control functions (NSACFs), performed by a network exposure function (NEF), comprising: wherein the first network slice state subscription request comprises an identifier of a network slice; (pg. 10, Section 4.15.3.2.X.1; AF uses NEF to subscribe to number of registered UEs of S-NSSAI. The NEF subscribes to events from the primary NSACF. If the primary NSACF is not collocated with secondary NSACFs, the primary NSACF invokes Nnsacf_EventExposure_StatusSubscribe to subscribe via the NEF to all the secondary NSACFs for the S-NSSAI. Pg. 11, Section 5.2.21.Y.1; Nnsacf_EventExposure provides event subscription by a consumer NF which can be a NSACF. The NSSAI is slice state identifier. Consequently, the Nnsacf_EventExposure request is a subscription to slice state information that is sent by a NSACF to multile NSACFs corresponding to the network slice.)
obtaining the slice state information of the network slice reported by the multiple NSACFs; and sending the slice state information to the first NSACF. (pgs. 10-11, Section 4.15.3.2.x.1; When the condition of the event notification trigger is met, the NSACF notifies the event and the NEF reports event data.)
But Event does not explicitly teach receiving a first network slice state subscription request sent by a first NSACF.
3GPP, however, does teach receiving a first network slice state subscription request sent by a first NSACF, (Event does not explicitly indicate that Nnsacf_EventExposure results in subscriptions and responses through the NEF because Event merely states “the primary NSACF invokes NNsacf[] to all the secondary NSACFs…” Examiner asserts that Event renders this obvious on its own. Event already discloses an event subscription request being sent to the NEF which results in the NSACF sending data to the subscriber through the NEF, see pg. 10, Section 4.15.3.2.X.1; AF uses Nnef_EventExposure to send a request to the NEF which results in receiving event data from NSACF. Event further identifies that NSACFs can be consumers of subscriptions, see pg. 11. Section 5.2.21.Y.1; NSACF can be consumer of Nnsacf_EventExposure. Therefore, it would have been obvious to one of ordinary skill to have a primary NSACF subscribe through NEF to the secondary NSACFs to allow the NEF to deliver the information to the primary NSACF in the same manner it delivers it to the AF. Regardless, Examiner notes that Event is seeking to modify Section 4.15 of 23.502 v17. Examiner therefore cites that document. See 3GPP, pg. 309, Section. 4.15.2; Monitoring for external exposure is done via NEF. See also pgs. 152-153; An AF may contact directly or via the NEF. NEF ensures authorization control.)
subscribing to slice state information of the network slice from multiple NSACFs corresponding to the network slice; (First see Event, Pg. 11, Section 5.2.21.Y.1; Nnsacf_EventExposure provides event subscription by a consumer NF which can be a NSACF. Then see 3GPP, pg. 314-315; NEF may subscribe itself to monitoring events.)
It would have been obvious to one of ordinary skill prior to the effective filing date to combine the method of Event with the subscription through the NEF in order to ensure authorization control for external consumers.
With respect to Claims 21, 23-25, 28, 33, they are substantially similar to Claims 3, 5-7, 11, 18, respectively, and are rejected in the same manner, the same art and reasoning applying.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NICHOLAS P CELANI whose telephone number is (571)272-1205. The examiner can normally be reached on M-F 9-5.
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, Vivek Srivastava can be reached on 571-272-7304. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/NICHOLAS P CELANI/Examiner, Art Unit 2449
Prosecution Insights