DETAILED ACTION
The office action is in response to the amendment filed on July 20, 2026 after RCE.
The RCE application was received on Feb. 10, 2026.
Claims 16-28 are pending in this application.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on April 17, 2023 and May 6, 2026 have been considered by the examiner.
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
Applicant’s Amendments and Arguments filed 07/20/2026 have been considered for examination. Claims 16-28 are pending in the instant application.
With regard to the 102/103 rejections, Applicant’s arguments filed 07/20/2026 (see pages 6-11 of Remarks) in view of the amendments have been fully considered but are not persuasive at least in view of the reasons set forth below. Further, Examiner notes that Applicant’s amendments necessitated the new ground(s) of rejection presented in the instant Office Action.
Regarding claims 16, 20, 23, and 26, Applicant argued:
In the argument, During the above-identified interview, the Examiner indicated that amending independent Claims 16, 20, 23, and 26 to recite "operating in evolved-universal terrestrial radio access (EUTRA)-new radio (NR) dual connectivity (EN-DC) or NR-dual connectivity (NR-DC)" would distinguish these claims over the combination Centonza and Teyeb.
In response to Applicant’s argument, Examiner respectfully disagrees.
As mentioned in the argument, Applicant and Examiner, in the interview, discuss about applying the proposed method of Application for dual connectivity and Applicant argued in the interview that Teyeb discloses about only NR-DC (dual connectivity) and does not disclose about EN-DC, since the F1-C transfer path information is discussed based on the art of Teyeb during an interview. Thus, Examiner said, if EN-DC is included in the following amendments (current amendments for now), Examiner will be further searching and considering the point.
However, during this examination, regarding the amended part, recited as “a method performed by a central unit (CU) of a first base station operating in evolved-universal terrestrial radio access CE-UTRA)-new radio (NR) dual connectivity (EN-DC) or NR-dual connectivity (NR-DC) in a communication system,” Examiner recognizes that Centonza, in Paragraphs [0096], [0105], [0108]-[0110], and [0123], teaches that for EN-DC, NGEN-DC (NG-RAN E-UTRA-NR DC), NE-DC (NR-E-UTRA DC), or MR (Multi-Radio)-DC (NR-DC is one of MR-DC) operation, communication between CU and DU is described based on the method of exchanging messages such as UE CONTEXT MODIFICATION REQUEST message and UE CONTEXT MODIFICATION RESPONSE message. Therefore, a method is performed by a CU of the first base station (gNB) (gNB-CU in the art) in a communication system. Namely, gNB-CU (the CU of the first base station (gNB)) and gNB-DU (the DU of the first base station (gNB)) communicate with each other by exchanging messages.
Further, as shown in the previous office action, the rest of the claim 16 was already disclosed by combination of Centonza and Teyeb.
Therefore, by the reasoning in the above, the amended claim 16 is clearly disclosed by combination of Centonza and Teyeb.
Further, by the similar reasoning, the amended claims 20, 23, and 26 are disclosed by combination of Centonza and Teyeb.
Therefore, according to the amended part, the rejection is updated and described in detail in the below.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 02/10/2026 has been entered.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 16, 20, 23, and 26 are rejected under U.S.C. 103 as being unpatentable over Angelo Centonza and et. al. (USPub. No.: US 20220369174 A1, hereinafter “Centonza”) in a view of Oumer Teyeb et. al. (USPub. No.: US 20220217613 A1, hereinafter “Teyeb).
Regarding claim 16, Centonza teaches a method performed by a central unit (CU) of a first base station operating in evolved-universal terrestrial radio access (E-UTRA)-new radio (NR) dual connectivity (EN-DC) or NR-dual connectivity (NR-DC) in a communication system, the method comprising: (Centonza, in Paragraphs [0096], [0105], [0108]-[0110], and [0123], teaches that for EN-DC, NGEN-DC (NG-RAN E-UTRA-NR DC), NE-DC (NR-E-UTRA DC), or MR (Multi-Radio)-DC (NR-DC is one of MR-DC) operation, communication between CU and DU is described based on the method of exchanging messages such as UE CONTEXT MODIFICATION REQUEST message and UE CONTEXT MODIFICATION RESPONSE message. Therefore, a method is performed by a CU of the first base station (gNB) (gNB-CU in the art) in a communication system. Namely, gNB-CU (the CU of the first base station (gNB)) and gNB-DU (the DU of the first base station (gNB)) communicate with each other by exchanging messages.) receiving, from the DU of the first base station, a UE context modification response message including cell group configuration information, the cell group configuration information including the F1-C transfer path information for the UE; (Centonza, in Fig. 2 and in Paragraph [0081]-[0088] teaches that as described in [0081] and [0084], the F1AP procedure over F1-C (F1 AP indicates the F1-C transfer path as shown in the below by Teyeb) includes the UE Context Modification procedure to modify the established UE Context, e.g., establishing, modifying and releasing radio resources. As shown in Fig. 2, the UE context modification request message is initiated by the gNB-CU. Upon reception of this request message, the gNB-DU perform the modifications and reports the updates in the UE context modification response message to gNB-CU. In Paragraphs [0124], [0137], and [0141]-[0142], when the gNB-Du configuration query IE is contained in the UE context modification request message, gNB-DU include the CellGroupConfig IE in the DU to CU RRC information IE in the UE context modification response message. When the full Configuration IE is contained in the UE context modification request message, the gNB-DU generate a CellGroupConfig IE using full configuration and include it in the UE context modification response message and the gNB-CU expect to receive the CellGroupConfig IE generated by gNB-DU on the UE context modification response message. Further, as shown in Fig. 10 and Fig. 11, using the CellGroupConfig IE included in the DU to CU RRC Information IE (it is called or considered as the F1-C transfer path information for UE) contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU performs RRC Reconfiguration for UE. Here, the F1-C transfer path updates by the elements in the UE context modification response message such as the CellGroupConfig IE, DRB (Data Radio Bearer), RRC reconfiguration parameters as described in the table 2 and table 3.) and transmitting, to a user equipment (UE), a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic (Centonza, in Paragraph [0124], teaches that if the CellGroupConfig IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall perform RRC Reconfiguration with UE. The CellGroupConfig IE shall transparently be signaled to the UE. Here, the UE CONTEXT MODIFICATION RESPONSE message includes the information indicating the transmission path of the F1-C traffic as described in the above. Therefore, it is clear that a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic is transmitted to the UE.)
Although Centonza teaches some part of the rest of the claim 16, transmitting, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; and receiving, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station, and wherein the F 1-C transfer path information is used by the UE to transfer the F 1-C packet, to show further detail, the rest of the claim 16 is taught by Teyeb in the below.
Teyeb teaches that transmitting, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; (Teyeb, in Fig. 2 and 3 and in Paragraph [0007], teaches that Fig. 2 illustrates the baseline user plane (UP) protocol stack for IAB. Figs. 3A, 3B, and 3C illustrate the baseline control plane (CP) protocol stack for IAB. As shown, the full user plane F1-U (GTP-U/UDP/IP) is terminated at the IAB node and the full control plane F1-C (Fl-AP/SCTP/IP) is also terminated at the IAB node. Further, Figs 3A, 3B, and 3C clearly show that the F1 AP procedure is performed thru F1-C (F1 control plane) and it can be considered as the F1-C transfer path for UE. As describe in Fig 11 and in Paragraphs [0197]-[0201] and [0204]-[0205], the F1-AP UE context modification message (request message) is sent for the donor CU to the donor DU, which contains DU BAP (Backhaul Adaptation protocol) for donor DU (e.g. routing information for packets destined to IAB node) and an RRC reconfiguration message to reconfigure the MT BAP of IAB1 and optionally setup/reconfigure BH RLC channels between donor DU and IAB1. Futher, as described in Paragraph [0158], for DL traffic, since an IAB node's MT BAP determines whether an incoming packet is destined to itself (i.e. data belonging to F1-AP or a DRB for a UE being served for an IAB node) or it is to be forwarded to a child node, the MT function of IAB node acts as UE.) and receiving, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station, and wherein the F1-C transfer path information is used by the UE to transfer the F1-C packet (Teyeb, in Paragraph [0010] and [0019]-[0022], teaches that whether the radio bearers carrying CP (Control Plane)/UP (User Plane) traffic for the MT functionality of an IAB node is handled separately from the BH (BackHaul) Radio Link Control (RLC) channels and BH RLC channels are used to carry traffic to/from the IAB DU functionality, which could be intended either for the UEs served by the IAB node or for the child IAB nodes. When the packet is from a UE connected directly to the IAB node, or it is an F1-AP traffic originating from the IAB node, it is processed first by the higher layers (IP/UDP/GTP-U for UP (User Plane), IP/SCTP/ F1-AP for CP (Control Plane)), and is forwarded to the MT BAP layer. Then the packet is arrived to CU via the MT BAP layer.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza and Teyeb to include the technique of transmitting, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; and receiving, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an Fl interface between the IAB node and the CU of the first base station, and wherein the F 1-C transfer path information is used by the UE to transfer the F 1-C packet of Teyeb in the system of Centonza to provide mechanisms that make it possible to configure, setup, and/or operate the different node within a multi-hop Integrated Access Backhaul (IAB) network so that packets can be routed properly to their intended destination, based on the uplink routing configuration associated with the cell group configuration. (Teyeb, see Paragraphs [0121]-[0122]).).
Regarding claim 20, Centonza teaches A method performed by a distributed unit (DU) operating in evolved-universal terrestrial radio access (E-UTRA)-new radio (NR) dual connectivity (EN-DC) or NR-dual connectivity (NR-DC) in a communication system, the method comprising: (Centonza, in Paragraphs [0096], [0105], [0108]-[0110], and [0123], teaches that for EN-DC, NGEN-DC (NG-RAN E-UTRA-NR DC), NE-DC (NR-E-UTRA DC), or MR (Multi-Radio)-DC (NR-DC is one of MR-DC) operation, communication between CU and DU is described based on the method of exchanging messages such as UE CONTEXT MODIFICATION REQUEST message and UE CONTEXT MODIFICATION RESPONSE message. Therefore, a method is performed by a DU of the first base station (gNB) (gNB-DU in the art) in a communication system. Namely, gNB-CU (the CU of the first base station (gNB)) and gNB-DU (the DU of the first base station (gNB)) communicate with each other by exchanging messages.) receiving, from a central unit (CU) of a first base station, a user equipment (UE) context modification request message including FI control plane interface (F 1-C) transfer path information for a mobile termination function of an integrated access and backhaul (IAB) node; generating cell group configuration information including the F 1-C transfer path information for the UE; and transmitting, to the CU of the first base station, a UE context modification response message including the cell group configuration information, (Centonza, in Fig. 2 and in Paragraph [0081]-[0088] teaches that as described in [0081] and [0084], the F1AP procedure over F1-C (F1 AP indicates the F1-C transfer path as shown in the below by Teyeb) includes the UE Context Modification procedure to modify the established UE Context, e.g., establishing, modifying and releasing radio resources. As shown in Fig. 2, the UE context modification request message is initiated by the gNB-CU. Upon reception of this request message, the gNB-DU perform the modifications and reports the updates in the UE context modification response message to gNB-CU. In Paragraphs [0137], and [0141]-[0142], when the gNB-Du configuration query IE is contained in the UE context modification request message, gNB-DU include the CellGroupConfig IE in the DU to CU RRC information IE in the UE context modification response message. When the full Configuration IE is contained in the UE context modification request message, the gNB-DU generate a CellGroupConfig IE using full configuration and include it in the UE context modification response message and the gNB-CU expect to receive the CellGroupConfig IE generated by gNB-DU on the UE context modification response message. Further, as shown in Fig. 10 and Fig. 11, using the CellGroupConfig IE included in the DU to CU RRC Information IE (it is called or considered as the F1-C transfer path information for UE) contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU performs RRC Reconfiguration for UE. Here, the F1-C transfer path updates by the elements in the UE context modification response message such as the CellGroupConfig IE, DRB (Data Radio Bearer), RRC reconfiguration parameters as described in the table 2 and table 3.) wherein the cell group configuration information is transferred to the UE, (Centonza, in Paragraph [0124], teaches that if the CellGroupConfig IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall perform RRC Reconfiguration with UE. The CellGroupConfig IE shall transparently be signaled to the UE. Here, the UE CONTEXT MODIFICATION RESPONSE message includes the information indicating the transmission path of the F1-C traffic as described in the above. Therefore, it is clear that a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic may be transmitted to the UE.)
Centonza does not explicitly teach that wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station.
Teyeb teaches that wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station (Teyeb, in Paragraph [0010] and [0019]-[0022], teaches that whether the radio bearers carrying CP (Control Plane)/UP (User Plane) traffic for the MT functionality of an IAB node is handled separately from the BH (BackHaul) Radio Link Control (RLC) channels and BH RLC channels are used to carry traffic to/from the IAB DU functionality, which could be intended either for the UEs served by the IAB node or for the child IAB nodes. When the packet is from a UE connected directly to the IAB node, or it is an F1-AP traffic originating from the IAB node, it is processed first by the higher layers (IP/UDP/GTP-U for UP (User Plane), IP/SCTP/ F1-AP for CP (Control Plane)), and is forwarded to the MT BAP layer. Then the packet is arrived to CU via the MT BAP layer.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza and Teyeb to include the technique of wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station of Teyeb in the system of Centonza to provide mechanisms that make it possible to configure, setup, and/or operate the different node within a multi-hop Integrated Access Backhaul (IAB) network so that packets can be routed properly to their intended destination, based on the uplink routing configuration associated with the cell group configuration. (Teyeb, see Paragraphs [0121]-[0122]).).
Regarding claim 23, Centonza teaches a central unit (CU) of a first base station operating in evolved universal terrestrial radio access (E-UTRA)-new radio (NR) dual connectivity (EN-DC) or NR- dual connectivity (NR-DC) in a communication system, (Centonza, in Paragraphs [0096], [0105], [0108]-[0110], and [0123], teaches that for EN-DC, NGEN-DC (NG-RAN E-UTRA-NR DC), NE-DC (NR-E-UTRA DC), or MR (Multi-Radio)-DC (NR-DC is one of MR-DC) operation, communication between CU and DU is described based on the method of exchanging messages such as UE CONTEXT MODIFICATION REQUEST message and UE CONTEXT MODIFICATION RESPONSE message. Therefore, a method is performed by a CU of the first base station (gNB) (gNB-CU in the art) in a communication system. Namely, gNB-CU (the CU of the first base station (gNB)) and gNB-DU (the DU of the first base station (gNB)) communicate with each other by exchanging messages.) the CU comprising: a transceiver; and a controller configured to: (Centonza, in Fig. 1, teaches that Fig. 1 illustrates the overall architecture of current 5G RAN architecture including the CU and the DU to communicate with each other. In Fig. 13 and in Paragraph [0287], the gNB-CU 1301 may include network interface circuitry 1301b configured to provide communications with other nodes of the network and/or core network CN. The gNB-CU 1301 may also include a processing circuitry 1301c coupled to the transceiver circuitry, and a memory circuitry 1301d. Therefore, it is clear that a central unit (CU) of a first base station in a communication system may comprise a transceiver and a controller) receive, from the DU of the first base station, a UE context modification response message including cell group configuration information, the cell group configuration information including the F1-C transfer path information for the UE; (Centonza, in Fig. 2 and in Paragraph [0081]-[0088] teaches that as described in [0081] and [0084], the F1AP procedure over F1-C (F1 AP indicates the F1-C transfer path as shown in the below by Teyeb) includes the UE Context Modification procedure to modify the established UE Context, e.g., establishing, modifying and releasing radio resources. As shown in Fig. 2, the UE context modification request message is initiated by the gNB-CU. Upon reception of this request message, the gNB-DU perform the modifications and reports the updates in the UE context modification response message to gNB-CU. In Paragraphs [0137], and [0141]-[0142], when the gNB-Du configuration query IE is contained in the UE context modification request message, gNB-DU include the CellGroupConfig IE in the DU to CU RRC information IE in the UE context modification response message. When the full Configuration IE is contained in the UE context modification request message, the gNB-DU generate a CellGroupConfig IE using full configuration and include it in the UE context modification response message and the gNB-CU expect to receive the CellGroupConfig IE generated by gNB-DU on the UE context modification response message. Further, as shown in Fig. 10 and Fig. 11, using the CellGroupConfig IE included in the DU to CU RRC Information IE (it is called or considered as the F1-C transfer path information for UE) contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU performs RRC Reconfiguration for UE. Here, the F1-C transfer path updates by the elements in the UE context modification response message such as the CellGroupConfig IE, DRB (Data Radio Bearer), RRC reconfiguration parameters as described in the table 2 and table 3.) transmit, to a user equipment (UE), a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic (Centonza, in Paragraph [0124], teaches that if the CellGroupConfig IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall perform RRC Reconfiguration with UE. The CellGroupConfig IE shall transparently be signaled to the UE. Here, the UE CONTEXT MODIFICATION RESPONSE message includes the information indicating the transmission path of the F1-C traffic as described in the above. Therefore, it is clear that a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic may be transmitted to the UE.)
Although Centonza teaches some part of the rest of the claim 16, transmit, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; and receive, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an Fl interface between the IAB node and the CU of the first base station, and wherein the F 1-C transfer path information is used by the UE to transfer the F 1-C packet, to show further detail, the rest of the claim 23 is taught by Teyeb in the below.
Teyeb teaches that transmit, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; (Teyeb, in Fig. 2 and 3 and in Paragraph [0007], teaches that Fig. 2 illustrates the baseline user plane (UP) protocol stack for IAB. Figs. 3A, 3B, and 3C illustrate the baseline control plane (CP) protocol stack for IAB. As shown, the full user plane F1-U (GTP-U/UDP/IP) is terminated at the IAB node and the full control plane F1-C (Fl-AP/SCTP/IP) is also terminated at the IAB node. Further, Figs 3A, 3B, and 3C clearly show that the F1 AP procedure is performed thru F1-C (F1 control plane) and it can be considered as the F1-C transfer path for UE. As describe in Fig 11 and in Paragraphs [0197]-[0201] and [0204]-[0205], the F1-AP UE context modification message (request message) is sent for the donor CU to the donor DU, which contains DU BAP (Backhaul Adaptation protocol) for donor DU (e.g. routing information for packets destined to IAB node) and an RRC reconfiguration message to reconfigure the MT BAP of IAB1 and optionally setup/reconfigure BH RLC channels between donor DU and IAB1. Futher, as described in Paragraph [0158], for DL traffic, since an IAB node's MT BAP determines whether an incoming packet is destined to itself (i.e. data belonging to F1-AP or a DRB for a UE being served for an IAB node) or it is to be forwarded to a child node, the MT function of IAB node acts as UE.) and receive, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station, and wherein the F1-C transfer path information is used by the UE to transfer the F1-C packet (Teyeb, in Paragraph [0010] and [0019]-[0022], teaches that whether the radio bearers carrying CP (Control Plane)/UP (User Plane) traffic for the MT functionality of an IAB node is handled separately from the BH (BackHaul) Radio Link Control (RLC) channels and BH RLC channels are used to carry traffic to/from the IAB DU functionality, which could be intended either for the UEs served by the IAB node or for the child IAB nodes. When the packet is from a UE connected directly to the IAB node, or it is an F1-AP traffic originating from the IAB node, it is processed first by the higher layers (IP/UDP/GTP-U for UP (User Plane), IP/SCTP/ F1-AP for CP (Control Plane)), and is forwarded to the MT BAP layer. Then the packet is arrived to CU via the MT BAP layer.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza and Teyeb to include the technique of transmit, to a distributed unit (DU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; and receive, from the UE, an F1-C packet, wherein the F1-C packet is a control plane data on an Fl interface between the IAB node and the CU of the first base station, and wherein the F 1-C transfer path information is used by the UE to transfer the F 1-C packet of Teyeb in the system of Centonza to provide mechanisms that make it possible to configure, setup, and/or operate the different node within a multi-hop Integrated Access Backhaul (IAB) network so that packets can be routed properly to their intended destination, based on the uplink routing configuration associated with the cell group configuration. (Teyeb, see Paragraphs [0121]-[0122]).).
Regarding claim 26, Centonza teaches a distributed unit (DU) operating in evolved-universal terrestrial radio access (E-UTRA)-new radio (NR) dual connectivity (EN-DC) or NR-dual connectivity (NR-DC) in a communication system, (Centonza, in Paragraphs [0096], [0105], [0108]-[0110], and [0123], teaches that for EN-DC, NGEN-DC (NG-RAN E-UTRA-NR DC), NE-DC (NR-E-UTRA DC), or MR (Multi-Radio)-DC (NR-DC is one of MR-DC) operation, communication between CU and DU is described based on the method of exchanging messages such as UE CONTEXT MODIFICATION REQUEST message and UE CONTEXT MODIFICATION RESPONSE message. Therefore, a method is performed by a DU of the first base station (gNB) (gNB-DU in the art) in a communication system. Namely, gNB-CU (the CU of the first base station (gNB)) and gNB-DU (the DU of the first base station (gNB)) communicate with each other by exchanging messages.) the DU comprising: a transceiver; and a controller configured to: (Centonza, in Fig. 1, teaches that Fig. 1 illustrates the overall architecture of current 5G RAN architecture including the CU and the DU to communicate with each other. In Fig. 13 and in Paragraph [0288], operations of a DU1303, 1305 network node (1300) may be performed by processing circuitry 1303c, 1305c, respectively, network interface 1303b, 1305b, and/or transceiver 1303a, 1305a. The processing circuitry 1303c, 1305c may control transceiver 1303a, 1305a to transmit downlink communications through transceiver 1303a, 1305a over a radio interface to one or more communication devices and/or to receive uplink communications through transceiver 1303a, 1305a from one or more communication devices over a radio interface. Therefore, it is clear that a DU of a first base station in a communication system may comprise a transceiver and a controller.) receive, from a central unit (CU) of the first base station, a user equipment (UE) context modification request message including F1 control plane interface (F1-C) transfer path information for a UE, wherein the UE is a mobile termination function of an integrated access and backhaul (IAB) node; generating cell group configuration information including the F1-C transfer path information for the UE; and transmitting, to the CU of the first base station, a UE context modification response message including the cell group configuration information, (Centonza, in Fig. 2 and in Paragraph [0081]-[0088] teaches that as described in [0081] and [0084], the F1AP procedure over F1-C (F1 AP indicates the F1-C transfer path as shown in the below by Teyeb) includes the UE Context Modification procedure to modify the established UE Context, e.g., establishing, modifying and releasing radio resources. As shown in Fig. 2, the UE context modification request message is initiated by the gNB-CU. Upon reception of this request message, the gNB-DU perform the modifications and reports the updates in the UE context modification response message to gNB-CU. In Paragraphs [0137], and [0141]-[0142], when the gNB-Du configuration query IE is contained in the UE context modification request message, gNB-DU include the CellGroupConfig IE in the DU to CU RRC information IE in the UE context modification response message. When the full Configuration IE is contained in the UE context modification request message, the gNB-DU generate a CellGroupConfig IE using full configuration and include it in the UE context modification response message and the gNB-CU expect to receive the CellGroupConfig IE generated by gNB-DU on the UE context modification response message. Further, as shown in Fig. 10 and Fig. 11, using the CellGroupConfig IE included in the DU to CU RRC Information IE (it is called or considered as the F1-C transfer path information for UE) contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU performs RRC Reconfiguration for UE. Here, the F1-C transfer path updates by the elements in the UE context modification response message such as the CellGroupConfig IE, DRB (Data Radio Bearer), RRC reconfiguration parameters as described in the table 2 and table 3.) wherein the cell group configuration information is transferred to the UE, (Centonza, in Paragraph [0124], teaches that if the CellGroupConfig IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall perform RRC Reconfiguration with UE. The CellGroupConfig IE shall transparently be signaled to the UE. Here, the UE CONTEXT MODIFICATION RESPONSE message includes the information indicating the transmission path of the F1-C traffic as described in the above. Therefore, it is clear that a configuration message including the cell group configuration information indicating the transmission path of the F1-C traffic may be transmitted to the UE.)
Centonza does not explicitly teach that wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station.
Teyeb teaches that wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station (Teyeb, in Paragraph [0010] and [0019]-[0022], teaches that whether the radio bearers carrying CP (Control Plane)/UP (User Plane) traffic for the MT functionality of an IAB node is handled separately from the BH (BackHaul) Radio Link Control (RLC) channels and BH RLC channels are used to carry traffic to/from the IAB DU functionality, which could be intended either for the UEs served by the IAB node or for the child IAB nodes. When the packet is from a UE connected directly to the IAB node, or it is an F1-AP traffic originating from the IAB node, it is processed first by the higher layers (IP/UDP/GTP-U for UP (User Plane), IP/SCTP/ F1-AP for CP (Control Plane)), and is forwarded to the MT BAP layer. Then the packet is arrived to CU via the MT BAP layer.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza and Teyeb to include the technique of wherein the F1-C transfer path information is used by the UE to transfer an F1-C packet to the CU of the first base station, and wherein the F1-C packet is a control plane data on an F1 interface between the IAB node and the CU of the first base station of Teyeb in the system of Centonza to provide mechanisms that make it possible to configure, setup, and/or operate the different node within a multi-hop Integrated Access Backhaul (IAB) network so that packets can be routed properly to their intended destination, based on the uplink routing configuration associated with the cell group configuration. (Teyeb, see Paragraphs [0121]-[0122]).).
Claims 17-18, 21-22, 24-25, and 27-28 are rejected under U.S.C. 103 as being unpatentable over Angelo Centonza et. al. (USPub. No.: US 20220369174 A1, hereinafter “Centonza”) in a view of Oumer Teyeb et. al. (USPub. No.: US 20220217613 A1, hereinafter “Teyeb) and further in a view of Daewook Byun (USPub. No.: US 20220086935 A1, hereinafter “Byun”).
Regarding claim 17, combination of Centonza and Teyeb teaches the features defined in the claims 16, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC (Byun, in Paragraph [0009] teaches that to further teach the EN-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 3 and 7 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating the transmission path of the F1-C traffic (F1 interface information) indicates one of LTE, NR, or both LTE and NR as the transfer path of the F1-C traffic in EN-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 18, combination of Centonza and Teyeb teaches the features defined in the claims 16, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC (Byun, in Paragraph [0009] teaches that to further teach NR-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 4 and 5 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Further, Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating transmission path of a F1-C traffic indicates one of MCG, SCG, or both the MCG and the SCG as the transfer path of the F1-C traffic in NR-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 21, combination of Centonza and Teyeb teaches the features defined in the claims 20, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC (Byun, in Paragraph [0009] teaches that to further teach the EN-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 3 and 7 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating the transmission path of the F1-C traffic (F1 interface information) indicates one of LTE, NR, or both LTE and NR as the transfer path of the F1-C traffic in EN-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of the F1-C traffic in the EN-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 22, combination of Centonza and Teyeb teaches the features defined in the claims 20, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC (Byun, in Paragraph [0009] teaches that to further teach NR-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 4 and 5 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Further, Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating transmission path of a F1-C traffic indicates one of MCG, SCG, or both the MCG and the SCG as the transfer path of the F1-C traffic in NR-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 24, combination of Centonza and Teyeb teaches the features defined in the claims 23, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of F1-C traffic in the EN-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of F1-C traffic in the EN-DC (Byun, in Paragraph [0009] teaches that to further teach the EN-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 3 and 7 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating the transmission path of the F1-C traffic (F1 interface information) indicates one of LTE, NR, or both LTE and NR as the transfer path of the F1-C traffic in EN-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb and Byun to include the technique of wherein the F1-C transfer path information indicates one of long term evolution (LTE), NR, or both LTE and NR as the transfer path of F1-C traffic in the EN-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 25, combination of Centonza and Teyeb teaches the features defined in the claims 23, -refer to the indicated claim for reference(s).
However combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC (Byun, in Paragraph [0009] teaches that to further teach NR-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 4 and 5 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Further, Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating transmission path of a F1-C traffic indicates one of MCG, SCG, or both the MCG and the SCG as the transfer path of the F1-C traffic in NR-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 27, combination of Centonza and Teyeb teaches the features defined in the claims 26, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of F1-C traffic in the EN-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of F1-C traffic in the EN-DC (Byun, in Paragraph [0009] teaches that to further teach the EN-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 3 and 7 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating the transmission path of the F1-C traffic (F1 interface information) indicates one of LTE, NR, or both LTE and NR as the transfer path of the F1-C traffic in EN-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of long term evolution (LTE), new radio (NR), or both LTE and NR as the transfer path of F1-C traffic in the EN-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Regarding claim 28, combination of Centonza and Teyeb teaches the features defined in the claims 26, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC.
Byun teaches that wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC (Byun, in Paragraph [0009] teaches that to further teach NR-DC, the integrated access and backhaul system should be compliant with SA and NSA deployments in that IAB-nodes can operate in SA (Stand Alone) or NSA (Non-Stand Alone) mode, meaning that support needs to be provided for dual connectivity (both EN-DC and NR-DC) for both UEs and IAB-nodes. Here, as described in ETSI TS 137 340 V.15.5.0 (2019-05) attached, EN-DC (E-UTRAN New Radio Dual Connectivity) enables UEs or IAB-nodes to connect to both LTE and NR (New Radio) networks, simultaneously and for UEs or IAB-nodes, the MCG (Master Cell Group) may use the LTE network and the SCG (Secondary Cell group) may use NR network. While, NR-DC (New Radio Dual Connectivity)) allows UEs or IAB-nodes to use two different NR networks and for both UE and IAB-nodes, MCG (Master Cell Group) and SCG (Secondary Cell group) represent two cell groups that can be connected to NR, simultaneously. Hereinafter, it can be considered as one of example that for EN-DC, the MCG may use LTE and the SCG may use NR and for NR-DC, both MCG and SCG may use NR. In Fig. 4 and 5 and in Paragraphs [0111]-[0131], Byun teaches that the F1-C traffic path information and indication can be decided by F1 interface and F1 control (F1-C) functions for gNB-CU and gNB-DU for MCG and SCG may include the following: F1 interface management function, System information management function, F1 UE context management function, RRC message transfer functions, and etc. Further, Byun, in Fig. 17 A and B and in Paragraphs [0241]-[0243], teaches that Fig. 17 A and B show an example of wireless system for controlling radio resource of route change or modification procedure with UE context modification function and RRC message transfer function for a dual-connecting IAB node (either EN-DC or NR-DC) in a wireless communication system. In FIGS. 17A and 17B, an IAB donor CU may provide an indication to a SCG IAB node DU. The indication may indicate whether to allocate or not the radio resource to established bearer(s) between the dual-connecting IAB node and the SCG IAB node DU for redundant route. The IAB donor CU may provide the indication when the IAB donor CU realizes that redundant route is not used, link blockage occurs, or load balancing over both routes is required. In case link blockage between the dual-connecting IAB node MT (Mobal Terminated) and MCG IAB node DU occurs, the MCG IAB node DU or the SCG IAB node DU may notify the IAB donor CU that link blockage happens via F1-U or F1-C, respectively in order to request or trigger route change toward already established redundant route. In addition, the SCG IAB node DU may inform the IAB donor CU of whether the radio resource can be allocated or not to bearer(s) established for redundant route. The detail procedure is taught by Byun in Paragraphs [0244]-[0261]. Based on this observation, it is clear that the information indicating transmission path of a F1-C traffic indicates one of MCG, SCG, or both the MCG and the SCG as the transfer path of the F1-C traffic in NR-DC.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Byun to include the technique of wherein the F1-C transfer path information indicates one of a master cell group (MCG), a secondary cell group (SCG), or both the MCG and the SCG as the transfer path of F1-C traffic in the NR-DC of Byun in the system of combination of Centonza and Teyeb to provide a method for controlling radio resource of a redundant route for a dual-connecting IAB node in a wireless communication system, in result using the radio resource efficiently by the SCG IAB node DU before link blockage case or load balancing case and being able to be switched by the DU of an IAB node to a different location or function without disrupting the network's performance or user experience. (Byun, see Paragraphs [0018] and [0021]).).
Claims 19 are rejected under U.S.C. 103 as being unpatentable over Angelo Centonza and et. al. (USPub. No.: US 20220369174 A1, hereinafter “Centonza”) in a view of Oumer Teyeb et. al. (USPub. No.: US 20220217613 A1, hereinafter “Teyeb) and further in a view of Taehun Kim (USPub. No.: US 20230247720 A1, hereinafter “Kim”).
Regarding claim 19, combination of Centonza and Teyeb teaches the features defined in the claims 16, -refer to the indicated claim for reference(s).
However, combination of Centonza and Teyeb does not explicitly teaches that further comprising: transmitting, to a CU of a second base station, a request message to provide configuration information of F1-C traffic; and receiving, from the CU of the second base station, a response message including information for the F1-C traffic.
Kim teaches that further comprising: transmitting, to a CU of a second base station, a request message to provide configuration information of F1-C traffic; and receiving, from the CU of the second base station, a response message including information for the F1-C traffic (Kim, in Fig. 29 and in Paragraphs [0354] and [0355], teaches that to further teach the communication between two CU-CPs of two base station, Fig 29 illustrates an example of determining SDT (Small Data Transmission). The base station distributed unit and the base station central unit may be connected to each other via an F1 interface comprising an Fl control plane interface (F1-C) and/or an Fl user plane interface (Fl-U). The base station central unit (CU) may comprise a base station central unit control plane (gNB-CU-CP) and/or a base station central unit user plane (gNB-CU-UP). The base station distributed unit (DU) may communicate with the base station central unit control plane via the F1 control plane interface (F1-C). The base station distributed unit may communicate with the base station central unit user plane via the Fl user plane interface (F1-U). In Fig. 29, a wireless device may communicate with a new base station (gNB) comprising a new base station central unit (gNB-CU) and a new base station distributed unit (gNB-DU). Based on determining SDT, a wireless device may send a message to the new base station distributed unit where the message may comprise at least one of: an RRC resume request message; the
1st uplink data; assistance parameters of the SDT; buffer status report (BSR) requesting uplink grant/resource for transmission of the 2nd uplink data. Based on receiving the message, the new base station distributed unit may send a first F1 message to a new base station central unit control plane via the F1-C. Based on receiving the message, the new base station distributed unit may send a second F1 message to the new base station central unit user plane via the F1-U where the second F1 message may comprise the 1st uplink data. Based on receiving the first F1 message, the new base station central unit control plane may send a retrieve UE Context Request Message to an old base station central unit control plane where the retrieve UE context message may comprise assistance information of the SDT. Based on the retrieve UE context message, the old base station central unit control plane may determine to keep contexts of the wireless device. Based on the retrieve UE context message, the old base station central unit control plane may further determine to postpone/delay sending an RRC release message. Based on the determining to keep contexts of the wireless device, the old base station central unit control plane may send an Xn DL message (retrieve UE context failure message) to the new base station central unit control plane where the Xn DL message may indicate the determining to keep contexts of the wireless device (anchor keeping) or the determining to postpone/delay sending an RRC release message. Based on receiving the Xn DL message, the new base station central unit control plane may determine to initiate/perform the SDT with the old base station. Based on this observation, it is clear that a second request message (UE Context Request Message) may be transmitted to a CU of a second base station (Old base station) to provide configuration information of the F1-C traffic and a second response message (Xn DL message (retrieve UE context failure message)) including information for the F1-C traffic may be received from the CU of the second base station.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Centonza, Teyeb, and Kim to include the technique of further comprising: transmitting, to a CU of a second base station, a request message to provide configuration information of F1-C traffic; and receiving, from the CU of the second base station, a response message including information for the F1-C traffic of Kim in the system of combination of Centonza and Teyeb to provide an enhanced procedure for sending an RRC release message during small data transmission (SDT) to avoid the interruption/failure of the SDT procedure that occurs in the existing technologies (Kim, see Paragraph [0329]).).
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 JAEYOUNG KWAK whose telephone number is (703)756-1768. The examiner can normally be reached Monday-Friday 9 AM -5 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/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kevin Bates can be reached at 571-272-3980. 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.
/JAEYOUNG KWAK/Examiner, Art Unit 2472
/KEVIN T BATES/Supervisory Patent Examiner, Art Unit 2472
Prosecution Insights