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 .
DETAILED ACTION
This office action is in response to the amendments filed on 01/14/2026.
Claims 1-3, 5, 8-10, 12, 16-18, 20-23 and 25 are currently pending.
Claims 1-3, 5, 8-10, 12, 16-18, 20-23 and 25 are rejected.
Claims 1, 8, 16 and 21 are independent claims.
Response to Amendment
Claim Rejections - 35 USC § 103
5. 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 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.
6. 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 of this title, 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.
7. The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under pre-AIA 35 U.S.C. 103(a) 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.
8. Claims 1-3, 5, 8-10, 12, 16-18, 20-23 and 25 are rejected under 35 U.S.C. 103 as being unpatentable over Kyungmin Park et al. (US 2023/0087615 A1 based on provisional application No. 63/083,026 filed on Sep. 24, 2020), hereinafter Park, in view of Philippe GODIN et al. (US 2024/0023186 A1), hereinafter GODIN.
For claim 1, Park teaches a method performed by a distributed unit (DU) of base station in a wireless communication system, the method comprising:
receiving, from a user equipment (UE) in an inactive mode, a radio resource control (RRC) resume request and uplink data for small data transmission (SDT) (Park, Fig. 24 teaches the gNB-DU receives RRC resume request and UL data. Since the UE sends the RRC resume request, the UE is in an inactive mode. See also paragraphs 261-290.);
transferring, to a central unit-control plane (CU-CP) of base station, a first message including an indication associated with the SDT (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request. In other words, the gNB-DU transfers to the gNB-CU-CP, a first message including information indicating that the UE is accessing for small data transmission (SDT). See also paragraphs 261-290.);
receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) (Park, Fig. 24 teaches the gNB-DU receives UE context setup request with UL TEID(s) from the gNB-CU-CP. In other words, the UL TEID is the information on the uplink endpoint, the UL TEID is also the information on the DRB and the UL TEID is also the second message. Therefore, Park teaches “receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID)”.);
in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID) (Park, Fig. 24 teaches the gNB-DU transfers UE context setup response with DL TEID(s) to gNB-CU-CP. In other words, the DL TEID is the information on the downlink endpoint, the DL TEID is also the third message. Therefore, Park teaches “in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.); and
forwarding, to a central unit-user plane (CU-UP) of base station, the uplink data for SDT over the uplink tunnel (Park, Fig. 24 and paragraph 248 teach the gNB-DU forwards the UL data to the gNB-CU-UP from the UE)
GODIN further teaches DU buffers UL data received from UE before forwarding the UL data to CU-UP (GODIN, Fig. 10 and paragraph 145-147 teaches the DU receives first UL data and buffers the first UL data before forwarding it to the CU-UP.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park with DU buffers UL data received from UE before forwarding the UL data to CU-UP taught in GODIN. Because both Park and GODIN teach SDT between UE, DU and CU, GODIN explicitly teaches the DU buffered the UL data received from the UE before forwarding the UL data to the CU-CP.
For claim 2, Park and GODIN further teach the method of claim 1, wherein the uplink data for SDT is delivered to a user plane function (UPF) via the CU-UP of base station (Park, Fig. 26 and paragraph 283 teach the CU-UP may receive the uplink data and/or the subsequent uplink data associated with the SDT procedure from the wireless device via the base station distributed unit. The CU-UP may send the uplink data and/or the subsequent uplink data to at least one of: a user plane function (UPF).).
For claim 3, Park and GODIN further teach the method of claim 1, wherein the first message further includes the RRC resume request (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request.).
For claim 5, Park and GODIN further teach the method of claim 1, further comprising: receiving, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF) (Park, Fig. 24 teaches the gNB-DU transfers to the gNB-CU-CP, UE context setup response with DL TEID(s), in response to the UE context setup request with UL TEID(s) received from the gNB-CU-CP. Park, Fig. 28 teaches the gNB-DU receives, from the gNB-CU-UP, DL data (with end marker). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park to have the method of claim 1, further comprising: receiving, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF).).
For claim 8, Park teaches a distributed unit (DU) of base station (Park, Fig. 15, item 1504) in a wireless communication system, the DU of base station comprising:
a transceiver (Park, Fig. 15, items 1510, 1512); and
a controller (Park, Fig. 15, item 1508) coupled with the transceiver and configured to:
receive, from a user equipment (UE) in an inactive mode, a radio resource control (RRC) resume request and uplink data for small data transmission (SDT) (Park, Fig. 24 teaches the gNB-DU receives RRC resume request and UL data. Since the UE sends the RRC resume request, the UE is in an inactive mode. See also paragraphs 261-290.);
transfer, to a central unit-control plane (CU-CP) of base station, a first message including an indication associated with the SDT (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request. In other words, the gNB-DU transfers to the gNB-CU-CP, a first message including information indicating that the UE is accessing for small data transmission (SDT). See also paragraphs 261-290.);
receive, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) (Park, Fig. 24 teaches the gNB-DU receives UE context setup request with UL TEID(s) from the gNB-CU-CP. In other words, the UL TEID is the information on the uplink endpoint, the UL TEID is also the information on the DRB and the UL TEID is also the second message. Therefore, Park teaches “receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID)”.);
in response to the second message, transfer, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID) (Park, Fig. 24 teaches the gNB-DU transfers UE context setup response with DL TEID(s) to gNB-CU-CP. In other words, the DL TEID is the information on the downlink endpoint, the DL TEID is also the third message. Therefore, Park teaches “in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.); and
forwarding, to a central unit-user plane (CU-UP) of base station, the uplink data for SDT over the uplink tunnel (Park, Fig. 24 and paragraph 248 teach the gNB-DU forwards the UL data to the gNB-CU-UP from the UE)
GODIN further teaches DU buffers UL data received from UE before forwarding the UL data to CU-UP (GODIN, Fig. 10 and paragraph 145-147 teaches the DU receives first UL data and buffers the first UL data before forwarding it to the CU-UP.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park with DU buffers UL data received from UE before forwarding the UL data to CU-UP taught in GODIN. Because both Park and GODIN teach SDT between UE, DU and CU, GODIN explicitly teaches the DU buffered the UL data received from the UE before forwarding the UL data to the CU-CP.
For claim 9, Park and GODIN further teach the DU of base station of claim 8, wherein the uplink data for SDT is delivered to a user plane function (UPF) via the CU-UP of base station (Park, Fig. 26 and paragraph 283 teach the CU-UP may receive the uplink data and/or the subsequent uplink data associated with the SDT procedure from the wireless device via the base station distributed unit. The CU-UP may send the uplink data and/or the subsequent uplink data to at least one of: a user plane function (UPF).).
For claim 10, Park and GODIN further teach the first DU of base station of claim 8, wherein the first message further includes the RRC resume request (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request.).
For claim 12, Park and GODIN further teach the DU of base station of claim 8, wherein the controller is configured to receive, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF) (Park, Fig. 24 teaches the gNB-DU transfers to the gNB-CU-CP, UE context setup response with DL TEID(s), in response to the UE context setup request with UL TEID(s) received from the gNB-CU-CP. Park, Fig. 28 teaches the gNB-DU receives, from the gNB-CU-UP, DL data (with end marker). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park to have the method of claim 1, further comprising: receiving, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF).).
For claim 16, Park teaches a method performed by a central unit-control plane (CU-CP) of base station in a wireless communication system, the method comprising:
receiving, from a distributed unit (DU) of base station, a first message including an indication associated with small data transmission (SDT) (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request. In other words, the gNB-DU transfers to the gNB-CU-CP, a first message including information indicating that the UE is accessing for small data transmission (SDT). Since the UE sends the RRC resume request, the UE is in an inactive mode. See also paragraphs 261-290.)); and
transferring, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station (Park, Fig. 24 teaches the gNB-DU receives UE context setup request with UL TEID(s) from the gNB-CU-CP. In other words, the UL TEID is the information on the uplink endpoint, the UL TEID is also the information on the DRB and the UL TEID is also the second message. Therefore, Park teaches “transferring, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station”.);
in response to the second message, receiving, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID) (Park, Fig. 24 teaches the gNB-DU transfers UE context setup response with DL TEID(s) to gNB-CU-CP. In other words, the DL TEID is the information on the downlink endpoint, the DL TEID is also the third message. Therefore, Park teaches “in response to the second message, receiving, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.);
GODIN further teaches receiving, from a distributed unit (DU) of base station, a first message including information indicating that a user equipment (UE) in an inactive mode is accessing for small data transmission (SDT) (GODIN, Fig. 10 step 1001 and paragraph 145-147 teach starting SDT procedure, the DU receives RRCResumeRequest and first UL data from the UE in RRC inactive mode.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park with GODIN to have receiving, from a distributed unit (DU) of base station, a first message including an indication associated with small data transmission (SDT); and transferring, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station; and
in response to the second message, receiving, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) and the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID). Because both Park and GODIN teach SDT between UE, DU and CU, GODIN explicitly teaches receiving, from a first base station operating as a distributed unit (DU), a first message including information indicating that a user equipment (UE) in an inactive mode is accessing for small data transmission (SDT).
For claim 17, Park and GODIN further teach the method of claim 16, wherein the uplink data for SDT is delivered to a user plane function (UPF) via the CU-UP of base station (Park, Fig. 26 and paragraph 283 teach the CU-UP may receive the uplink data and/or the subsequent uplink data associated with the SDT procedure from the wireless device via the base station distributed unit. The CU-UP may send the uplink data and/or the subsequent uplink data to at least one of: a user plane function (UPF).).
For claim 18, Park and GODIN further teach the method of claim 16, wherein the first message further includes the RRC resume request (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request.).
For claim 20, Park and GODIN further teach the method of claim 16, wherein the downlink tunnel is associated with forwarding the downlink data to the DU of base station, the downlink data being forwarded from a user plane function (UPF) (Park, Fig. 24 teaches the gNB-DU transfers to the gNB-CU-CP, UE context setup response with DL TEID(s), in response to the UE context setup request with UL TEID(s) received from the gNB-CU-CP. Park, Fig. 28 teaches the gNB-DU receives, from the gNB-CU-UP, DL data (with end marker). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park to have the method of claim 1, further comprising: receiving, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF).).
For claim 21, Park teaches central unit- control plane (CU-CP) of base station in a wireless communication system (Park, Fig. 15 item 1504), the CU-CP of base station comprising:
a transceiver (Park, Fig. 15 items 1510, 1512); and
a controller (Park, Fig. 15 item 1508) coupled with the transceiver and configured to:
receive, from a distributed unit (DU) of base station, a first message including an indication associated with small data transmission (SDT) (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request. In other words, the gNB-DU transfers to the gNB-CU-CP, a first message including information indicating that the UE is accessing for small data transmission (SDT). Since the UE sends the RRC resume request, the UE is in an inactive mode. See also paragraphs 261-290.)); and
transfer, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station (Park, Fig. 24 teaches the gNB-DU receives UE context setup request with UL TEID(s) from the gNB-CU-CP. In other words, the UL TEID is the information on the uplink endpoint, the UL TEID is also the information on the DRB and the UL TEID is also the second message. Therefore, Park teaches “transferring, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station”.);
in response to the second message, receive, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID) (Park, Fig. 24 teaches the gNB-DU transfers UE context setup response with DL TEID(s) to gNB-CU-CP. In other words, the DL TEID is the information on the downlink endpoint, the DL TEID is also the third message. Therefore, Park teaches “in response to the second message, receiving, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.);
GODIN further teaches receiving, from a distributed unit (DU) of base station, a first message including information indicating that a user equipment (UE) in an inactive mode is accessing for small data transmission (SDT) (GODIN, Fig. 10 step 1001 and paragraph 145-147 teach starting SDT procedure, the DU receives RRCResumeRequest and first UL data from the UE in RRC inactive mode.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park with GODIN to have receiving, from a distributed unit (DU) of base station, a first message including an indication associated with small data transmission (SDT); and transferring, to the DU of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for uplink data for SDT, wherein the uplink tunnel is associated with forwarding the uplink data for SDT, transmitted with a radio resource control (RRC) resume request from a user equipment (UE), to a central unit-user plane (CU-UP) of base station; and
in response to the second message, receiving, from the DU of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) and the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID). Because both Park and GODIN teach SDT between UE, DU and CU, GODIN explicitly teaches receiving, from a first base station operating as a distributed unit (DU), a first message including information indicating that a user equipment (UE) in an inactive mode is accessing for small data transmission (SDT).
For claim 22, Park and GODIN further teach the CU-CP of base station of claim 21, wherein the uplink data for SDT is delivered to a user plane function (UPF) via the CU- UP of base station (Park, Fig. 26 and paragraph 283 teach the CU-UP may receive the uplink data and/or the subsequent uplink data associated with the SDT procedure from the wireless device via the base station distributed unit. The CU-UP may send the uplink data and/or the subsequent uplink data to at least one of: a user plane function (UPF).).
For claim 23, Park and GODIN further teach the CU-CP of base station of claim 21, wherein the first message further includes the RRC resume request (Park, Fig. 24 teaches the gNB-DU sends initial UL RRC message transfer message and/or RRC resume request.).
For claim 25, Park and GODIN further teach the CU-CP of base station of claim 21, wherein the downlink tunnel is associated with forwarding the downlink data to the DU of base station, the downlink data being forwarded from a user plane function (UPF) (Park, Fig. 24 teaches the gNB-DU transfers to the gNB-CU-CP, UE context setup response with DL TEID(s), in response to the UE context setup request with UL TEID(s) received from the gNB-CU-CP. Park, Fig. 28 teaches the gNB-DU receives, from the gNB-CU-UP, DL data (with end marker). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method taught in Park to have the method of claim 1, further comprising: receiving, from the CU-UP of base station, the downlink data over the downlink tunnel, the downlink data being forwarded from a user plane function (UPF).).
Response to Arguments
9. Applicant's arguments (remarks pages 8-9) filed 01/14/2026 have been fully considered but they are not persuasive.
For claim 1, Applicant argues that Park and Godin do not teach the following
limitations (Remarks, pages 7-9):
receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT;
in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data: and
forwarding, to a central unit-user plane (CU-UP) of base station, the uplink data for SDT over the uplink tunnel,
wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) and the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID).
In response, Examiner respectfully disagrees. Examiner points to the detailed
rejection below, which includes added explanations which address all of the Applicant’s
arguments.
Claim 1 recites that the second message includes information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT; wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID). So, the UL TEID is the information on the uplink endpoint of the uplink tunnel, the UL TEID is also the information on the DRB, the UL TEID is also the second message. Therefore, since Park (Fig. 24) teaches the gNB-DU receives UE context setup request with UL TEID(s) from the gNB-CU-CP, Park teaches “receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT; wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID)”.
Claim 1 further recites “in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data; wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”. So, the DL TEID is the information on the downlink endpoint, the DL TEID is also the third message. Therefore, since Park (Fig. 24) teaches the gNB-DU transfers UE context setup response with DL TEID(s) to gNB-CU-CP, Park teaches “in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data; wherein the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.
Park (Fig. 24 and paragraph 248) teaches the gNB-DU forwards the UL data to the gNB-CU-UP from the UE. In other words, Park teaches “forwarding, to a central unit-user plane (CU-UP) of base station, the uplink data for SDT over the uplink tunnel”.
Therefore, Park and Godin teach “receiving, from the CU-CP of base station, a second message including information on a data radio bearer (DRB), the information on the DRB including information on an uplink endpoint of an uplink tunnel for the uplink data for SDT; in response to the second message, transferring, to the CU-CP of base station, a third message including information on a downlink endpoint of a downlink tunnel for downlink data: and forwarding, to a central unit-user plane (CU-UP) of base station, the uplink data for SDT over the uplink tunnel, wherein the information on the uplink endpoint is an uplink tunnel endpoint identifier (UL TEID) and the information on the downlink endpoint is a downlink tunnel endpoint identifier (DL TEID)”.
Conclusion
10. THIS ACTION IS MADE FINAL. 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.
11. Any inquiry concerning this communication or earlier communications from the examiner should be directed to WILL W LIN whose telephone number is (571)272-8749. The examiner can normally be reached M-F 8:00-5:00.
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, Charles Jiang can be reached at 571-270-7191. 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.
/WILL W LIN/ Primary Examiner, Art Unit 2412
Prosecution Insights