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 Arguments
The Petition for Revival filed 5/12/2026 is noted. Applicant’s arguments with respect to claim(s) 1-3, 6-9, and 12 (and corresponding dependent claims 4-5 and 10-11) have been considered but are moot based on new grounds of rejection necessitated by applicant’s amendments.
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.
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.
Claim(s) 1-3, 5-9, 11-15, 17-18, and 20 is/are rejected under 35 U.S.C. 103 as being unpatentable over Yang et al. (US 2022/0377043 A1) hereinafter Yang in view of Wu (US 2021/0127271 A1, made of record as pertinent art in the OA of 5/24/2024) hereinafter Wu.
Regarding claim 1, Yang teaches a method for creating an outer header for an outgoing packet (create an outer header; para. 119), the outgoing packet based on an incoming packet received at a node (forwarding packets / network address translation (NAT); para. 08-09, node of embodiments; para. 162 and Fig. 14), comprising: receiving an outer header creation information element (IE) type at the node (user plane (UP) function instructed (receiving) Information Element (IE) create outer header for IP header modification; para. [72, 119]), including instructions to create an outer header for the outgoing packet (create outer header contains instruction to create outer header; para. 119); creating the outer header for the outgoing packet based on the outer header creation IE type (outer header creation description in form of bitmask, each bit indicates the outer header to be created in the outgoing packet; para. 120-121), wherein the outer header creation IE type instructs creation of the outer header including an Internet protocol (IP) header (create outer header instruction for IP address / IP header; para. [119-121, 133-134], UP function performs IP header modification; para. 79) having a source IP address (replacing original source IP address at IP header; para. 146, modifying IP header of packets in transit across device; para. 53); and sending, from the node, the outgoing packet including the newly created outer header (replacing original source IP address at IP header; para. 146, modifying IP header of packets in transit across device; para. 53).
Yang does not explicitly disclose the outer header creation IE type encoded with at least one source IP address field.
However, in the same field of endeavor, Wu teaches the outer header creation IE type encoded with at least one source IP address field (outer header creation includes source address; para. 196).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to provide the technique of Wu to the system of Yang, where Yang’s network address translation (06-07) along with Wu’s user plane separation (para. 11-12) improves the system by protecting a private network having non-3GPP access from unlawful incursion.
Regarding claim 2, the combination of Yang and Wu discloses the limitation of previous claim 1.
Yang further teaches wherein the outer header creation IE type instructs creation of the outer header including an Internet protocol version 4 (IPv4) header (outer header creation description for creating IPv4 header; para. 119-122) and a source IPv4 address (outer header creation description for instructions for IPv4 address; para. 119-122, replacing original source IP address at IP header; para. 146, modifying IP header of packets in transit across device; para. 53).
Regarding claim 3, the combination of Yang and Wu discloses the limitation of previous claim 1.
Yang further teaches wherein the outer header creation IE type instructs creation of the outer header including an Internet protocol version 6 (IPv6) header (outer header creation description for create IPv6 header; para. 119-122) and a source IPv6 address (outer header creation description for instructions for IPv6 address; para. 119-122, replacing original source IP address at IP header; para. 146, modifying IP header of packets in transit across device; para. 53).
Regarding claim 5, the combination of Yang and Wu discloses the limitation of previous claim 1.
Yang further teaches wherein: an outer header creation description field of the outer header creation IE type includes a bitmask (outer header creation description in form of bitmask; para. 120-121) indicating fields present in the outer header to be created in the outgoing packet (each bit indicates the outer header to be created in the outgoing packet; para. 120-121); and creating the outer header for the outgoing packet based on the outer header creation IE type includes creating the outer header for the outgoing packet based on the bitmask (each bit indicates the outer header to be created in the outgoing packet; para. 120-121, modifying IP header of packets in transit across device; para. 53).
Regarding claim 6, the combination of Yang and Wu discloses the limitation of previous claim 1.
Yang further teaches wherein the incoming packet is a downlink packet received at a Packet Data Network (PDN) Gateway (PGW) or an uplink packet received at the PGW (packets being UL packets by Packet Data Network (PDN) Gateway (PGW); para. 121 and para. 125-126, examiner notes the use of alternative language here, thus, only one of the alternative features need to be shown by reference).
Regarding claim 20, the combination of Yang and Wu discloses the limitation of previous claim 1.
Yang further teaches wherein the node is a Packet Data Network (PDN) Gateway (PGW) (packets being UL packets by PGW; para. 121 and para. 125-126).
Regarding claim 7, the claim is interpreted and rejected for the same reason as set forth in claim 1, including a non-transitory computer-readable medium containing instructions, when executed (processor executing program in memory; para. 255).
Regarding claim 8, the claim is interpreted and rejected for the same reason as set forth in claim 2.
Regarding claim 9, the claim is interpreted and rejected for the same reason as set forth in claim 3.
Regarding claim 11, the claim is interpreted and rejected for the same reason as set forth in claim 5.
Regarding claim 12, the claim is interpreted and rejected for the same reason as set forth in claim 6.
Regarding claim 13, the claim is interpreted and rejected for the same reason as set forth in claim 7, including system (system implementing embodiments; para. 41).
Regarding claim 14, the claim is interpreted and rejected for the same reason as set forth in claim 8.
Regarding claim 15, the claim is interpreted and rejected for the same reason as set forth in claim 9.
Regarding claim 17, the claim is interpreted and rejected for the same reason as set forth in claim 11.
Regarding claim 18, the claim is interpreted and rejected for the same reason as set forth in claim 12.
Claim(s) 4, 10, 16, and 19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Yang in view of Wu, and further in view of Zhu et al. (US 2023/0147272 A1) hereinafter Zhu.
Regarding claim 4, the combination of Yang and Wu discloses the limitation of previous claim 1.
While the combination of Yang and Wu discloses SGW, the combination of Yang and Wu discloses does not explicitly disclose wherein the incoming packet is a downlink packet received at a Serving Gateway (SGW) or an uplink packet received at the SGW.
However, in the same field of endeavor, Zhu teaches wherein the incoming packet is a downlink packet received at a Serving Gateway (SGW) (packet handling at serving gateway (SGW); para. 102, for outer header creation, SGW for downlink (DL) data forwarding; para. [112, 135-142], examiner notes the use of alternative language here, thus, only one of the alternative features need to be shown by reference) or an uplink packet received at the SGW (packet handling at serving gateway (SGW); para. 102, for outer header creation, SGW for uplink (UL) data forwarding; para. 135-142).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to provide the technique of Zhu to the modified system of Yang and Wu, where Yang and Wu’s modified system along with improved forwarding solution for UP (para. 07-08) improves efficiency of system resources.
Regarding claim 19, the combination of Yang and Wu discloses the limitation of previous claim 1.
While the combination of Yang and Wu discloses SGW, the combination of Yang and Wu discloses does not explicitly disclose wherein the node is a Serving Gateway (SGW).
However, in the same field of endeavor, Zhu teaches wherein the node is a Serving Gateway (SGW) (packet handling at SGW; para. 102).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to provide the technique of Zhu to the modified system of Yang and Wu, where Yang and Wu’s modified system along with improved forwarding solution for UP (para. 07-08) improves efficiency of system resources.
Regarding claim 10, the claim is interpreted and rejected for the same reason as set forth in claim 4.
Regarding claim 16, the claim is interpreted and rejected for the same reason as set forth in claim 10.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Muñoz de la Torre Alonso et al. (US 2023/0180311 A1) discloses session identifier handling for co-located user plane gateways.
Jain et al. (US 2018/0206275 A1) discloses a system and method to facilitate stateless serving gateway operations in a network environment.
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 JOSE L PEREZ whose telephone number is (571) 270-7348. The examiner can normally be reached M-F 11 am - 3 pm.
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/uspto-automated-interview-request-air-form.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Michael Thier can be reached at (571) 272-2832. 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.
/JOSE L PEREZ/Examiner, Art Unit 2474
Prosecution Insights