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 .
Allowable Subject Matter
Claim 26 objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
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 (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.
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.
Independent Claim
Claim(s) 21 is/are rejected under 35 U.S.C. 103 as being unpatentable over 3GPP TS 23.558 Architecture for enabling Edge Applications, September 24, 2021 in view of 3GPP TS 32.291, 5G system, charging service, December 23, 2021.
As to claim 21: TS 23.558 teaches an electronic device comprising: one or more processors; and one or more non-transitory computer-readable media comprising instructions, the one or more processors configure the electronic device to, when the instructions are executed: identify a notification related to an edge application server (EAS) lifecycle management (LCM) entity (8.6.3.2.3 The EES detects the ACR management event of the UE).
TS 23.558 may not explicitly teach generate charging data related to the EAS LCM entity (5.2.2.2; 6.1.6.1 Charging Data Request to the CHF); transmit, based on the charging data, a charging data request to a network function of at least one of a cellular system and a management system (5.2.2.2 NF (CTF) sends a Nchf_ConvergedCharging_Create request to the CHF to create resource for charging; 6.2.5.2.1.1 multipleUnitUsage this field contains parameters for usage reporting); and identify, based on the charging data request, a charging data response received from the network function. However, TS 32.291 teaches generate charging data related to the EAS LCM entity (5.2.2.2; 6.1.6.1 Charging Data Request to the CHF); transmit, based on the charging data, a charging data request to a network function of at least one of a cellular system and a management system (5.2.2.2 NF (CTF) sends a Nchf_ConvergedCharging_Create request to the CHF to create resource for charging; 6.2.5.2.1.1 multipleUnitUsage this field contains parameters for usage reporting); and identify, based on the charging data request, a charging data response received from the network function (6.1.6.1 Charging Data Response from CHF; 6.1.6.2.1.2-1 the same value of the sequence number received in the request should be used in the response).
Thus, it would have been obvious to one of ordinary skill in the art to implement charging data, taught by TS 32.291, into the communication management system, taught by TS 23.558, in order to implement a well-known feature of a pre-defined protocol and enable billing for activities. In addition, it would have been obvious to combine TS 23.558 and TS 32.291 in a known manner to obtain predictable results as the combination would not change the essence, quiddity, or functionality of the prior art references.
Dependent Claims
Claim(s) 22, 25 is/are rejected under 35 U.S.C. 103 as being unpatentable over 3GPP TS 23.558 Architecture for enabling Edge Applications, September 24, 2021; 3GPP TS 32.291, 5G system, charging service, December 23, 2021 in view of 3GPP TS 32.257 Charging management; Edge Computing domain charging, November, 2021.
As to claim 22: TS 23.558 teaches the electronic device of claim 21.
TS 23.558 may not explicitly teach wherein the logic is electronic device is configured to operate as a charging enablement function (CEF). However, TS 32.257 wherein the logic is electronic device is configured to operate as a charging enablement function (CEF) (section 4.2.2, p.10 The CEF consumes the MnS from the MnS producer for EAS management).
Thus, it would have been obvious to one of ordinary skill in the art to implement CEF, taught by TS 32.257, into the communication management system, taught by 23.558, in order to implement a well-known feature of a pre-defined protocol and enabling billing services. In addition, it would have been obvious to combine TS 23.558 and TS 32.257 in a known manner to obtain predictable results as the combination would not change the essence, quiddity, or functionality of the prior art references.
As to claim 25: TS 23.558 teaches the electronic device of claim 21.
TS 23.558 may not explicitly teach wherein the notification related to the EAS LCM entity is received from a management service (MnS) producer. However, TS 32.257 wherein the notification related to the EAS LCM entity is received from a management service (MnS) producer (section 4.2.2, p.10 The CEF consumes the MnS from the MnS producer for EAS management).
Thus, it would have been obvious to one of ordinary skill in the art to implement CEF, taught by TS 32.257, into the communication management system, taught by 23.558, in order to implement a well-known feature of a pre-defined protocol and enabling billing services. In addition, it would have been obvious to combine TS 23.558 and TS 32.257 in a known manner to obtain predictable results as the combination would not change the essence, quiddity, or functionality of the prior art references.
Claim(s) 23, 24 is/are rejected under 35 U.S.C. 103 as being unpatentable over 3GPP TS 23.558 Architecture for enabling Edge Applications, September 24, 2021 in view of 3GPP TS 32.291, 5G system, charging service, December 23, 2021.
As to claim 23: TS 23.558 teaches the electronic device of claim 21.
TS 23.558 may not explicitly teach wherein the second logic network function is a charging function (CHF). However, TS 32.291 teaches wherein the second logic network function is a charging function (CHF) (5.2.2.2; 6.1.6.1 Charging Data Request to the CHF)).
Thus, it would have been obvious to one of ordinary skill in the art to implement charging data, taught by TS 32.291, into the communication management system, taught by TS 23.558, in order to implement a well-known feature of a pre-defined protocol and enable billing for activities. In addition, it would have been obvious to combine TS 23.558 and TS 32.291 in a known manner to obtain predictable results as the combination would not change the essence, quiddity, or functionality of the prior art references.
As to claim 24. (Previously Presented) The electronic device of claim 21, wherein the cellular system is a fifth generation (5G) cellular system (section 2, p.13).
Claim(s) 27 is/are rejected under 35 U.S.C. 103 as being unpatentable over 3GPP TS 23.558 Architecture for enabling Edge Applications, September 24, 2021; 3GPP TS 32.291, 5G system, charging service, December 23, 2021 in view of 3GPP TS 28.532 Management and orchestration; Generic management services, December 23, 2021.
As to claim 27: TS 23.558 teaches the electronic device of claim 21.
TS 23.558 may not explicitly teach wherein the notification is a notifyMOICreation notification, a notifyMOIAttributeValueChanges notification, or a notifyMOIDeletion notification. However, TS 28.532 wherein the notification is a notifyMOICreation notification, a notifyMOIAttributeValueChanges notification, or a notifyMOIDeletion notification (section 11.1.1.11, p.34 The MnS producer decides whether to send notifications of type notifyMOICreation, notifyMOIDeletion or notifyMOIAttributesValueChange, or a single notifyMOIChanges reporting all changes in a single notification).
Thus, it would have been obvious to one of ordinary skill in the art to implement notifications, taught by TS 28.532, into the communication management system, taught by TS 23.558, in order to implement a well-known feature of a pre-defined protocol and enable billing and charging services. In addition, it would have been obvious to combine TS 23.558 and TS 28.532 in a known manner to obtain predictable results as the combination would not change the essence, quiddity, or functionality of the prior art references.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANDREW CHUNG SUK OH whose telephone number is (571)270-5273. The examiner can normally be reached M-F 12p-8p.
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, Faruk Hamza can be reached at 5712727969. 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.
/ANDREW C OH/ Primary Examiner, Art Unit 2466