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 .
Response to Amendment
The Examiner acknowledges the receipt of the Applicant’s amendment filed on 05/20/2026. Claims 1, 3, 8, 10, 14, and 16 have been amended. Claims 1-20 are currently pending in the present application.
Response to Arguments
Applicant’s arguments with respect to claims 1-20 have been considered but are moot in view of the new grounds of rejection.
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Dai et al. (US 2023/0336657 A1 herein Dai), and further in view of Szilagyi et al. (US 2017/0359743 A1 herein Szilagyi).
Regarding claim 1, Dai teaches a method for performing a call trace in a cloud- based communication network comprising a plurality of network functions (read as cellular network which can accommodate the cloud-based architecture which includes cellular networks) (Dai - Figure 1, [0020]), where each network function includes one or more pods (read as each network function can include multiple pods) (Dai - [0043]- [0044]), the method comprising:
receiving, using a call trace module, a region (read as cloud computing regions 210) (Dai - Figure 2, [0040]-[0041]) for a user equipment (UE) device and a subscriber number for the UE device (read subscriber management components 170; International Mobile Subscriber Identity) (Dai - [0033], [0036], [0056]);
identifying, using the call trace module, a set of the network functions associated with the region for the UE device from the plurality of network functions of the communication network (read as cloud platform drill engine 514 can identify all of the cellular network core NF instances and their respective identifiers within the specified cloud computing region or sub-region) (Dai - Figure 5, [0067]);
establishing, using the call trace module, a call trace for each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
However, Dai fails to teach collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions; storing, using the call trace module, the collected call trace data in a data storage device; and generating, using the call trace module, a report with at least the collected call trace data.
In the related art, Szilagyi teaches collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]); storing, using the call trace module, the collected call trace data in a data storage device (read as the closed set of calls (i.e. of trace data or call traces 60 representing the calls) are stored in memory 80 or the like used as a call storage from which the closed set calls is transferred to the analysis element of function 30) (Szilagyi – Figure 3, [0083]); and generating, using the call trace module, a report with at least the collected call trace data (read as sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace; a sequence element carries information about the associated part of the call trace that is relevant) (Szilagyi – [0105]).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date to incorporate the teachings of Szilagyi into the teachings of Dai for the purpose of providing a sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace, wherein a sequence element carries information about the associated part of the call trace that is relevant.
Regarding claim 2 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein establishing, using the call trace module, a call trace for each network function of the set of network functions further comprises establishing a call trace for at least one pod of each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
Regarding claim 3 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions further comprises collecting only call trace data associated with the subscriber number for the UE device from at least one pod in the one or more network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]).
Regarding claim 4 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein the subscriber is a phone number (read as subscriber's mobile phone) (Dai - Abstract, [0002]).
Regarding claim 5 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein the identified set of network functions associated with the region for the UE device includes one or more of an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and an evolved packet data gateway (ePDG).
Regarding claim 6 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein the call trace data comprises signaling messages (read as messages exchanged between functions) (Dai - [0047], [0050]).
Regarding claim 7 as applied to claim 1, Dai as modified by Szilagyi further teaches wherein the region for a user equipment (UE) device is a region in which the UE device is physically located (read as functionality of such components can be co- located or located at disparate physical server systems; certain components of 5G core 139 may be co-located with components of CU 129) (Dai - [0024]).
Regarding claim 8, Dai teaches a system for performing a call trace in a cloud- based communication network comprising a plurality of network functions (read as cellular network which can accommodate the cloud-based architecture which includes cellular networks) (Dai - Figure 1, [0020]), where each network function includes one or more pods (read as each network function can include multiple pods) (Dai - [0043]- [0044]), the system comprising:
a memory that stores one or more computer readable media that include instructions (read as non-transitory computer-readable medium such as storage medium) (Dai - [0005], [0016], [0085]); and
one or more processor devices that execute the instructions of the computer readable media to perform a process (read as one or more processors) (Dai - [0005]- [0006]) comprising:
receiving a region (read as cloud computing regions 210) (Dai - Figure 2, [0040]-[0041]) for a user equipment (UE) device and a subscriber number for the UE device (read subscriber management components 170; International Mobile Subscriber Identity) (Dai - [0033], [0036], [0056]);
identifying a set of the network functions associated with the region for the UE device from the plurality of network functions of the communication network (read as cloud platform drill engine 514 can identify all of the cellular network core NF instances and their respective identifiers within the specified cloud computing region or sub- region) (Dai - Figure 5, [0067]);
establishing a call trace for each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
However, Dai fails to teach collecting only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions; storing the collected call trace data; and generating a report with at least the collect call trace data.
However, Szilagyi teaches collecting only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]); storing the collected call trace data (read as the closed set of calls (i.e. of trace data or call traces 60 representing the calls) are stored in memory 80 or the like used as a call storage from which the closed set calls is transferred to the analysis element of function 30) (Szilagyi – Figure 3, [0083]); and generating a report with at least the collect call trace data (read as sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace; a sequence element carries information about the associated part of the call trace that is relevant) (Szilagyi – [0105]).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date to incorporate the teachings of Szilagyi into the teachings of Dai for the purpose of providing a sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace, wherein a sequence element carries information about the associated part of the call trace that is relevant.
Regarding claim 9 as applied to claim 8, Dai as modified by Szilagyi further teaches wherein establishing a call trace for each network function of the set of network functions further comprises establishing a call trace for at least one pod of each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
Regarding claim 10 as applied to claim 8, Dai as modified by Szilagyi further teaches wherein collecting call trace data associated with the subscriber number for the UE device from one or more network functions further comprises collecting only call trace data associated with the subscriber number for the UE device from at least one pod in the one or more network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]).
Regarding claim 11 as applied to claim 8, Dai as modified by Szilagyi further teaches wherein the identified set of network functions associated with the region for the UE device includes one or more of an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and an evolved packet data gateway (ePDG) (Dai - [0037]).
Regarding claim 12 as applied to claim 18, Dai as modified by Szilagyi further teaches wherein the call trace data comprises signaling messages (read as messages exchanged between functions) (Dai - [0047], [0050]).
Regarding claim 13 as applied to claim 8, Dai as modified by Szilagyi further teaches wherein the region for a user equipment (UE) device is a region in which the UE device is physically located (read as functionality of such components can be co- located or located at disparate physical server systems; certain components of 5G core 139 may be co-located with components of CU 129) (Dai - [0024]).
Regarding claim 14, Dai teaches a non-transitory, computer-readable medium storing instructions that, when executed by an electronic processor, perform a set of functions, the set of functions comprising:
receiving, using a call trace module, a region (read as cloud computing regions 210) (Dai - Figure 2, [0040]-[0041]) for a user equipment (UE) device and a subscriber number for the UE device (read subscriber management components 170; International Mobile Subscriber Identity) (Dai - [0033], [0036], [0056]);
identifying, using the call trace module, a set of the network functions associated with the region for the UE device from a plurality of network functions of a communication network (read as cloud platform drill engine 514 can identify all of the cellular network core NF instances and their respective identifiers within the specified cloud computing region or sub-region) (Dai - Figure 5, [0067]);
establishing, using the call trace module, a call trace for each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
However, Dai fails to teach collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions; storing, using the call trace module, the collected call trace data in a data storage device; and generating, using the call trace module, a report with at least the collect call trace data.
In the related art, Szilagyi teaches collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions in the set of network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]); storing, using the call trace module, the collected call trace data in a data storage device (read as the closed set of calls (i.e. of trace data or call traces 60 representing the calls) are stored in memory 80 or the like used as a call storage from which the closed set calls is transferred to the analysis element of function 30) (Szilagyi – Figure 3, [0083]); and generating, using the call trace module, a report with at least the collect call trace data (read as sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace; a sequence element carries information about the associated part of the call trace that is relevant) (Szilagyi – [0105]).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date to incorporate the teachings of Szilagyi into the teachings of Dai for the purpose of providing a sequence model used for a call sequence generation from trace data or call traces of a call is an ordered list of so-called sequence elements each of which represents one or more messages or events which are identified within the call trace, wherein a sequence element carries information about the associated part of the call trace that is relevant.
Regarding claim 15 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein each network function of the plurality of network functions of the communication network includes one or more pods, and wherein establishing, using the call trace module, a call trace for each network function of the set of network functions further comprises establishing a call trace for at least one pod of each network function in the set of network functions (read as a call trace is to be established at SBC 310 to capture all communication traffic received from CSCF 320) (Dai - Figure 4, [0054]).
Regarding claim 16 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein each network function of the plurality of network functions of the communication network includes one or more pods, and wherein collecting, using the call trace module, only call trace data associated with the subscriber number for the UE device from one or more network functions further comprises collecting only call trace data associated with the subscriber number for the UE device from at least one pod in the one or more network functions (read as first the trace data or call traces 70 representing the individual signaling sets (calls) are filtered so that only those elements of the traces are kept which are relevant for the classification) (Szilagyi – [0078]).
Regarding claim 17 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein the subscriber number is a phone number (read as subscriber's mobile phone) (Dai - Abstract, [0002]).
Regarding claim 18 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein the identified set of network functions associated with the region for the UE device includes one or more of an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and an evolved packet data gateway (ePDG) (Dai - [0037]).
Regarding claim 19 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein the call trace data comprises signaling messages (read as messages exchanged between functions) (Dai - [0047], [0050]).
Regarding claim 20 as applied to claim 14, Dai as modified by Szilagyi further teaches wherein the region for a user equipment (UE) device is a region in which the UE device is physically located (read as functionality of such components can be co- located or located at disparate physical server systems; certain components of 5G core 139 may be co-located with components of CU 129) (Dai - [0024]).
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 APRIL GUZMAN GONZALES whose telephone number is (571)270-1101. The examiner can normally be reached Monday - Friday 8:00 am to 4:00 pm EST. The examiner’s email address is april.guzman@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, Wesley L. Kim can be reached at (571) 272-7867. 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.
/APRIL G GONZALES/ Primary Examiner, Art Unit 2648
Prosecution Insights