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 .
Summary
This action is in reply to Applicant’s Preliminary Amendment filed on 04/06/2026.
Claims 1-3 and 5-13 are pending.
Claim 4 is canceled.
Claim 13 is added new.
Response to Arguments
Applicant’s arguments filed on 04/06/2026 with respect to claims 1-3 and 5-13 have been considered but they are moot as they are not applicable to the combination of prior arts used in this office action.
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 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.
Claims 1-3, 5-7 and 11-13 are rejected under 35 U.S.C. 103 as being unpatentable over Jo et al. (US 20200128431 A1, of IDS, hereinafter ‘JO’) in view of Parron et al. (US 20190387577 A1, of record, hereinafter ‘PARRON’) and with further in view of STOJANOVSKI et al. (EP 3456085 B1, hereinafter ‘STOJANOVSKI’).
Regarding claim 1, JO teaches a communication method used in a mobile communication system (
Fig. 1, [0003] FIG. 1 is a view schematically illustrating a network structure of an E-UMTS as an exemplary radio communication system. An Evolved Universal Mobile Telecommunications System (E-UMTS)….
[0004] Referring to FIG. 1, the E-UMTS includes a User Equipment (UE), eNode Bs (eNBs), and an Access Gateway (AG) which is located at an end of the network (E-UTRAN)….
Fig. 9, [0081] FIG. 9 is a conceptual diagram for transmitting TCP ACK packet using a special DRB in wireless communication system), the communication method comprising the steps of:
configuring, by a network node (Fig. 1 eNB), a user equipment (Fig. 1 UE) with a first communication path and a second communication path associated with the first communication path as communication paths to be established between the network node and the user equipment (
Fig. 9 S901, [0092] A UE is configured by a network with one or more radio bearer belonging to a PDU session (S901).
[0096] Preferably, when the UE receives configuration information for configuring one or more radio bearer belonging to a PDU session from a network, the UE can receive the TCP ACK DRB configuration information.
[0097] Preferably, the TCP ACK DRB is used for transmitting all TCP ACK packets from all DRBs belonging to the PDU session.
[0098] Preferably, the UE receives a TCP ACK DRB configuration information from the network including at least one i) an indication of a TCP ACK DRB, ii) a PDU session identifier associated with the TCP ACK DRB, iii) priority information of the TCP ACK DRB, or iv) configuration parameters for TCP ACK DRB such as Layer1, Layer2, Layer3 parameters.
[0099] The Indication of the TCP ACK DRB indicates whether the RB is TCP ACK DRB or not.
[0100] The PDU session identifier identifies a PDU session associated with the TCP ACK DRB. In this case, the UE transmits TCP ACKs for all radio bearers belonging to the PDU session identified by the PDU session identifier via the TCP ACK DRB, and for one PDU session, only one TCP ACK DRB is configured, i.e., only one PDU session identifier is associated with the TCP ACK DRB.
[0114] When the UE receives the TCP ACK DRB configuration information indicating that the TCP ACK DRB is a DRB 4, the UE configures that the TCP ACK DRB for the PDU session is DRB 4 according to the received TCP ACK DRB configuration information.);
mapping, by an entity in a predetermined layer of the user equipment, first data belonging to a data flow to the first communication path (
[0060] The main services and functions of SDAP entity include i) Mapping between a QoS flow and a data radio bearer, and ii) Marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.
[0061] At the reception of an SDAP SDU from upper layer for a QoS flow ….. If there is a stored QoS flow to DRB mapping rule for the QoS flow, the SDAP entity may map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule. And the SDAP entity may construct the SDAP PDU and deliver the constructed SDAP PDU to the lower layers.
[0093] A new layer, e.g., SDAP (Service Data Adaptation Protocol layer), is configured per PDU session, which is placed above PDCP entities of the PDU session and in charge of routing a packet to an associated radio bearer, i.e., a PDCP entity of the associated radio bearer. And a PDCP entity and an RLC entity are configured per radio bearer.
[0094] The UE receives a QoS flow to DRB mapping rule from the network which is used for the PDU session, wherein the QoS flow to DRB mapping rule defines a mapping between a QoS flow and a DRB for the PDU session (S903).);
mapping, by the entity to the second communication path, second data belonging to the data flow and being assigned a higher priority than the first data (
[0095] A UE receives TCP ACK DRB configuration information for transmitting TCP ACK packets, wherein the TCP ACK RB is configured for the PDU session (S905). The UE configures the TCP ACK DRB for the PDU session according to the received TCP ACK DRB configuration information.
[0101] The priority information of the TCP ACK DRB is a priority that is to be used for logical channel prioritization procedure in MAC, wherein the priority is as follows: i) the priority is the highest than any other priorities, e.g., 1, regardless of the priority of configured radio bearers; ii) the priority is higher than any other configured radio bearers belonging to the PDU session associated with the TCP ACK DRB, iii) the priority is higher than any other configured data radio bearers belonging to the PDU session associated with the TCP ACK DRB; ); and
transmitting, by the user equipment to the network node, the second data mapped to the second communication path with priority over the first data mapped to the first communication path (
[0101] The priority information of the TCP ACK DRB is a priority that is to be used for logical channel prioritization procedure in MAC, wherein the priority is as follows: i) the priority is the highest than any other priorities, e.g., 1, regardless of the priority of configured radio bearers; ii) the priority is higher than any other configured radio bearers belonging to the PDU session associated with the TCP ACK DRB….
[0102] When the UE receives a packet together with a QoS flow ID identifying the QoS flow of the packet for a PDU session from an upper layer, the UE may perform checking whether the received packet includes a TCP ACK or not only if a TCP ACK DRB is configured for the PDU session (S907).
[0103] If the received packet includes a TCP ACK, the UE generates a PDU including the received packet and delivers the PDU to a lower layer via the TCP ACK DRB (S909).
[0104] Preferably, the new layer of the UE generates a PDU by attaching a QoS flow ID identifying the QoS flow of the TCP ACK to the received packet, and the new layer delivers the generated PDU to a PDCP entity of the TCP ACK DRB.
[0111] The UE transmits the received packet to the network via the radio bearer corresponding to the received packet (S913).
See also Fig. 10, [0113] FIG. 10 is an example for transmitting TCP ACK packet using a special DRB according to embodiments of the present invention.
[0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.
(Construed that TCP ACK DRB having logically a highest priority or a higher priority than priority of other data DRB, a corresponding TCP ACK packet is transmitted using the TCP ACK DRB before a TCP data packet using regular DRB)).
However, assuming arguendo that the claim must be so narrowly construed such that JO does not explicitly disclose transmitting, by the user equipment to the network node, the second data mapped to the second communication path with priority over the first data mapped to the first communication path, and wherein the configuring comprises transmitting, from the network node to the user equipment, an RRC Reconfiguration message comprising information associating the first communication path with the second communication path, then,
in an analogous art, PARRON teaches transmitting, by the user equipment to the network node, the second data mapped to the second communication path with priority over the first data mapped to the first communication path (
[0043] to disclose a process for prioritization of TCP ACKs in transmission of the air interface to reduce the delay of TCP ACK transmissions and minimize the risk of TCP ACK filtering (drop of data). Further, processes are disclosed to detect an ACK and transmit the ACK on a higher priority DRB. In certain embodiments, having a dedicated DRB with higher priority for a transmission of TCP ACKs versus normal data can help to reduce Round Trip Time (RTT) for TCP communication.
[0044] In one embodiment, when a high priority DRB is used for transmission of TCP ACKs (compared to normal data), the logical channel prioritization applied in the UL by the UE will result in TCP ACKs being prioritized over normal data and sent in the UL when the UL grant is not sufficient for both data and the TCP ACKs.).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of prioritized transmission of TCP ACK data over normal data of PARRON to the method for transmitting TCP ACK packet in wireless communication system of JO in order to take the advantage of providing a method for reducing the delay of TCP ACK transmissions and minimize the risk of TCP ACK filtering (drop of data) allowing more consistency in the TCP traffic (PARRON: [0043, 0044]).
JO and PARROR do not explicitly disclose wherein the configuring comprises transmitting, from the network node to the user equipment, an RRC Reconfiguration message comprising information associating the first communication path with the second communication path.
In an analogous art, STOJANOVSKI teaches wherein the configuring comprises transmitting, from the network node to the user equipment, an RRC Reconfiguration message comprising information associating the first communication path with the second communication path (
[0004] In some instances, multiple applications can be concurrently executing on a user equipment (UE), each application having different quality of service (QoS) requirements. …. In order to support multiple QoS requirements, different bearers are established within the long term evolution (LTE) Evolved Packet System (EPS), each being associated with a QoS.
[0023] … Network devices can utilize the QCI for establishing / modifying the EPS bearer between the UE 102 and the NG6 reference point, or equivalent in 4G. The QCI associated with a specific QCI level or value so all packets need to be handled with this specific QCI and sent in the specific pipe or EPS bearer in the network communications.
[0027] …. there can be one or more priority lists of EPS bearer IDs. Thus, when the UE 102 receives an uplink packet of an application running in the UE 102, it can go through the matching process to see if there is any packet filter that corresponds to this packet. If there are multiple such packet filters that match the UL packet, it can process through the priority list of the EPS bearer IDs and selects the EPS bearer ID that is first in the list so that the UE performs the bearer binding.
[0045] …. explicit signalling of QoS information (i.e. Flow Descriptor and associated QoS parameters) can still be utilized, but performed only as needed, such as when a GBR traffic is requested or utilized. The explicit signalling can be performed using an AS layer or procedure only (e.g., via RRC Reconfiguration Request) ….. The linkage between the explicitly signalled QoS information and the associated radio bearer is performed …. with an RB ID signalled as Access Stratum (e.g. RRC) parameter …… also used in the PDCP/RLC/MAC header of the data units), for example.
[0046] The embodiments discussed above can be applied to the LTE-Uu interface, by making the same changes in the PDCP (or RLC or MAC) header, in the RRC Reconfiguration Request message …...).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of explicit RRC signalling of QoS associated with respective RBs of STOJANOVSKI to the method for transmitting TCP ACK packet in wireless communication system using RRC layer controls of radio bearers (RBs) of JO and PARRON in order to take the advantage of providing a method for supporting multiple QoS requirements or priority for multiple applications concurrently executing on a user equipment (UE) (STOJANOVSKI: [0004, 0045]).
Regarding claim 11, JO teaches a user equipment (Fig. 1 UE) used in a mobile communication system (
Fig. 1, [0003] FIG. 1 is a view schematically illustrating a network structure of an E-UMTS as an exemplary radio communication system. An Evolved Universal Mobile Telecommunications System (E-UMTS)….
[0004] Referring to FIG. 1, the E-UMTS includes a User Equipment (UE), eNode Bs (eNBs), and an Access Gateway (AG) which is located at an end of the network (E-UTRAN)….
Fig. 9, [0081] FIG. 9 is a conceptual diagram for transmitting TCP ACK packet using a special DRB in wireless communication system), the user equipment comprising:
a receiver, a controller and a transmitter (
Fig. 11, 0126] The apparatus shown in FIG. 11 can be a user equipment (UE) and/or eNB adapted to perform the above mechanism.
[0127] As shown in FIG. 11, the apparatus may comprises a DSP/microprocessor (110) and RF module (transceiver; 135). The DSP/microprocessor (110) is electrically connected with the transceiver (135) and controls it. The apparatus may further include power management module (105), battery (155), display (115), keypad (120), SIM card (125), memory device (130) ….).
Further, claim 11 with similar features as in claim 1, is also interpreted mutatis mutandis of claim 1 and rejected for the same reason as set forth for claim 1.
Regarding claim 12, JO teaches a network node (Fig. 1 eNB) used in a mobile communication system (
Fig. 1, [0003] FIG. 1 is a view schematically illustrating a network structure of an E-UMTS as an exemplary radio communication system. An Evolved Universal Mobile Telecommunications System (E-UMTS)….
[0004] Referring to FIG. 1, the E-UMTS includes a User Equipment (UE), eNode Bs (eNBs), and an Access Gateway (AG) which is located at an end of the network (E-UTRAN)….
Fig. 9, [0081] FIG. 9 is a conceptual diagram for transmitting TCP ACK packet using a special DRB in wireless communication system), the network node comprising:
a controller, a receiver (
Fig. 11, 0126] The apparatus shown in FIG. 11 can be a user equipment (UE) and/or eNB adapted to perform the above mechanism.
[0127] As shown in FIG. 11, the apparatus may comprises a DSP/microprocessor (110) and RF module (transceiver; 135). The DSP/microprocessor (110) is electrically connected with the transceiver (135) and controls it. The apparatus may further include power management module (105), battery (155), display (115), keypad (120), SIM card (125), memory device (130) ….).
Further, claim 12 with similar features as in claim 1, is also interpreted mutatis mutandis of claim 1 and rejected for the same reason as set forth for claim 1.
Regarding claim 2, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 1, wherein the second data is a Transmission Control Protocol Acknowledgement (TCP Ack) (
[0095] A UE receives TCP ACK DRB configuration information for transmitting TCP ACK packets, wherein the TCP ACK RB is configured for the PDU session (S905)).
Regarding claim 3, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 1, further comprising:
configuring, by the network node, the user equipment with a type of data to be mapped to the second communication path (
[0098] Preferably, the UE receives a TCP ACK DRB configuration information from the network including at least one i) an indication of a TCP ACK DRB, ii) a PDU session identifier associated with the TCP ACK DRB, iii) priority information of the TCP ACK DRB, or iv) configuration parameters for TCP ACK DRB such as Layer1, Layer2, Layer3 parameters.
[0099] The Indication of the TCP ACK DRB indicates whether the RB is TCP ACK DRB or not.
[0100] The PDU session identifier identifies a PDU session associated with the TCP ACK DRB. In this case, the UE transmits TCP ACKs for all radio bearers belonging to the PDU session identified by the PDU session identifier via the TCP ACK DRB, and for one PDU session, only one TCP ACK DRB is configured, i.e., only one PDU session identifier is associated with the TCP ACK DRB), wherein
the mapping to the second communication path comprises mapping the data of the configured type to the second communication path as the second data (
[0103] If the received packet includes a TCP ACK, the UE generates a PDU including the received packet and delivers the PDU to a lower layer via the TCP ACK DRB (S909).).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of prioritized transmission of TCP ACK data over normal data of PARRON to the method f for transmitting TCP ACK packet in wireless communication system of JO in order to take the advantage of providing a method for reducing the delay of TCP ACK transmissions and minimize the risk of TCP ACK filtering (drop of data) allowing more consistency in the TCP traffic (PARRON: [0043, 0044]).
Regarding claim 5, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 1, wherein
the predetermined layer is a Service Data Adaptation Protocol (SDAP) layer, and the data flow is a QoS flow (
[0060] The main services and functions of SDAP entity include i) Mapping between a QoS flow and a data radio bearer, and ii) Marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.
Fig. 10, [0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.),
the first communication path is a Normal Data Radio Bearer (DRB) (
[0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.
(Construed that DRB#2 for QoS flow #2 is the Normal DRB)), and
the second communication path is a Prioritized DRB associated with the Normal DRB (
[0114] When the UE receives the TCP ACK DRB configuration information indicating that the TCP ACK DRB is a DRB 4, the UE configures that the TCP ACK DRB for the PDU session is DRB 4 according to the received TCP ACK DRB configuration information.).
Regarding claim 6, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 5, wherein
the mapping to the first communication path comprises mapping, to the normal DRB, the first data belonging to a plurality of QoS flows (
Fig. 10, [0115] The DRB 4 is used for transmitting all TCP ACK packets from all DRBs belonging to the PDU session.
[0116] According to QoS flow to DRB mapping rule, QoS flow #1 is mapped to DRB1, QoS flow #2 is mapped to DRB2, QoS flow #3 is mapped to DRB3.
[0117] When the UE receives several packets for the PDU session from the upper layer in order as FIG. 10, the new layer (e.g. SDAP layer) checks the received packet includes a TCP ACK or not.
[0119] When the packet B is received from upper layer, the SDAP layer checks the packet B is TCP ACK or not. Since the packet B is not TCP ACK, the SDAP layer delivers a PDU including the packet B to a PDCP entity of the DRB 1 which is mapped to the QoS flow #1. In this case the SDAP PDU includes the packet B and an identifier identifying QoS flow #1.), and
the mapping to the second communication path comprises mapping, to the Prioritized DRB, the second data belonging to at least one QoS flow among the plurality of QoS flows (
[0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.).
Regarding claim 7, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 6, further comprising:
configuring, by the network node, the user equipment with the at least one QoS flow enabling mapping to the Prioritized DRB (
Fig. 9, S903, [0094] The UE receives a QoS flow to DRB mapping rule from the network which is used for the PDU session, wherein the QoS flow to DRB mapping rule defines a mapping between a QoS flow and a DRB for the PDU session (S903).
Fig. 10, [0114] When the UE receives the TCP ACK DRB configuration information indicating that the TCP ACK DRB is a DRB 4, the UE configures that the TCP ACK DRB for the PDU session is DRB 4 according to the received TCP ACK DRB configuration information.
[0115] The DRB 4 is used for transmitting all TCP ACK packets from all DRBs belonging to the PDU session.
[0116] According to QoS flow to DRB mapping rule, QoS flow #1 is mapped to DRB1, QoS flow #2 is mapped to DRB2, QoS flow #3 is mapped to DRB3.).
Regarding claim 13, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 1, wherein the predetermined layer is a Service Data Adaptation Protocol (SDAP) layer, and the entity attaches an SDAP header to an SDAP SDU (Service Data Unit) even when there is no configuration to attach the SDAP header (
Fig. 5, [0059] The user plane protocol stack contains Phy, MAC, RLC, PDCP and SDAP (Service Data Adaptation Protocol) which is newly introduced to support 5G QoS model.
[0060] The main services and functions of SDAP entity include i) Mapping between a QoS flow and a data radio bearer, and ii) Marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.
[0061] At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity may map the SDAP SDU to the default DRB if there is no stored QoS flow to DRB mapping rule for the QoS flow. ).
Claim 8 is rejected under 35 U.S.C. 103 as being unpatentable over Jo et al. (US 20200128431 A1, of IDS, hereinafter ‘JO’) in view of Parron et al. (US 20190387577 A1, of record, hereinafter ‘PARRON’) in view of STOJANOVSKI et al. (EP 3456085 B1, hereinafter ‘STOJANOVSKI’) and with further in view of ESKELINEN; J. (US 20240007899 A1, of record, hereinafter ‘ESKELINEN’).
Regarding claim 8, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 6, wherein
the second data is a TCP Ack (
Fig, 10, [0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.), and
the mapping to the second communication path comprises mapping, to the second communication path, SDAP Protocol Data Unit (PDU) comprising two or more TCP Acks belonging to two or more QoS flows among the plurality of QoS flows (
Fig. 10, DRB#4, [0118] When the packet A is received from upper layer, the SDAP layer checks the packet A is TCP ACK or not. Since the packet A is TCP ACK, the SDAP layer delivers a PDU including the packet A to a PDCP entity of the DRB 4, although the packet A has QoS flow #2 which is mapped to the DRB 2. In this case the SDAP PDU includes the packet A and an identifier identifying QoS flow #2.
[0121] When the packet D is received from upper layer, the SDAP layer checks the packet D is TCP ACK or not. Since the packet D is TCP ACK, the SDAP layer delivers a PDU including the packet D to a PDCP entity of the DRB 4, although the packet D has QoS flow #1 which is mapped to the DRB 1. In this case the SDAP PDU includes the packet D and an identifier identifying QoS flow #1.).
JO, PARRON and STOJANOVSKI do not explicitly disclose one SDAP Protocol Data Unit (PDU) comprising two or more TCP Acks belonging to two or more QoS flows among the plurality of QoS flows.
In an analogous art, ESKELINEN teaches one SDAP Protocol Data Unit (PDU) comprising two or more TCP Acks belonging to two or more QoS flows among the plurality of QoS flows (
[0026] as described more in detail below, including: compression of the TCP ACKs, decompression of the TCP ACKs, a format of the compressed TCP ACKs, transfer or transmission of compressed TCP ACKs over a normal PDCP data protocol data unit (PDU), transfer or transmission of a TCP ACK flow descriptor over a PDCP data PDU when uplink data compression (UDC) is active, and transfer or transmission of compressed TCP ACKs over a SDAP PDU in compressed TCP ACKs over IP or in compressed TCP ACKs over TCP.).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of compressing TCP ACKs and transmitting multiple TCP ACKs over a SDAP PDU of ESKELINEN to the method for transmitting TCP ACK packet in wireless communication system of JO, PARRON and STOJANOVSKI in order to take the advantage of providing a method for solution to reduce TCP ACK rate in mobile communications (ESKELINEN: [0006,0026]).
Claims 9-10 are is rejected under 35 U.S.C. 103 as being unpatentable over Jo et al. (US 20200128431 A1, of IDS, hereinafter ‘JO’) in view of Parron et al. (US 20190387577 A1, of record, hereinafter ‘PARRON’) in view of STOJANOVSKI et al. (EP 3456085 B1, hereinafter ‘STOJANOVSKI’) and with further in view of Kumar et al. (US 20200153594 A1, of record, hereinafter ‘KUMAR’).
Regarding claim 9, JO, in view of PARRON and STOJANOVSKI, teaches the communication method according to claim 1.
JO, PARRON and STOJANOVSKI do not explicitly disclose wherein
the predetermined layer is a Packet Data Convergence Protocol (PDCP) layer, and the first communication path is a Normal leg of a split bearer, and the second communication path is a Prioritized-leg of the split bearer
In an analogous art, KUMAR teaches wherein
the predetermined layer is a Packet Data Convergence Protocol (PDCP) layer, and the first communication path is a Normal leg of a split bearer, and the second communication path is a Prioritized-leg of the split bearer (
[0005] User Equipment (UE) for transmission of one or more Transport Control Protocol (TCP) Acknowledgement (ACK) packets of a bearer service. The method includes ordering the one or more TCP ACK packets in a first queue and one or more non-TCP ACK packets of the bearer service in a second queue, the first queue having a higher priority than the second queue, and allocating a plurality of Sequence Numbers (SN) in at least one of a Packet Data Convergence Protocol (PDCP) SN space or a Radio Link Control (RLC) SN space to the one or more TCP ACK packets and the one or more non-TCP ACK packets based on the priority of the first queue and the priority of the second queue.).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of transmission of tcp ack packets of KUMAR to the method for transmitting TCP ACK packet in wireless communication system of JO, PARRON and STOJANOVSKI in order to take the advantage of providing a method for prioritizing transmission of TCP ACK packets and increasing reliability of the transmission of the TCP ACK packets (KUMAR: [0002]).
Regarding claim 10, JO, in view of PARRON, STOJANOVSKI and KUMAR, teaches the communication method according to claim 9.
JO, PARRON and STOJANOVSKI do not explicitly disclose wherein the configuring comprises
configuring the user equipment with the split bearer.
KUMAR teaches wherein the configuring comprises
configuring the user equipment with the split bearer (
[0005] User Equipment (UE) for transmission of one or more Transport Control Protocol (TCP) Acknowledgement (ACK) packets of a bearer service. The method includes ordering the one or more TCP ACK packets in a first queue and one or more non-TCP ACK packets of the bearer service in a second queue, the first queue having a higher priority than the second queue…).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of transmission of tcp ack packets of KUMAR to the method for transmitting TCP ACK packet in wireless communication system of JO, PARRON and STOJANOVSKI in order to take the advantage of providing a method for prioritizing transmission of TCP ACK packets and increasing reliability of the transmission of the TCP ACK packets (KUMAR: [0002]).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Yu et al. (US 20210288747 A1), describing COMMUNICATION METHOD AND COMMUNICATIONS APPARATUS
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 SHAH M RAHMAN whose telephone number is (571)272-8951. The examiner can normally be reached 9:30AM-5:30PM PST.
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, UN C CHO can be reached at 571-272-7919. 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.
/SHAH M RAHMAN/Primary Examiner, Art Unit 2413
Prosecution Insights