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
This action is responsive to an amendment filed on 08/12/2025. Claims 1, 7, and 13 have been amended. Claims 19 and 20 have been added. Claims 1-20 are pending.
Response to Arguments
Applicant’s arguments, see Applicant Arguments/Remarks, filed on 08/12/2025, with respect to the rejection of the pending claims under 35 U.S.C. §103 have been fully considered.
Applicant argues that Applicant argues that UE components of Sharma do not disclose "a protocol fusion engine coupled to a processor at the edge node of the wireless access network". …a UE is not an edge node. …If the UE of Sharma includes the protocol fusion engine, then the UE would predict and analyze network behavior and make adjustments to the wireless access network to provide better performance of the wireless access network. (Arg./Rem. Page 2)
Since, the amended limitation, “wherein the protocol fusion engine when executed by the processor.…for a user across one or more access methods.”, has altered the scope of the claims, therefore, in current rejection, Examiner relies on Svennebring to teach the amended limitations, see the current rejection, infra.
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.
Claims 1-4, 7-10, 13-16 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over US 2019/0319868 (Svennebring et al.) in view of US 2020/0196199 (Sharma et al.).
Regarding Claim 1, Svennebring teaches a wireless access network comprising: a converged data plane at an edge node of the wireless access network, with multiple radio access technology (RAT) integration ([¶ 0085], Multi-access Edge Computing (MEC) architecture may be access-agnostic …MEC enables implementation of MEC applications that run on top of a Virtualization Infrastructure (VI), which is located in or close to the network edge. [¶ 0087], Each of the VIs includes a respective data plane (DP) that executes respective traffic rules, and routes the traffic among applications, MEC services, DNS server/proxy, 3GPP network, local networks, and external networks. The MEC DP may be connected with the RAN nodes and Core Network (CN), and/or may be connected with an Access Point (AP) via a wider network, such as the internet, an enterprise network, or the like); and a protocol fusion engine coupled to a processor at the edge node of the wireless access network ([¶ 0011], Svennebring discloses wireless communications, and in particular, technologies for Link Quality Prediction (LQP) or Link Performance Prediction (LPP). [¶ 0040], various aspects of the LPP embodiments may be performed by …one or more edge compute nodes [¶ 0044], the LPP layer may implement a data fusion engine (also referred to as an “LPP engine”). [¶¶ 0065-0067] FIG. 3 illustrates an example of infrastructure equipment 300. The infrastructure equipment 300 may be implemented as a base station, radio head, access network node, edge compute nodes, and/or any other element/device. The system 300 includes application circuitry 305… Application circuitry 305 includes circuitry such as, but not limited to one or more processors (or processor cores)); wherein the protocol fusion engine when executed by the processor uses a shared pool of information about at least one of the wireless access network or a core network collected across a 4G RAT and a 5G RAT to predict and analyze network behavior and make adjustments to the wireless access network to provide better performance of the wireless access network for a user across one or more access methods ([¶ 0011], Svennebring teaches a wireless communications, and in particular, technologies for Link Quality Prediction (LQP) or Link Performance Prediction (LPP). LQP/LPP to improve wireless network performance by predicting future network behaviors/metrics and making applications, user equipment (UE), and/or network infrastructure more aware of these predicted network behaviors/metrics. The LPP technology uses machine learning (ML) techniques and a rich set of historical and real-time data feeds to dynamically predict the quality and/or performance of any given radio link and optimize application level behaviors. This allows the applications/UEs/infrastructure to make operational decisions. The LPP technology can also be used for other network planning and management tasks to further improve network performance and reduce operating costs. [¶ 0040], various aspects of the LPP embodiments may be performed by …one or more edge compute nodes. [¶ 0042], The LPPS predicts how network performance changes over time with a relatively high degree of confidence. For example, the LPPS is capable of predicting link performance in time and space, which allows applications, UEs, and/or network infrastructure able to shift delay tolerant traffic in time and/or space in order to smooth out peak demand and improve overall network resource utilization. [¶ 0044], the LPP layer may implement a data fusion engine (also referred to as an “LPP engine”). [¶¶ 0046-0047] one of the layers is responsible for collecting data from one or more UEs and/or NANs, which may be processed by that layer and provided to other layers for determining their respective predicted performance metrics. …The LPP layer obtains the predicted performance metrics from the prediction layers and fuses the predicted performance metrics together to obtain an LPP for an LPPS consumer. The LPP layer may include any suitable technology to fuse the predicted performance metrics provided by the prediction layers. Data fusion is a process of integrating and/or combining data collected from multiple sources at different spatial and temporal scales in order to make inferences about that data. [¶ 0049], the LPP layer is configured to perform Multi-Cell Multi-Layer (MCML) data fusion techniques. …the LPP layer takes data from one or more prediction layers and combines that data with data from one or more other prediction layers to derive the link performance prediction for corresponding LPPS consumers. In one MCML example, the LPP layer may take an output from a cell transition prediction layer, which is in the form of expected cells a UE will visit, and pairs that output with outputs provided by a cell load prediction layer to predict a performance of individual cells based on mobility of the UE. [¶ 0025], the access networks provide network connectivity to the end-user devices via respective NANs. The access networks may be Radio Access Networks (RANs) such as an NG RAN or a 5G RAN for a RAN that operates in a 5G/NR cellular network, an E-UTRAN for a RAN that operates in an LTE or 4G cellular network).
Svennebring does not explicitly teach, however, Sharma teaches a radio access technology (RAT) control plane with functionality supporting a 4G control plane and a 5G control plane ([¶ 0001], Sharma discloses an inter-network switching for 4G-5G networks and more particularly manage data and control plane issues in a 4G-5G network switching. [¶ 0004], the terminal basically is connected to the 4G network to operate the communication service, and connects to the 5G network as required according to the control of the 4G NW. …the control plane uses 4G and the user plane can use both 4G and 5G simultaneously).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to incorporate Sharma’s control plane functionality for 4G-5G network switching to the teachings of Svennebring, because such incorporation would have provided the ability to manage both 4G and 5G connections from a unified control plane ensures seamless handovers as users move between areas with different network coverages.
Regarding Claim 2, Svennebring teaches the wireless access network of claim 1 wherein the wireless access network provides network slicing across technologies ([¶ 0034] The Network Access nodes (NAN)s are communicatively coupled to Core Network (CN). The CN may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, a 5G core (5GC), or some other type of CN. The CN may comprise a plurality of network elements, which are configured to offer various data and telecommunications services to customers/subscribers who are connected to the CN via a RAN. Network Functions Virtualization (NFV) may be utilized to virtualize any or all of the network node functions. A logical instantiation of the CN may be referred to as a network slice, and a logical instantiation of a portion of the CN may be referred to as a network sub-slice).
Regarding Claim 3, Svennebring does not explicitly teach, however, Sharma teaches the wireless access network of claim 1 wherein the wireless access network provides cross- technology interoperability ([¶ 0001], inter-network switching for 4G-5G networks and manage data and control plane issues in a 4G-5G network switching).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to incorporate Sharma’s functionality for 4G-5G network switching to the teachings of Svennebring, because such incorporation would have provided the ability to manage both 4G and 5G connections from a unified control plane ensures seamless handovers as users move between areas with different network coverages.
Regarding Claim 4, Svennebring teaches the wireless access network of claim 1 wherein the wireless access network provides seamless quality of experience (QoE) regardless of an access method ([¶ 0057] The LPP notifications may also be used by network operators and service providers to improve Quality of Service (QoS) and/or Quality of Experience (QoE), which are traditionally associated with network performance metrics. Static network performance metrics only provide a partial, snapshot view of the QoS and/or QoE. Using the LPP notifications, network operators and service providers can adjust traffic routes, mode of operation, and/or other parameters to optimize QoS and QoE since they will have advance warning regarding any significant changes in expected network performance. The LPPS itself may be an abstraction layer between service providers and the underlying mobile access network giving an abstracted view of the access network link quality, which allows service providers and/or application developers to make proactive decisions to improve QoS/QoE).
Regarding Claims 7-10, the claimed limitations are identical and/or equivalent in scope to Claims 1-4, therefore, Claims 7-10 are rejected under the same rationale as claims 1-4.
Regarding Claim 13, the claim limitations are identical and/or equivalent in scope to claim 1, therefore, rejected under the same rationale as claim 1. Svennebring further teaches a non-transitory computer-readable medium containing instructions (Fig. 5, ¶ 0124, 0133), as claimed in claim 13.
Regarding Claims 14-16, the claimed limitations are identical and/or equivalent in scope to Claims 2-4, therefore, Claims 14-16 are rejected under the same rationale as claims 2-4.
Regarding Claim 19, Svennebring teaches the wireless access network of claim 1, wherein the wireless access network includes the edge node ([Fig. 1, ¶ 0015] FIG. 1, illustrates an example edge computing environment 100, specifically illustrates the different layers of communication occurring within the environment 100…access node layer 130 (or “edge node layer 130”) comprising a plurality of network access nodes (NANs) 131, 132, and 133 and a plurality of edge compute nodes 136a-c within an edge computing system 135).
Claims 5, 11 and 17 are rejected under 35 U.S.C. 103 as being unpatentable over Svennebring in view of Sharma, and further in view of US 2019/0166634 (Ni et al.).
Regarding Claim 5, Svennebring in view of Sharma do not explicitly teach, however, Ni teaches the wireless access network system of claim 1 provides per user granular control at one or more of a control plane and a data plane ([¶ 0194], a process of establishing a service packet forwarding path between the second base station and the second forwarding plane network element and a service packet forwarding path between the second service network element and the second forwarding plane network element. It should be noted that, a granularity of the service packet forwarding path is per user. [¶ 0210], the path between the second base station and the second forwarding plane network element and the path between the second forwarding plane network element and the second service network element are IP in IP tunnels. a granularity of the tunnel between the forwarding plane network element and the service network element is per user.
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to incorporate Ni with Svennebring and Sharma in order to provide a granularity of the service packet forwarding path per user. The combination would have allowed for a system to provide an end-to-end service packet routing [Ni, Abstract]
Regarding Claims 11 and 17, the claimed limitations are identical and/or equivalent in scope to claim 5, therefore, claims 11 and 17 are rejected under the same rationale as claim 5.
Claims 6, 12 and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Svennebring in view of Sharma, and further in view of US 2021/0282082 (Mildh et al.).
Regarding Claim 6, Svennebring in view of Sharma do not explicitly teach, however, Mildh teaches the wireless network system of claim 1 provides per session granular control at one or more of a control plane and a data plane ([¶ 0144] The control plane configures user-plane (UP) functions to provide the traffic handling functionality needed for a session. One or multiple UP functions per session can be activated and configured by the control-plane as needed for a given user-plane scenario).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to incorporate Mildh with Svennebring and Sharma, in order to activate One or multiple UP functions per session, configured by a control-plane. The combination would have allowed for a system to support low latency services [Mildh, ¶ 0145].
Regarding Claims 12 and 18, the claimed limitations are identical and/or equivalent in scope to claim 6, therefore, claims 12 and 18 are rejected under the same rationale as claim 6.
Claim 20 is rejected under 35 U.S.C. 103 as being unpatentable over Svennebring in view of Sharma, and further in view of US 2018/0192131 (Epstein et al.).
Regarding Claim 20, although, Svennebring teaches the edge servers may be deployed at the edge of Core Network (CN), however, Svennebring in view of Sharma do not explicitly teach, but Epstein teaches the wireless access network of claim 1, wherein the core network includes the edge node ([¶0032] As shown in FIG. 2, in some implementations, the core network 240 includes an edge node 235 that provides an interface for data communication external to the core network 240.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to incorporate Epstein’s teachings of includes edge node with core network to the combined teachings of Svennebring and Sharma, because such incorporation would have allowed for a system to reduce latency significantly.
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 MOHAMMAD YOUSUF A MIAN whose telephone number is (571)272-9206. The examiner can normally be reached Monday-Friday 9am-5:30pm.
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, ARIO ETIENNE can be reached at 571-272-4001. 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.
/MOHAMMAD YOUSUF A. MIAN/ Examiner, Art Unit 2457
/ARIO ETIENNE/ Supervisory Patent Examiner, Art Unit 2457