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 .
Claim Objections
Claim 11 objected to because of the following informalities: said claim newly introduces TCE for the first time. That abbreviation needs to be spelled out and the antecedent basis issue needs to be addressed.
Claim Rejections - 35 USC § 103
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.
Claim(s) 1-4, 12-15 and 20 rejected under 35 U.S.C. 103 as being unpatentable over ETSI TS 128 622 V16.4.0 (“128”) in view of ETSI TS 132 422 V15.1.0 (“132”).
Examiner’s note: in what follows, references are drawn to 128 unless otherwise mentioned.
128 comprises the following features:
With respect to independent claims:
Regarding claim 1, an apparatus, the apparatus comprising processing circuitry coupled to storage ([4.3.3.1] “A ManagedElement IOC is used to represent a Network Element defined in TS 32.101[1] including virtualization or
non-virtualization scenario.”), the processing circuitry configured to:
receive a request from a consumer to create a Trace job ([4.3.30.1] “A TraceJob instance represents the Trace Control and Configuration parameters of a particular Trace Job (see TS 32.421 [29] and TS 32.422 [30] for details). To activate Trace Jobs, a MnS consumer has to create TraceJob object instances on the MnS producer. A MnS consumer can activate a Trace Job for another MnS consumer”) for collecting delay-related measurements from a User Plane Function (UPF) ([4.3.30.2] “tjMDTListOfMeasurements”, “tjMDTReportInterval”, and [4.4.1 on P51] “tjMDTListOfMeasurements; It specifies the UE measurements that shall be collected in anImmediate MDT job. The attribute is applicable only for Immediate MDT.” Note that UPF will be discussed in view of 132.);
request a Unified Data Management (UDM) system to create the Trace job (This will be discussed in view of 132.);
receive a response about a result of the Trace job creation from the UDM ([4.5.2] “This clause presents a list of notifications, defined in [27], that a MnS consumer can receive.”, and “notifyMOIObjectCreation”); and
send a response indicating the result of the Trace job creation to the consumer ([4.5.2] “The notification header attribute objectClass/objectInstance, defined in [3], captures the DN of an instance of an IOC defined in the present document.”).
It is noted that while disclosing a tracejob, 128 does not specifically teach about UDM. It, however, had been known in the art before the effective date of the instant application as shown by 132 as follows;
a User Plane Function (UPF) ([132, 4.1.2.15.1.3 on p75] “20. SMF performs N4 Session Establishment with UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502 [41]) and provides the trace control and configuration parameters information to the UPF.”);
request a Unified Data Management (UDM) system to create the Trace job ([132, 4.1.2.15.1.3 on p74] “1. Management system activates Trace Session to the UDM. The following trace control and configuration parameters shall be included in the Trace Activation message:”, and [132, 4.1.2.15.1.3 on p75] “2. UDM stores the trace control and configuration parameters received from the management system.”).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of instant application to modify the TraceJob creation and consumer notification framework of 128 by using the 5GC UDM and UP Trace Session activation procedure of 132 in order to create and activate a TraceJob at UDM for trace/measurement collection from UPF such that “When an AF, AMF, AISF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM receives Trace Session activation from the management function, it shall start a Trace Session.” [132, 4.1.1.8].
Regarding claim 12, it is a CRM claim corresponding to the method claim 1, except the limitations, “computer-readable medium storing computer-executable instructions”, and is therefore rejected for the similar reasons set forth in the rejection of claim 1.
Regarding claim 20, it is a method claim corresponding to the method claim 1, and is therefore rejected for the similar reasons set forth in the rejection of claim 1.
With respect to dependent claims:
Regarding claims 2 and 13, the apparatus of claim 1 and the CRM of claim 12, respectively, wherein the Trace job includes at least one trace control and configuration parameter selected from the group consisting of a Subscription Permanent Identifier (SUPI), International Mobile Equipment Identity Software Version (IMEISV), Session ID, Quality of Service (QoS) Flow Identifier (These alternatives are not examined.), Trace Reference ([4.4.1 on p50] “tjTraceReference A globally unique identifier, which uniquely identifies the Trace Session that is created by the TraceJob.”), a list of Network Element (NE) types to trace, a list of measurements, Report Interval, IP address of Trace Collection Entity (TCE), URI of the Trace Reporting Management Service (MnS) consumer, or Trace reporting format (These alternatives are not examined.).
Regarding claims 3 and 14, the apparatus of claim 1 and the CRM of claim 12, respectively, the UDM propagates the trace control and configuration parameters to an Access and Mobility Management Function (AMF) ([132, 4.1.2.15.1.3 on p75] “3. UDM sends Nudm_SDM_Notification to AMF with the trace control and configuration parameters information (see clauses 4.5.1 and 5.2.3.3 of 3GPP TS 23.502 [41]).”).
Regarding claims 4 and 15, the apparatus of claim 3 and the CRM of claim 14, respectively, wherein the AMF propagates the trace control and configuration parameters to a Session Management Function (SMF) ([132, 4.1.2.15.1.3 on p75] “11. AMF sends the Nsmf_PDUSession_CreateSMContext request to the selected SMF”).
Claim(s) 5, 8-10, 16 and 19 rejected under 35 U.S.C. 103 as being unpatentable over ETSI TS 128 622 V16.4.0 (“128”) in view of ETSI TS 132 422 V15.1.0 (“132”) and further in view of Wang et al. (US 2025/0071034, “Wang”).
Examiner’s note: in what follows, references are drawn to 128 unless otherwise mentioned.
Regarding claims 5 and 16, it is noted that while disclosing a tracejob, 128 does not specifically teach about UDM. It, however, had been known in the art before the effective date of the instant application as shown by Wang as follows;
the apparatus of claim 4 and the CRM of claim 15, respectively, wherein the SMF activates Quality of Service (QoS) monitoring for a User Equipment (UE), Packet Data Unit (PDU) session, and QoS flow to be measured ([132, 4.1.2.15.1.3 on p75] “20. SMF performs N4 Session Establishment with UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502 [41]) and provides the trace control and configuration parameters information to the UPF.”, and [Wang, 0154] “in step 404, the first network element (e.g., serving SMF) may (e.g., send configuration information to) configure the UPF (PMF) for QoS monitoring and may send a (e.g., QoS monitoring response) message comprising information indicating a QoS monitoring response to the AIML-serving NF.”).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of instant application to modify the SMF trace control / configuration handling of 128 in view of 132 by using Wang’s serving SMF QoS monitoring configuration in order to configure the UPF for QoS monitoring of an identified UE, PDU session and QoS flow such that “Methods, architectures, apparatuses, and systems directed to real-time QoS monitoring and prediction are described herein.” [Wang, 0004].
Regarding claims 8 and 19, the apparatus of claim 5 and the CRM of claim 16, respectively, wherein the SMF propagates the trace control and configuration parameters to a UPF ([132, 4.1.2.15.1.3 on p75] “20. SMF performs N4 Session Establishment with UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502 [41]) and provides the trace control and configuration parameters information to the UPF. 21. UPF stores the trace control and configuration parameters received from the SMF as part of N4 Session Establishment.”).
Regarding claim 9, the apparatus of claim 8, wherein the UPF starts a Trace Session ([132, 4.1.2.15.1.3 on p75] “22. UPF starts the Trace Session according to the received configuration.”).
Regarding claim 10, the apparatus of claim 9, wherein the UPF produces the measurements and optionally starts a Trace Recording Session ([132, 4.2.2.9 on p106] “In an AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM, a Trace Recording Session should start after the reception of a Trace Session Activation from management system and if any of the defined start triggering events occur. During the Trace Recording Session, the AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM shall record those signalling messages in the interfaces that are defined in the list of interfaces parameter.”).
Claim(s) 6 and 17 rejected under 35 U.S.C. 103 as being unpatentable over ETSI TS 128 622 V16.4.0 (“128”) in view of ETSI TS 132 422 V15.1.0 (“132”) and Wang et al. (US 2025/0071034, “Wang”), and further in view of Dao et al. (US 2018/0262924, “Dao”).
Examiner’s note: in what follows, references are drawn to 128 unless otherwise mentioned.
Regarding claims 6 and 17, it is noted that while disclosing a tracejob, 128 does not specifically teach about activating QoS monitoring. It, however, had been known in the art before the effective date of the instant application as shown by Dao as follows;
the apparatus of claim 5 and the CRM of claim 16, respectively, wherein the SMF receives the request to activate QoS monitoring from a Policy Control Function (PCF) ([Dao, 0038] “The SMF 235 manages establishing the UP connection between the UE 110 and a node or network function (e.g. a DN gateway function) connected to the DN 140. The PCF 236 provides policies to network functions for the handling of a UE's session. Such policies include QoS”, and [Dao, 0008] “The communication network comprises a NWDA function, a user plane function (UPF) connected to the NWDA function via a first interface, a unified data management (UDM) function connected to the NWDA function via a second interface, an access and mobility function (AMF) connected to the NWDA function via a third interface, a session management function (SMF) connected to the NWDA function via a fourth interface, and a policy and control function (PCF) connected to the NWDA function via a fifth interface.”).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of instant application to modify Wang’s serving SMF QoS monitoring configuration procedure to receive the QoS monitoring request from Dao’s PCF in order to apply PCF provided QoS session policies to the SMF’s QoS monitoring configuration such that “there is provided a method of policy optimization in a communication network.” [Dao, 0006].
Claim(s) 7, 11 and 18 rejected under 35 U.S.C. 103 as being unpatentable over ETSI TS 128 622 V16.4.0 (“128”) in view of ETSI TS 132 422 V15.1.0 (“132”) and Wang et al. (US 2025/0071034, “Wang”), and further in view of Guo et al. (US 2026/0082269, “Guo”)
Examiner’s note: in what follows, references are drawn to 128 unless otherwise mentioned.
Regarding claims 7 and 18, it is noted that while disclosing a tracejob, 128 does not specifically teach about receiving a request for QoS monitoring. It, however, had been known in the art before the effective date of the instant application as shown by Guo as follows;
the apparatus of claim 5 and the CRM of claim 16, respectively, wherein the SMF receives the request to activate QoS monitoring from a management function ([Guo, 0071] “after generating the QoS monitoring policy, the PCF may include the authorized QoS monitoring policy in a policy and charging control (PCC) rule, and provide it to the SMF.”).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of instant application to modify 128 by using features of Guo in order to activate QoS monitoring for the current PDU session based on a management function policy such that “the demand for end-to-end QoS control of services has become more and more abundant, so that application scenarios of the QoS monitoring mechanism also need to be further enhanced” [Guo, 0004].
Regarding claim 11, the apparatus of claim 10, wherein the UPF reports the produced measurements to the TCE ([Guo, 0105] “Step III: the UPF reports the QoS monitoring result to the SMF.”, [Guo, 0157] “the packet delay between the UPF and the DN may be measured by the UPF.”, and [132, 4.1.1.2a on p17] “The Trace Records shall be forwarded to the Trace Collection Entity indicated in the MDT report received from the UE in case of Logged MDT.”).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Harry H. Kim whose telephone number and email address are as follows; 571-272-5009, harry.kim2@uspto.gov.
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, Derrick Ferris can be reached at 571-272-3123.
Information regarding the status of an application may be obtained from www.uspto.gov. For questions or assistance, 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.
/HARRY H KIM/ Primary Examiner, Art Unit 2411
